EVM Contract Status Lifecycle

This lifecycle tracks the status of the off-chain contract record in our database as it moves from creation to deployment and finally to an archived state.

Lifecycle Diagram

PENDING_DEPLOYMENT → DEPLOYMENT_IN_PROGRESS → ACTIVE → ARCHIVED

Status Definitions

Status	Description
PENDING_DEPLOYMENT	The Fund has been approved, and a contract record has been created, but it has not yet been sent to the blockchain.
DEPLOYMENT_IN_PROGRESS	A deployment transaction has been broadcast to the network. The system is awaiting confirmation.
ACTIVE	The contract is successfully deployed, its address is confirmed, and it is fully operational.
ARCHIVED	An approved fund-close or repayment decision applies under the owning EVM service's policy, and this contract record is archived according to that policy. See Offer State Lifecycle.

Key Transitions

• Deploy Contract (PENDING_DEPLOYMENT → DEPLOYMENT_IN_PROGRESS)

  • Trigger: An administrator initiates the deployment for a legally approved Fund.

  • Action: The system broadcasts the deployment transaction to the specified network, stores the resulting deployment_tx_hash, and updates the status.

• Confirm Deployment (DEPLOYMENT_IN_PROGRESS → ACTIVE)

  • Trigger: A background service (blockchain listener) confirms the deployment transaction has been successfully mined.

  • Action: The system parses the transaction receipt to get the contract address, stores it, and updates the status to ACTIVE.

• Archive Contract (ACTIVE → ARCHIVED)

  • Trigger: An approved fund-close or repayment decision is identified under the owning EVM service's policy.

  • Action: The owning EVM service records the contract as ARCHIVED under that policy. Archiving requires an external trigger and does not create a new Offer state.