ERIIKA NOVA

I didn’t expect sanctions screening to make me think this much about trust.
At first, it looked simple enough. There are sanctioned wallets, or at least wallets believed to be connected to sanctioned people or organizations. An app checks those wallets before letting a transaction go through. If something looks wrong, it blocks the transaction.
That is the easy version.
But the more I thought about it, the less simple it felt.
Because the real question is not only whether a wallet is risky. The real question is who gets to decide that, and how much of that decision the rest of the system can actually see.
Most applications today solve this by using a compliance API. Before a transaction reaches the contract, the app asks an outside service whether the address is safe. The service responds with a result, and the app trusts it.
That works. It is fast, familiar, and probably the easiest way to stay aligned with regulations.
But there is something uncomfortable about it too.
The protocol is not really checking the facts itself. It is trusting another system to check them. And in a space that talks so much about verification, that feels like a strange place to stop verifying.
I don’t say that as criticism only. Some things are genuinely hard to verify onchain. A blockchain cannot understand global politics. It cannot read sanctions updates, connect real-world entities to wallet clusters, or know when ownership has changed behind the scenes.
So outside information is necessary.
The question is what form that outside information should take.
Should it arrive as a simple answer from an API?
Or should it arrive as evidence that can be checked more openly?
This is where Newton Protocol becomes interesting to me.
Not because it removes trust completely. I don’t think any system can do that here. But because it seems to ask a better question: instead of blindly accepting an outside decision, can a protocol verify that certain authorization conditions have been met?
That difference matters.
An API says, “Trust me, this passed.”
Verifiable authorization says, “Here is why this passed.”
That does not make the second model perfect. Someone still has to define the rules. Someone still has to provide attestations. Someone still has to decide which sources are acceptable. And those decisions can carry bias, mistakes, or pressure from institutions.
But at least the trust is less hidden.
That may be the most important part.
A lot of crypto conversations pretend the goal is to remove trust entirely. I think that is too clean. In reality, trust usually gets moved around. Sometimes it becomes code. Sometimes it becomes governance. Sometimes it becomes an API nobody questions until something breaks.
Sanctions screening shows that clearly.
With API-based screening, the weak point is not only censorship. It is dependence. The application depends on a service whose reasoning may not be visible. If that service changes its methods, gets something wrong, or becomes unavailable, the system has limited ways to respond.
With verifiable authorization, the problem does not disappear. It changes shape. The system becomes more transparent, but also more complex. Policies need to be written clearly. Proofs need to be generated. Updates need governance. Mistakes can still happen, just in a different layer.
That is why I don’t see this as a simple battle between old compliance APIs and new crypto-native infrastructure.
It is more like a question of what kind of trust we are willing to live with.
Hidden trust is easier.
Visible trust is harder, but healthier.
The more I think about it, the more I feel that sanctions screening is only one example of a much bigger issue. Blockchains are good at verifying what happens inside their own world. But whenever they touch real-world facts, they need help from somewhere else.
That “somewhere else” is where the real design choice begins.
Maybe the future is not about pretending compliance can become fully trustless. Maybe it is about making each trusted step easier to inspect, challenge, and understand.
And maybe that is the part we should pay more attention to: not just whether a transaction is allowed, but whether the reason behind that decision can be seen at all.
@NewtonProtocol #Newt $NEWT

The thing that stayed with me after looking at Newton Protocol was not the usual promise of verification. It was the awkward question sitting behind it.
What does it actually mean for an AI agent to “follow the rules”?
Newton is useful because it tries to make AI behavior provable. An agent is given a policy, it acts within that policy, and later there can be evidence that it did not cross the line. That matters. In a world where AI agents may move funds, execute trades, approve actions, or interact with contracts, “trust me, it behaved correctly” is not enough.
But verification only proves a very specific thing.
It can show that the agent followed the rulebook.
It cannot show that the rulebook was good.
That sounds simple, but it changes how I think about the whole project. Imagine a company using an AI agent to handle refunds. The agent follows every internal policy exactly. It rejects late claims, approves eligible ones, escalates edge cases, and produces proof for every decision.
From a technical perspective, everything worked.
But what if the refund policy was unfair? What if it ignored situations a human support worker would have understood immediately? What if the rules were written quickly, by people trying to reduce costs rather than solve customer problems?
Newton could prove the agent obeyed.
It could not prove the company had good judgment.
That is not a failure of Newton. It may actually be one of the most honest things about the design. The protocol does not magically decide what is fair, wise, or context-aware. It deals with execution. Humans still have to deal with meaning.
The danger is that people may forget this distinction. Once something becomes verifiable, it starts to feel legitimate. A clean proof can make a bad process look disciplined. An audit trail can make a poor decision look responsible.
But some of the worst decisions in the world were made by people who followed procedure.
This is where Newton becomes more interesting to me. It does not remove trust. It moves trust to a different place. Instead of asking, “Did the AI secretly break the rules?” we start asking, “Who wrote these rules, and were they thoughtful enough?”
That second question is harder.
Rules get old. Markets change. Users behave in unexpected ways. A policy that made sense three months ago can become dangerous today. An AI agent may keep following it perfectly while reality has already moved on.
So the protocol can give us confidence in compliance, but not confidence in wisdom.
That boundary matters.
The documentation, to its credit, seems more focused on verifiable execution than on pretending to solve every AI governance problem. That restraint is important. Still, the unresolved part is where the real tension lives.
Who updates the policies?
Who notices when the rules are no longer working?
Who is responsible when an agent does exactly what it was told and the result is still wrong?
Those are not cryptographic questions. They are human ones.
Maybe Newton’s biggest contribution is not that it makes AI agents “trustless.” Maybe it makes the remaining trust more visible. If execution can be proven, then weak governance has fewer places to hide.
And that leaves us with a less comfortable but more useful question:
As AI agents become easier to verify, will we become better at writing the rules they follow?
@NewtonProtocol #Newt $NEWT