← Projects
CustodyPolicyQuorumTreasurySecurity

Narrative hub linking ephemeral signing, air-gapped confirmation, and quorum treasury flows. Framing for how policy and controls sit under digital-asset movement, not a finished production custody product.

Technical Narrative hub linking the 1Password ephemeral EVM signer, air-gap Pico signer, and Solana treasury vault into a single treasury-policy walkthrough: whitelist, limits, dual approval, cooldown, and offline or ephemeral signed transactions.

Problem

Institutional digital-asset treasuries need enforceable policy before funds move: who can propose, who must approve, what counterparties and sizes are allowed, how long to wait, and how keys stay out of always-on hosts.

What I designed and implemented

  • Unified narrative across three existing demos
  • Policy vocabulary mapped to signing, quorum, and approval controls
  • Walkthrough of whitelist, limits, dual approval, cooldown, and offline or ephemeral signing

Architecture

  • Ephemeral host signing with full field review before a test key is touched (1Password Ephemeral EVM Signer)
  • Offline device confirmation for transaction digests over USB with no network on the signer (Air-Gap TX Signer)
  • On-chain dual approval, recipient binding, and cooldown before treasury execution (Solana Treasury Vault)

Engineering decisions

  • Tell one custody story instead of three disconnected cards
  • Use institutional language: policy, quorum, approval, cooldown
  • Keep each repo independent so demos stay focused

Verification and testing

  • Each linked project carries its own tests and demos
  • This hub is narrative packaging; runtime verification lives in the child projects

Limitations and what is simulated

  • Learning and demo controls, not a production custody platform
  • No claim of Fireblocks, Anchorage, or Safe feature parity

Production differences

  • Production custody adds HSM or MPC key ceremonies, formal policy engines, audit export, and regulated operating procedures