Contract Directory
(Explorer-First Reference Index)
2.1 Contract Directory
This page lists all deployed contracts that compose the Modulexo system.
All addresses are publicly verifiable on-chain.
The directory is structured by network.
I. Execution Networks
Each execution network includes:
These contracts form the Recycle Execution Layer.
Polygon (Chain ID: 137)
Component
Address
Role
Owner
Governance
BNB Chain (Chain ID: 56)
Component
Address
Role
Owner
Governance
II. Treasury Layer (Ethereum Mainnet)
Ethereum hosts the Fund and governance contracts.
Ethereum (Chain ID: 1)
Component
Address
Role
Owner
Governance
III. Ownership State
Ownership must be verified directly on-chain via:
Possible states:
• Private Owner
• Timelock Controlled
• Renounced
If owner() equals Timelock address:
Private operator control has been removed.
If owner() equals zero address:
Contract is immutable and renounced.
IV. Parameter Control
To verify parameter mutability:
RecyclingEngine:
Ledger:
Fund:
Any parameter changes emit events:
Each contract exposes:
or can be verified via deployment block on explorer.
Deployment block numbers should be included here for transparency.
Example:
RecyclingEngine (Polygon)
VI. Contract Verification Standard
All listed contracts must be:
• Verified on block explorer
• ABI available
• Ownership state publicly readable
If a contract is upgradeable via proxy, the following must be listed:
• Proxy address
• Implementation address
• Admin address
This must be explicit.
VII. Separation of Layers
Execution Layer (L2):
Handles recycle mechanics.
Treasury Layer (L1):
Handles governance and aggregated value.
These layers are independent but optionally connected via FeeVault + BridgeAdapter.
Last updated
