This report, by Eric Meng collaborating with the BSSC Audit Adoption WG, describes an assessment of the token stETH deployed on the Ethereum network against the BSSC Token Integration Standard version 2. It is published as an example assessment of a well-known token against the specification.
| BSSC Token Integration Standard version 2 | ||
|---|---|---|
| Specification URL: https://specs.blockchainssc.org/tis/v2.html | ||
| Token being evaluated | Name: | Lido Staked ETH |
| Symbol: | stETH | |
| Network: | Ethereum | |
| Deployment Address(es): | ||
| Evaluator | Name: | Eric Meng and BSSC Audit Adoption WG |
| Contact Details: | ||
| Evaluation | Date completed: | 2026-11-08 |
| Outcome / comments: |
This report was compiled as an illustative example to provide guidance on developing an evaluation report, and may contain material errors. The reprt was generated independently from public information, and the participation of Lido (the principal Token Porject participant) was not sought. The stETH token fails a small number of requirements of the specification. However, the assessors believe it meets all other requirements. The failures are related to the events it emits when balances are changed - its behaviour is non-standard. The differences are documented in the source code. Mitigation of any risk introduced requires specific handling for the stETH-specific behaviour. | |
| title | Status | Comments / evidence |
|---|---|---|
| Token Allocation | Passes - Correctly Implemented |
stETH is minted 1:1 on ETH deposit via submit() and tracks total pooled ether through internal shares accounting; allocation and supply mechanics are documented |
| Is it native, bridged, wrapped? | Passes - Correctly Implemented |
Native Ethereum liquid staking token issued by the Lido protocol, not bridged or wrapped; wstETH is the non-rebasing wrapper. |
| Token Rebasing | Passes - Correctly Implemented |
Balances rebase daily from the Lido oracle report (nine operators, 5-of-9 consensus) with sanity bounds of max 27% APR and max 5% CL decrease. The shares mechanism and getPooledEthByShares() are documented. |
| Trading History | Passes - Correctly Implemented |
Live since December 2020 with continuous trading across the Curve stETH/ETH pool and major exchanges. |
| Price Discovery Mechanism | Passes - Correctly Implemented |
Secondary price is discovered on the Curve stETH/ETH pool and exchanges; a Chainlink stETH/ETH feed exists and the protocol conversion rate is exposed via getPooledEthByShares(). |
| Stablecoin Backing | Not Applicable (passes) |
Not a stablecoin |
| Protect Backing Assets from Issuer Insolvency | Not Applicable (passes) |
Not an off-chain or real-world asset-backed token, so this requirement does not apply. |
| Identify Parties Controlling Critical Actions | Passes - Correctly Implemented |
Upgrades, role grants, and pause are controlled by the Lido DAO Aragon Voting and Agent and executed through the dual governance timelock; the controlling parties are identified in the docs. |
| Document Governance | Passes - Correctly Implemented |
The governance model of LDO voting via Aragon, Easy Track, and dual governance is publicly documented. |
| Identify Governance participants | Passes - Correctly Implemented |
Governance participants are LDO holders; votes and proposals are public on the Aragon voting portal and Snapshot |
| Pass Code Audit | Passes - Correctly Implemented |
Repeatedly audited by Sigma Prime, MixBytes, Certora, ChainSecurity, Statemind, OpenZeppelin, and Consensys Diligence, with reports published and no unresolved critical findings. audits |
| Audit Code to a Standard | Justified Exception (passes) |
In the opinion of the assessor(s), the audits represented standard practice when performed. |
| Publish Code Audit Report or Attestation | Passes - Correctly Implemented |
|
| Limit Privileged Roles | Passes - Correctly Implemented |
Privileged capability is scoped to named roles (PAUSE_ROLE, RESUME_ROLE, STAKING_CONTROL_ROLE, STAKING_PAUSE_ROLE) held by the DAO Agent rather than broad owner control. |
| Decentralize Privileged Roles | Passes - Correctly Implemented |
Roles are assigned to the Aragon Agent under LDO governance with a dual governance timelock giving stETH stakers a veto, not to EOAs |
| Document Privileged Roles | Passes - Correctly Implemented |
Roles and their functions are enumerated in the stETH contract documentation. |
| Secure Privileged Roles | Passes - Correctly Implemented |
Privileged roles are held by on-chain contracts (the Aragon Agent acting under LDO voting), not off-chain EOAs, and are bounded by dual governance: an emergency-protected timelock plus a stakers veto, with emergency committees able only to delay or block proposals within the timelock window. The design is publicly documented and independently audited (Certora, OpenZeppelin, ChainSecurity). |
| Vulnerability Disclosure Procedure | Passes - Correctly Implemented |
Disclosure runs through the Immunefi program and the Lido security contact. |
| Bug Bounty program | Passes - Correctly Implemented |
Immunefi program live since May 2021 with up to 2,000,000 USD for critical smart contract vulnerabilities. |
| No Transfer or Method Hooks | Passes - Correctly Implemented |
Transfers are plain share reassignments with no ERC-777 style transfer callbacks or method hooks. |
| Document Transaction Limits | Passes - Correctly Implemented |
No per-transfer limits exist; the separate daily staking rate limit is documented. |
| Define Transaction Size Limits | Passes - Correctly Implemented |
stETH imposes no transfer size limits; transfers are unrestricted by amount. |
| Avoid Transfer Fees | Passes - Correctly Implemented |
No transfer fees; the protocol fee is taken from staking rewards at oracle report, not on transfers. |
| Fix Transfer Fees | Not Applicable (passes) |
No transfer fees |
| Restrict Transfers from Blocked or Frozen Accounts | Not Applicable (passes) |
stETH has no blocklist or freeze capability. |
| Document Whether Blocked Accounts Can Receive Transfers | Passes - Correctly Implemented |
stETH has no account blocking or freezing; all accounts can send and receive |
| Make Confidential Transfers Auditable | Not Applicable (passes) |
No confidential transfer functionality. |
| ERC: Implement ERC Token Standards | Partial / Incomplete (fails) |
Implements ERC-20 plus ERC-2612 permit and ERC-1271 signature validation, with one documented deviation scored below. |
| ERC: Document ERC Implementation Upgradability | Passes - Correctly Implemented |
Deployed as an upgradeable Aragon AppProxyUpgradeable with the upgrade path via the DAO documented; implementation at 0x028271E30a695c0527A0C50cA30603feD004cDb0. |
| ERC: Balance Changes Create Transfer Events | Fails |
The daily rebase changes holder balances without emitting Transfer(). Lido documentation states stETH does not emit Transfer() on rebase as ERC-20 requires. The deviation is intentional and trackable via the TokenRebased event and shares, and avoided by wstETH |
| ERC: Mint and Burn as per ERC-5679 | Fails |
Minting occurs via submit() and shares and burning via the Burner contract. They are documented as not emiting Transfer events |
| ERC: No Fallback Function | Justified Exception (passes) |
The stETH implementation (Lido.sol) defines a payable fallback that routes to submit() and mints stETH when ETH is sent directly to the contract. A functional fallback exists by design |
| ERC: Revert Blocked Transfers | Not Applicable (passes) |
No blocking mechanism exists |
| Solana: SPL or 2022 Program Tokens | Not Applicable (passes) |
Not a Solana Token |
The BSSC Token Integration Standard version 2 ("the Standard") establishes technical, governance, and operational requirements intended to help identify and reduce known security risks associated with digital asset integration. BSSC makes the Standard and related assessment framework (the "Assessment Framework") available for use by third parties, including independent evaluators and those conducting self-assessments. Reports prepared using these materials may provide useful information about conformity with the requirements evaluated, but the findings and conclusions are those of the report's preparer, not BSSC.
Conformance to the Standard's requirements can provide meaningful information about a Token's integration-related security practices, but does not guarantee that the Token is secure, free from vulnerabilities, or suitable for any particular purpose. An assessment against the Standard is not necessarily a comprehensive security audit. Conversely, failure to satisfy a requirement does not necessarily establish an exploitable vulnerability. Findings should be considered together with their accompanying explanations, and requirements that have not been evaluated or verified should not be treated as satisfied.
Use of the Standard or Assessment Framework does not, by itself, establish any employment, agency, accreditation, certification, or other relationship between BSSC and the person preparing a report. Unless BSSC expressly states otherwise in writing, BSSC has not selected, supervised, or evaluated the qualifications of that person, nor has it reviewed or verified the report's methods, evidence, findings, or conclusions. BSSC does not adopt, warrant, or stand behind the evaluator, the report, or the Token evaluated. Publication of an illustrative report by BSSC does not itself constitute approval or endorsement. BSSC does not currently operate a certification program for this Standard, and use of these materials confers no BSSC certification or certification mark. Nor does a report constitute a listing or integration decision by any exchange or other organization merely because it uses the Standard.
Neither the Standard nor the Assessment Framework provides financial, investment, or legal advice. No report prepared using these materials should be treated as providing such advice, establishing regulatory compliance, or recommending the purchase, sale, holding, listing, or integration of a Token merely because it was prepared using these materials. BSSC makes no representation concerning any Token's current or future value, investment merits, regulatory status, or performance
Reports prepared using the Assessment Framework may rely on information supplied by Token issuers or other third parties that BSSC has not independently verified, including statements about reserves, asset backing, issuer solvency, or legal rights. Findings are limited to the information reviewed and procedures performed and may become outdated as the Token, its underlying contracts, governance, or operating environment changes. Readers should consider the report preparer's methodology, qualifications, and stated limitations.
Readers should also review BSSC's Disclaimer of Warranty and Liability accompanying the Standard.