Comparison of Fund Control Models
Published 7/14/2026, 12:20:52 PM
As of July 14, 2026, Tempo’s Receive Policies (introduced via the TIP-403 protocol and the T6 network upgrade) represent a fundamental shift in crypto payment fund control. Traditionally, blockchain accounts are passive recipients—any token can be sent to any address without the receiver's consent. Tempo's Receive Policies change this by giving accounts protocol-level autonomy to filter, block, or redirect incoming funds before they are credited to a balance [Source: https://docs.tempo.xyz/docs/protocol/tip403/overview].
Comparison of Fund Control Models
The core innovation is the transition from passive acceptance to active policy enforcement. Instead of a binary "success" or "revert" state, Tempo introduces a third state: Blocked & Held.
| Feature | Traditional Crypto Payments | Tempo with Receive Policies |
|---|---|---|
| Inbound Control | None; anyone can send any token. | Active filtering by sender, token type, or amount. |
| Failed Deposits | Often lost (e.g., wrong token sent to exchange). | Recoverable via claim receipts and recovery authorities. |
| Compliance | Reactive (freeze funds after they arrive). | Proactive (block transfers from sanctioned addresses). |
| Finality | Transaction success = funds credited. | Transaction success = Policy check, then credit or hold. |
[Source: https://docs.tempo.xyz/docs/protocol/tip403/spec]
Key Mechanisms of Receive Policies
1. The ReceivePolicyGuard
When a transfer violates an account's policy, the funds are not returned to the sender or lost. Instead, they are redirected to a protocol-level contract called the ReceivePolicyGuard. This ensures the sender's transaction still "succeeds" at the network level (maintaining deterministic finality), but the receiver's main balance remains untouched by unauthorized assets [Source: https://docs.tempo.xyz/docs/protocol/tip403/spec].
2. Claim Receipts & Recovery
When a transfer is blocked, the system emits a TransferBlocked event and generates an ABI-encoded Claim Receipt.
- Recovery Authority: Account owners can designate specific addresses (e.g., a compliance officer or a cold wallet) as recovery authorities.
- Actionable Outcomes: The authority can use the receipt to claim (release to the intended recipient), reroute (send to a different internal account), or burn (if authorized) the held funds [Source: https://getfoundry.sh/reference/cast/receive-policy].
3. TIP-403 Policy Registry
Users manage their controls through a standardized registry that supports:
- Whitelists: Only allowing transfers from KYC-verified counterparties.
- Blacklists: Automatically blocking known scam addresses or sanctioned entities.
- Token Filtering: Restricting an account to only accept specific stablecoins (e.g., only USDC or EURT), preventing "dusting" attacks or accidental deposits of unsupported assets [Source: https://tempo.xyz/learn].
Strategic Impact for Enterprises
For financial institutions and large-scale merchants, this feature solves the "unsolicited funds" problem. It allows them to:
- Maintain Clean Ledgers: Prevent unauthorized or "tainted" tokens from ever appearing in their primary treasury balances [Source: https://blockdaemon.com/blog/tempo-blockchain-analysis].
- Automate Compliance: Integrate real-time AML/KYC checks directly into the protocol layer via partners like Chainalysis and TRM Labs [Source: https://tempo.xyz/learn].
- Reduce Support Overhead: Convert "wrong token" deposit errors into self-service recovery workflows rather than manual database corrections [Source: https://getfoundry.sh/reference/cast/receive-policy].
Technical Implementation
Developers manage these policies using the cast receive-policy command suite:
cast receive-policy set: Configures the sender and token policy IDs for an account.cast receive-policy validate: Pre-checks if a specific transfer would be credited or held.cast receive-policy claim: Releases held funds from theReceivePolicyGuardto a target address [Source: https://getfoundry.sh/reference/cast/receive-policy].
Conclusion: Tempo's Receive Policies transform crypto wallets from passive buckets into programmable gateways, allowing users to enforce compliance and security rules at the protocol level before funds are ever accepted into their balance. While the T6 upgrade is live, independent third-party verification of specific institutional adoption rates remains an open area for further research.