Solana launches SAS identification verification service: a new mechanism for verification distinct from Oracle Machine.

robot
Abstract generation in progress

Solana Launches Identification Verification Service SAS, How is it Different from Oracle Machine?

Recently, Solana launched a new identification verification service (SAS), which is an open, permissionless verifiable credential protocol. This service allows trusted issuers to associate off-chain information with user wallets, such as KYC check results, geographical eligibility, membership status, or certification status. These verifications are signed and validated, allowing for reuse across different applications without exposing sensitive data or requiring repeated verification steps.

The launch of SAS provides a neutral and permissionless proof layer for the Solana ecosystem, aiming to achieve compliance, access control, reputation systems, and programmable identification throughout the ecosystem. This not only brings a higher quality and more convenient experience for end users but also offers new functional support for developers.

Solana launches AS identification verification service, what is the difference with Oracle Machine?

Although verification services and Oracle Machines are both mechanisms for bringing off-chain information onto the blockchain, they have significant differences in terms of positioning, use cases, trust models, and how they operate. Below is a detailed comparison of the two:

Verification Services vs Oracle Machine: Main Features Comparison

  1. Main Use:

    • Verification services: Transforming off-chain identification, status, behaviors, and other subjective or static information into on-chain credentials.
    • Oracle Machine: Input objective and dynamic off-chain data (such as prices, weather, etc.) onto the chain.
  2. Data Types:

    • verification services: subjective/event-based, such as age verification, identification, organizational membership, etc.
    • Oracle Machine: Numerical/Factual type, such as cryptocurrency prices, external API data, weather information, etc.
  3. Data Structure:

    • Verification service: reusable, wallet-bound verification "stamp"
    • Oracle Machine: Real-time data streams used in transactions (e.g., price feed)
  4. Source of Trust:

    • Verification service: Specific trusted publishers (such as KYC institutions, DAOs, device manufacturers) sign to prove
    • Oracle Machine: Multiple data sources aggregated and published through the Oracle Machine network.
  5. Update Frequency:

    • verification service: usually infrequent, valid for a long time after being generated once
    • Oracle Machine: High-frequency updates, possibly updating price data every minute.
  6. Composability and Reusability:

    • Verification service: Yes, a single verification can be reused across multiple applications.
    • Oracle Machine: Usually not allowed, price data is primarily used as input for specific transactions.
  7. Privacy Processing:

    • Verification Service: Emphasizes privacy protection, only verifies "whether passed" without disclosing detailed information.
    • Oracle Machine: usually does not involve user identification privacy
  8. Representative project/technology:

    • verification services: Solana Attestation Service, Ethereum Attestation Service (EAS)
    • Oracle Machine: Chainlink, Pyth, Band Protocol

A specific example can help to better understand the difference between the two.

Application scenarios of verification services: After users complete identity verification on the Web3 platform, they receive an "adult" on-chain certification stamp. This stamp is stored in the user's wallet, and any dApp can verify it in the future without the user needing to resubmit identification documents.

Application scenarios of Oracle Machine: DeFi protocols need to know the current price of ETH to determine liquidation conditions, and will read the real-time ETH/USD price through the Oracle Machine.

Overall, the Oracle Machine primarily focuses on the off-chain "objective facts" data input, while the verification service concentrates on off-chain "subjective or conditional trust" identification or status verification. These two mechanisms play a complementary rather than substitute role in the blockchain ecosystem, jointly promoting the diversified development of blockchain applications.

SOL-0.1%
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • 6
  • Share
Comment
0/400
BakedCatFanboyvip
· 5h ago
Another verification mechanism, I'm so hungry.
View OriginalReply0
AirdropHustlervip
· 5h ago
It's another new trick to Be Played for Suckers...
View OriginalReply0
ForkTroopervip
· 5h ago
Is this really going viral?
View OriginalReply0
SmartMoneyWalletvip
· 6h ago
Another identification tool to fish for retail investors
View OriginalReply0
OnChainDetectivevip
· 6h ago
hmm another identity layer... traced the commit history, seems legit but idk about the trust model tbh
Reply0
HodlBelievervip
· 6h ago
Analysis indicators are king, a trust tool that does not betray the original intention.
View OriginalReply0
Trade Crypto Anywhere Anytime
qrCode
Scan to download Gate app
Community
English
  • 简体中文
  • English
  • Tiếng Việt
  • 繁體中文
  • Español
  • Русский
  • Français (Afrique)
  • Português (Portugal)
  • Bahasa Indonesia
  • 日本語
  • بالعربية
  • Українська
  • Português (Brasil)