BNB Attestation Service

BNB Chain’s August 8, 2024 hackathon article presented BAS as a tool for applications involving credentials, reputation and verification. This is a dated record of the service’s developer-facing role before the separately tracked BAS token appeared. It is not a claim that every suggested application was built.

The official contract repository credits Ethereum Attestation Service as its starting point and lists deployments for BNB Smart Chain and opBNB. A schema sets the fields of a statement; an attester signs it; an application decides whether to accept it. BAS can preserve who said something without making that person infallible.

The Passport documentation goes beyond an abstract registry. It describes a request moving from the user through the SDK to an issuer, then a proof reaching a verifier before the user calls the Passport contract. It lists several exchange-KYC schemas. These are documented verification formats, not proof that an exchange endorses every application using them.

The storage choice also matters. The SDK supports off-chain signatures without Greenfield and an optional Greenfield route with public or private object visibility. A private object is not the same as an anonymous identity, and moving an object off-chain cannot undo information already published. This makes privacy a property of an implemented workflow rather than a blanket promise attached to BAS.

The distinct BASToken was deployed on July 14, 2025 at BNB block 53,994,920. Binance Wallet then scheduled a July 17 subscription offering 200 million BAS, 2% of a 10-billion supply. Its Booster program allocated a further 600 million, or 6%. The sale conditions said claimed tokens would remain locked until the project enabled circulation.

The July 16 Binance announcement already described fees, premium APIs, reputation staking, rewards and governance as intended uses. On August 19, the project published an allocation of 15% to investors, 18% to the team, 42% to the community and 25% to the foundation. KuCoin scheduled BAS/USDT trading for August 21 at 08:00 UTC. These records establish a market rollout and published plans; they do not supply a complete vesting calendar or demonstrate every utility in operation.

The verified token is not a proxy. Its cap and total supply both read 10 billion at review, and it was unpaused. A minter cannot exceed the cap merely because it has the minting role.

Transfer access is less automatic. The pauser role can pause the contract and maintain an allowlist; while paused, ordinary transfers require both sender and recipient to be allowed. Minting has a separate exception to that check, still bounded by the cap. The default administrator can assign minters, while the pauser role administers its own membership. Those code powers should not be collapsed into a single unidentified “owner”; the full current membership of those roles was not resolved.

The public homepage and BAScan still present credentials, reputation and an attestation explorer. The Passport repository provides a concrete application design. None of these observations by itself shows that creating a credential must consume the traded BAS token or that a token holder receives registry income. The reviewed sources did not identify a complete live fee schedule, staking and governance deployment map or a legal revenue-sharing instrument.

BAS therefore has a more specific unfinished task than simply attracting users: making the promised token functions traceable through the credential products people can use. A claim recorded by BAS, an identity checked through Passport and a BAS balance are three different things. The project’s next economic chapter depends on how those things actually connect.