Operational Status
0.2 Operational Status
Deployment State
Modulexo is deployed as a set of on-chain contracts across supported networks.
Each network instance includes:
RecycleAssetRegistry
SponsorshipLedger
RecyclingEngine
Fee Router
(Optional) FeeVault
(On Ethereum) Fund + Governor + Timelock
All contract interactions are executed directly on-chain. There are no upgradeable proxies in the execution path unless explicitly stated in the Contract Directory.
Contract State Verification
Operational status can be independently verified through the following read-only functions:
RecyclingEngine
deployedAt()owner()pendingOwner()registry()ledger()router()baseWeightPriceWei()decayPerDayPPM()linearGrowthSlopeWeiPerDay()
These values determine:
Deployment timestamp
Control authority
Parameter configuration
Connected contract addresses
SponsorshipLedger
engine()owner()blackHole()
These confirm:
Execution binding
Administrative control
Burn routing address
Fund (Ethereum)
owner()shareBalances(address)Governor address
Timelock address
These confirm:
Governance structure
Voting weight basis
Execution authority
Governance Status
On Ethereum, the Fund is governed via:
Weighted Governor → Timelock → Fund
Governance state is verifiable through:
Voting period
Quorum
Proposal threshold
Timelock execution delay
All parameter changes must pass governance once ownership is transferred to Timelock.
Parameter Mutability
The following parameters may be adjustable if ownership is active:
RecyclingEngine:
setParams(baseWeightPriceWei, decayPerDayPPM, linearGrowthSlopeWeiPerDay)
Ledger:
setEngine()
Ownership:
transferOwnership()renounceOwnership()
If ownership has been renounced or transferred to governance, these functions cannot be called by private operators.
This is publicly verifiable.
Current Operational Mode
Modulexo operates under one of the following states:
Owner-controlled
Governance-controlled
Frozen (ownership renounced)
The current mode per network is listed in the Contract Directory.
Transparency Policy
Modulexo does not publish status claims that cannot be verified through:
Direct contract reads
Event logs
Explorer links
UI indicators reflect contract state and do not override it.
Last updated