@resurrect-protocol/contracts
v0.6.0
Published
Canonical immutable Solidity contracts, ABIs, and Ethereum deployments for Resurrect
Readme
@resurrect-protocol/contracts
Canonical Resurrect Solidity sources, ABIs, and Ethereum mainnet deployment records.
npm install @resurrect-protocol/contractsBeacon
import beaconAbi from '@resurrect-protocol/contracts/abi/ResurrectBeaconV1.json' with { type: 'json' }
import ethereumMainnet from '@resurrect-protocol/contracts/deployments/ethereum-mainnet.json' with { type: 'json' }Solidity tools can import @resurrect-protocol/contracts/src/ResurrectBeaconV1.sol. The permissionless beacon exposes exactly VERSION, MAX_TTL, MAX_RECORD_BYTES, and announce. It has no owner, administrator, allowlist, pause, upgrade, withdrawal, or peer-storage path. Despite the name, it is a rendezvous beacon rather than an upgradeable proxy beacon.
The canonical deployment is 0x136c191B5e6541532E42Ecd7C719C29D7ecdf468 on Ethereum mainnet, chain ID 1, receipt block 25943058. Its deployment JSON includes the transaction, deployer, compiler settings, bytecode hashes, Etherscan and Sourcify links, and audit metadata.
Applications may use the canonical deployment or deploy the exact source elsewhere, but must pin the chosen chain, address, deployment block, namespace, and constants. A shared stateless beacon does not create a shared peer list. RPC providers remain caller-selected, and an event remains an untrusted discovery hint until the signed record, sequence, expiry, endpoints, and application handshake are verified.
OneDollarAudit job #904 reviewed the exact canonical address and produced an immutable IPFS report with 0 Critical, 0 High, 0 Medium, 2 Low, and 1 Informational finding.
Immutable explorer
import siteAbi from '@resurrect-protocol/contracts/abi/ResurrectOnchainSite.json' with { type: 'json' }
import explorerMainnet from '@resurrect-protocol/contracts/deployments/ethereum-mainnet-explorer.json' with { type: 'json' }Solidity tools can import @resurrect-protocol/contracts/src/ResurrectOnchainSite.sol. The contract implements ERC-5219 and the ERC-6944 5219 resolve mode, reconstructing immutable resources from bytecode-storage contracts. It has no owner, mutable storage, or upgrade path.
The source-verified production router is 0x14765f12a7f068EDf42dF4920fd5170ADBa73306 on Ethereum mainnet at block 25943864. Its deployment JSON records the 24 data contracts, all 25 transaction hashes and blocks, every resource hash and payload length, the router runtime and manifest hashes, compiler settings, Etherscan and Sourcify verification, deployment cost, gateway URLs, and runtime verification results. The embedded explorer uses the canonical ResurrectBeaconV1 at 0x136c191B5e6541532E42Ecd7C719C29D7ecdf468.
Open it through:
https://resurrect.wei.limo/— primary human-readable entry point;https://resurrect.wei.domains/— alternative name gateway;web3://resurrect.wei/;web3://0x14765f12a7f068EDf42dF4920fd5170ADBa73306:1/;https://0x14765f12a7f068edf42df4920fd5170adba73306.w3eth.io/; orhttps://0x14765f12a7f068edf42df4920fd5170adba73306.1.w3link.io/.
The deployment JSON also records the WNS contract, resurrect.wei token ID,
owner, expiry, resolved address, ERC-6821 contentcontract, registration and
configuration transactions, cost, and byte-for-byte WNS gateway verification.
Consumers should independently compare deployed code and resources with the pinned source and build artifact before relying on them.
License
Resurrect's original source and deployment metadata are licensed under MIT. Dependency licenses remain their own.
