Centrifuge has launched V3.3 with an Onchain Execution Policy designed to place programmable investment constraints directly between fund managers and the actions they execute through tokenized pools. The new policy layer allows investors to inspect predefined execution boundaries before depositing while limiting what managers can do without delay or additional oversight.
According to Centrifuge’s official Onchain Execution Policy announcement, each participating pool can install a contract that evaluates manager instructions before they reach the underlying portfolio infrastructure. The objective is to move enforceable parts of an investment mandate closer to the point where portfolio actions actually occur instead of leaving those constraints exclusively in external documents and operating procedures.
The mechanism remains configurable rather than universal. A fund determines which actions are permitted immediately, which thresholds apply and what changes require a delay. Centrifuge does not claim that the policy automatically translates an entire legal mandate into smart-contract logic, and restrictions that depend on information unavailable onchain may still require conventional oversight.
Immediate Execution Sits Alongside Timelocked Controls
Routine actions that remain inside configured limits can execute immediately. Centrifuge gives price updates within predefined size and rate-of-change thresholds as one example, while reallocations between approved venues can also proceed without delay when they remain within the applicable caps.
Actions outside those boundaries enter a timelocked queue. Adding a new venue, asset or counterparty can be subjected to a longer delay, while changes to the policy itself can receive an even longer review period. The structure separates ordinary portfolio management from actions that materially expand the manager’s existing authority.
An independent group of sentinels provides the veto layer. Any single sentinel can cancel a pending authorization without requiring coordination with the rest of the group. Sentinels can stop a queued action but cannot use that role to initiate portfolio transactions themselves, preserving a distinction between execution authority and oversight.
The policy also applies if a manager credential is compromised. An attacker controlling the manager key inherits only the permissions allowed by the policy rather than unrestricted access to the pool. This does not eliminate key-management or smart-contract risk, but it can restrict the actions available to a compromised operational account before assets move outside configured boundaries.
That kind of control becomes more relevant as tokenized funds move from simple issuance into active financial workflows. Centrifuge has already brought institutional fixed-income funds onto Arc, while its deSPXA token can now serve as collateral for USDC borrowing on Base. Once tokenized assets become usable in lending and portfolio management, execution policy becomes a separate infrastructure problem from simply issuing the tokens.
One Policy Can Govern Multichain Fund Activity
Centrifuge V3 uses a hub-and-spoke architecture in which a pool can distribute assets and vault access across multiple blockchains while maintaining accounting and management logic through a central Hub. The Onchain Execution Policy is defined at the pool level on that Hub, allowing the same configured constraints to govern manager activity across the pool’s supported chains.
V3.3 adds other safeguards around that multichain structure. Each pool can now select its own cross-chain adapter set rather than inheriting a universal protocol configuration, while per-chain circuit breakers can limit outbound share transfers if a connected chain is compromised. The release also constrains the effect that abnormal price updates can have on redemption calculations.
Those controls complement Centrifuge’s wider distribution strategy. Its Para integration lets applications embed access to tokenized funds directly inside wallets, extending fund distribution without removing the settlement and redemption conditions of the underlying products. Wider distribution makes consistent portfolio controls more important because the same fund can increasingly interact with users and applications across multiple environments.
Centrifuge says V3.3 underwent independent security reviews and formal-verification work before release. Those assessments reduce specific implementation risks but do not establish that every fund using the framework is automatically safe, compliant or operating under a sufficiently restrictive mandate. The quality of the controls still depends on the parameters each pool chooses.
The development reflects a broader change in tokenization infrastructure. As institutional RWA value has moved beyond simple issuance toward custody, collateral and liquidity workflows, tokenized funds increasingly need operational systems that govern how assets are managed after they reach the blockchain.
Centrifuge V3.3 moves that problem into the execution stack by making selected investment constraints visible and enforceable alongside portfolio actions. Its significance will ultimately depend on how live fund managers configure those policies and whether depositors begin treating machine-verifiable execution limits as a meaningful part of evaluating tokenized investment products.