Step 7 and last of the r/moul/demo walkthrough: a time-locked vault over the
GRC20 token from grc20.
Withdrawing is deliberately two steps, so that a stolen key does not drain the
vault in one transaction:
1funcDeposit(currealm,amountuint,recoverAddressaddress)// caller -> vault2funcUnvault(currealm,amountuint)// arm the timer3funcRedeem(currealm,amountuint)// after the lock4funcRecover(currealm,targetaddress)// escape hatch
Unvault moves an amount from vaulted to pending and stamps
unlockAt = ChainHeight() + 100. Redeem refuses until the chain passes that
height. In between, the depositor (or whoever is watching) can call Recover
to push the still-locked balance to the recovery address recorded at deposit
time. That is the pattern: a withdrawal announces itself, and the announcement
window is when a theft can be reversed.
Deposited tokens live at the realm's own address (cur.Address()), which is
what makes the vault custodial rather than an accounting fiction.
What is wrong with it on purpose
This is a demo, and two things would sink it in production:
Recover has no caller check. Anyone can call Recover(target) for any
target. It only ever pays out to the address the target itself recorded, so
it cannot steal, but it is a free denial of service: a bystander can rewind
anyone's deposit at will.
Only Unvault/Redeem are covered by tests.Recover has none, flagged
as a TODO in the test file.
Read it for the two-step withdrawal shape, not as a vault to deploy. (Note that
r/moul/x/daily/vault is a different thing entirely: a key-value store, not a
token vault.)
Part of moul/gno-contracts — moul's versioned gno.land contracts. See the repository for the full catalog, build/test tooling, and usage.
On mainnet:
Dependency graph:
⚠️ Disclaimer: provided as-is, without warranty; not security-audited. Full disclaimer: DISCLAIMER.
Overview
Package vault demonstrates a minimal time-locked token vault built on top of the grc20 token package. Deposited tokens are held at the realm's own address; withdrawing them is a two-step process: Unvault marks an amount for withdrawal and starts a lock timer, then (once the lock elapses) Redeem moves the tokens back to the depositor.