Appearance
Audit Reports
These references cover reusable token implementations and their reviewed code revisions. They are not project-specific audits of the current SPACE deployments, bridge configuration or administrative permissions.
xERC20 reference implementation
Creed — Connext xTokens audit (PDF)
The report reviews Connext and Wonderland's reference implementation of ERC-7281, including the xERC20 token, lockbox and factory. Its scope identifies revision 52d1e5c2e8671a05f8020ab61f5e204250d945d5.
See the upstream xERC20 implementation and our xERC20 overview for the token and lockbox mechanics.
BEP-20 / ERC-20 base-library references
BEP-20 specifies a token interface. There is no single implementation shared by all BEP-20 tokens, so a report must identify the library and revision it actually reviewed.
For base ERC-20 contract security research, OpenZeppelin publishes:
- LevelK — OpenZeppelin v2.0 security audit (PDF): a library-wide review, including the base ERC-20 contracts, at revision
dac5bccf803696d9d98d269b8c27c7aac5fa1c5c. - OpenZeppelin's official audit index: reports with their library versions, reviewed commits and scopes.
- OpenZeppelin Contracts Security Center: the library's audit and security-update reference.
These are library references. A match between the deployed SPACE source and a specific audited OpenZeppelin revision has not been established here.
Current contracts
Use Contracts & Routes to find the current token addresses and verified source links. Audit applicability depends on matching that source to the report's scope and reviewed revision; a token-standard name alone does not establish coverage.