DarkscanSafe custody

Custody builder

The Safe path is built as a transaction packet before any custody claim.

The current configured role target is not a Safe. This page publishes the Safe construction route, official contract checks, signer-policy requirements, and the next role-transfer command once a Safe address exists.

Required signer policy

Production custody requires at least three owners with a threshold of two or higher. The preferred long-lived policy is three-of-five.

Claim boundary

Safe deployment alone is not DRK role custody. DRK roles must be granted to the Safe and deployer roles revoked before multisig custody can be claimed.

Evidence

Open the build packet and custody readiness proof.

Execution order

Custody is only complete after mined Safe and role receipts.

First deploy or provide a real Ethereum Safe contract. Then generate the DRK role-transfer plan for that Safe. Then execute and publish mined grant and revoke receipts. Until those receipts exist, DRK role custody remains unresolved.