I recently saw a statistic: over the past year, the total value locked in managed DeFi vaults has grown by more than 350%. The number is quite alarming—not because it’s going up so much, but because it’s rising so fast. The rules controlling these funds are apparently still sitting in some document.

I’m not talking about some small vault—an institutional-grade vault, with amounts often in the hundreds of millions of dollars. The decisions made by the manager directly affect every depositor’s assets. But when you dig into these vaults’ rules, you’ll most likely find a PDF or a Notion page stating that the manager promises not to exceed an X% concentration limit, and that the manager promises to invest only in whitelisted protocols.

A commitment, not an enforcement.

I think this is the most absurd thing about on-chain finance: the money is on-chain, the rules are off-chain. Every unit of fund flow is recorded in the blocks, but the logic that constrains these flows depends on people’s willingness to do the right thing.

@NewtonProtocol What I understand is that it flips this inverted structure the right way around. VaultKit isn’t just another vault product; it’s an SDK that turns vault rules into executable on-chain strategies. When an operator wants to move a transaction, Newton’s strategy engine runs checks first: does this transaction violate concentration limits? Does it hit a sanctions list? Is it outside the authorized scope? If any condition fails, the transaction is blocked directly—not a post-fact alert, but something that can’t even pass in the first place.

I’ve seen VaultKit integrate several interesting modules. Chainalysis handles sanctions screening, RedStone provides real-time price data for risk-control threshold decisions, Webacy provides security scoring, and vaults.fyi offers vault transparency. These aren’t loose collaboration relationships—these are data sources for a strategy engine: use the Rego policy language to write the rules, have the WASM oracle pull the on-chain and off-chain data into the chain, have the EigenLayer AVS operator network independently evaluate, aggregate BLS signatures into a consensus proof, and finally have on-chain verifiers check the proof to allow or block it.

One thing I care about a lot is that this verification process is verifiable. Each transaction corresponds to a signed timestamp proof, and both the deployer and the regulator can look it up on Newton Explorer.

I wonder why this kind of thing is only showing up now—it may have to do with the industry’s stage of development. A few years ago, DeFi was still figuring out whether it could work at all. Vault TVL grew from zero to tens of billions, and everyone neglected the risk-control infrastructure. But now institutional money has truly entered: stablecoin monthly transfer volume exceeds $4 trillion, tokenized real-world assets exceed $25 billion, and compliance costs are $206 billion globally each year. The money is there, but the control layer hasn’t caught up.

#Newt Starting from vaults is, I think, the right path. Vaults are the most rule-dense and power-concentrated scenario in on-chain finance—one sentence from the operator can reallocate positions worth hundreds of millions. If the rules in this scenario can move from documents to code, from commitments to enforcement, then what follows—RWA, stablecoins, AI agents—are all extensions of the same authorization layer.

@NewtonProtocol The VaultKit is already running on Base and the Ethereum mainnet. I think what’s worth paying attention to isn’t how many vaults it manages today, but that it defines something new: policies aren’t promises written on paper—they’re enforceable commands written on-chain. $NEWT