The other day I tried to answer a very familiar question.
"In the end, who is the Newton Protocol Vault SDK really for?"
At first, I was also looking for an answer similar to most other projects. Are they targeting financial institutions? Or AI Agents? Or DeFi Whales?
But the more I looked, the more I felt that none of these groups could adequately represent the entire product.
If it only serves the Institution, why is the Newton Protocol investing in the TypeScript SDK and tools for integrating AI Agents? If it only serves AI Agents, then why does the project put so much effort into Compliance and Risk Control? And if it’s meant for DeFi Whales, that also isn’t quite right—because many of the Vault SDK’s designs are aimed at workflows with an organizational nature.
I started to think maybe I’m asking the wrong question.
The Vault SDK doesn’t choose the user.
The Vault SDK chooses the Bottleneck.
It sounds similar, but in reality it’s very different.
In a Bear Market, the biggest Bottleneck isn’t profit. It’s Compliance and Survival. At this time, financial organizations become the most suitable user group—not because Newton Protocol was specifically designed for them, but because they are the ones who have the most painful problems with controlling assets and meeting governance requirements.
When DeFi enters a phase of strong growth, the Bottleneck shifts again. The market no longer lacks opportunities to make profits, but it lacks a way to allocate capital to new strategies while still retaining control. At that point, DeFi Whales and DAOs become the group that feels the value of the Vault SDK most clearly.
Then if we move into the AI Agent operating phase, where more and more assets are on-chain, the Bottleneck keeps shifting. The issue is no longer Compliance or Yield. What people worry about most then is how to make sure the Agent can operate automatically without exceeding the permissions granted to it. At that point, AI Developers become the most suitable user group.
What’s interesting is that across all three stages, the Vault SDK almost never needs to become three different products.
What changes is the market’s Bottleneck.
And the Bottleneck determines who will find this product most valuable.
That’s also why I don’t like the way many people try to find a fixed ICP for Newton Protocol.
Infrastructure is different from Application.
Applications usually have to find the right user.
Infrastructure, however, has to stand exactly where the market is congested.
Today, the point of stagnation is Compliance.
Tomorrow is about Capital Protection.
In a few years, it could be about AI Guardrails.
The user changes with each cycle, but the core problem that the Vault SDK solves remains unchanged: how can assets be delegated to operate without losing control rights?
So if I had to describe the Vault SDK in one sentence, I wouldn’t call it a product for Institutions, Whales, or AI Agents.
I’ll call it an infrastructure that’s always shifting according to the Market Bottleneck.
Because in the end, Newton Protocol doesn’t win by choosing the right user.
@NewtonProtocol It wins if it always stands in the place where the market hurts most.
$SYN
$NEWT #Newt