Kill Your Customer price

Edit / far@Centreless X(Twitter)@Tocentreles On May 24, Solana posted a blog on its website, saying that the Solana Identity Group and the Solana Foundation announced that the Solana Authentication Service (SAS) is now live on the Solana mainnet, an open, permissionless, verifiable credential protocol. SAS allows trusted issuers to associate off-chain information, such as KYC checks, geolocation eligibility, Clip membership, or authentication status, with a user's wallet. These certifications are signed, verifiable, and reusable across applications, eliminating the need to expose sensitive data on-chain or repeat verification steps. By providing a neutral, permissionless attestation layer, SAS enables compliance, access control, reputation systems and programmable identities across the entire Solana ecosystem. This results in a better and more convenient experience for both end users and builders. Attestation Service and Oracle are both mechanisms that bring off-chain information on-chain, but they differ significantly in their positioning, purpose, trust model, and way of working. Let's do a system comparison: ✅ A table to understand Attestation Service vs oracles: project Attestation Service Oracle (oracle) Main uses: Turn off-chain "subjective or static information such as identity, status, behavior, etc." into on-chain credentials Feed off-chain "objective, dynamic data" to on-chain (e.g., price, weather, etc.) data type Subjective/event-based: whether you are at least 18 years old, whether you have passed the verification, and whether you are a member of an organization Numeric/factual type: BTC price, off-chain API data, weather data data structure Authentication "claim" that can be reused and bound to a wallet Data used in real-time in transactions (e.g. price feeds) Sources of trust Proof of signature by a "trusted publisher" (e.g., KYC agency, DAO, device vendor). From multiple data sources, aggregated and published by oracle networks Frequency of updates Infrequent and often generated once in long term Frequent updates, such as prices every minute Whether it can be composable and reused Yes, a single authentication can be reused by multiple applications (e.g. KYC proof for one wallet) No, price data is primarily an input to a trading action Handling of Privacy Strong privacy protection, only verifies whether it is passed or not, and does not disclose detailed information There is usually no privacy of user identity Representative project/technology Solana Attestation Service、Ethereum Attestation Service (EAS) Chainlink、Pyth、Band Protocol ? Let's take a comparative example Attestation Service Use Case: You complete "real-name authentication" through a Web3 platform and receive the "I'm an adult" on-chain authentication seal. This stamp is stored in your wallet and can be verified by any dApp in the future without requiring you to resubmit your ID each time. Oracle Use Case: A DeFi protocol needs to know the current price of ETH in order to determine the liquidation conditions. It reads the real-time ETH/USD price through an oracle like Chainlink. The core differences are summarized in one sentence: The oracle is a mechanism for "feeding numbers", focusing on off-chain "objective facts"; Attestation Service, on the other hand, is a mechanism for "authenticating identity or state" and focuses on off-chain "subjective or conditional trust". The two are complementary, not substitute.