Neel_Proshun_DXC

I want to be straightforward about how I approached this campaign, because I think it matters for how you read the conclusion.
I didn't come in trying to sell $NEWT . I came in trying to figure out if the "verifiable on-chain automation layer" pitch was substance or just another category name someone invented for a pitch deck. Fourteen days of writing, reading the docs, checking the numbers against what was claimed here's where I landed.
The core idea holds up better than I expected
The pre-settlement check is the actual innovation, not the branding around it. Policy enforcement happening before a transaction settles, instead of after checked against RedStone's live pricing and Credora's risk data isn't a small architectural choice. Most automation in DeFi still fails after the fact. You find out the bot did something dumb when you check your balance, not before it happens. Newton's whole design bet is that you can catch it before settlement instead of cleaning up after.
Whether that bet pays off depends entirely on adoption and stress-testing under real volume, which 14 days of writing can't tell you. Nobody's numbers can tell you that yet.
The inherited scale is real, and that's unusual
A lot of infrastructure projects launch with a narrative about future scale. Newton launched already sitting inside Magic Labs' 57M wallets and 200K developers. That's not a projection, it's a starting point. Whether that translates into actual usage of the policy engine specifically versus just existing alongside it is the open question I'd want answered before day 30, not day 14.
The valuation gap is still unresolved for me
I flagged this on day 10 and I still don't have a clean answer. A ~$12.6M market cap against 1.1M+ registered users and infrastructure integrated into a 57M-wallet ecosystem is either a mispricing or a signal that the market doesn't believe the usage numbers convert into value yet. I lean toward the second explanation, but I want to say clearly that's a guess, not a conclusion.
What I'd still want to see
Real transaction volume through the policy engine under adverse conditions. Not a controlled beta environment an actual liquidity event, an actual attempted exploit, something that tests whether "can't" really means can't. The June unlocks and the next one on July 24 are also worth watching, since unlock pressure tends to be where projects with good fundamentals still see price disconnect from usage.
I came into this skeptical. I'm leaving it cautiously interested, with a specific list of things I still need to see before that turns into conviction.
What would it take for you?
#Newt @NewtonProtocol $NEWT
$SYN $T

ニュートンの複製が難しいのは、技術...ではありません。
私は、このことを繰り返し思い出します。論文をストレステストしようとするときにです。暗号領域では、コードがフォークされます。ホワイトペーパーはコピーされます。技術的な優位性は、ほぼ他のどの業界よりも早く目減りします。ニュートンの防御力がzkPermissionsのアーキテクチャか、事前決済ポリシーレイヤーだけにあるのであれば、十分に資金のある競合は18か月でそのギャップを埋めることができるでしょう。
しかし、ここでの堀（モート）は主に技術的なものではありません。構造的なものです。そして、構造的な堀は、関係性や認証、さらに10年にわたるインフラの信頼はフォークできないため、模倣がずっと難しくなります。

Vaults first. Then RWAs. Then AI agents...
The first time I saw this progression laid out, I almost skipped past it. Roadmaps in crypto are usually just ambition dressed up as strategy. But the more I sat with this one, the more the sequence felt like it was actually doing something each stage creating the conditions the next one requires.
You can't start with fully autonomous AI agents managing complex financial positions. Not in 2026. The regulatory environment isn't ready. Institutional risk frameworks aren't designed for it. And the trust —the kind of trust that comes from watching a system perform under real conditions, with real money, across enough edge cases to know what it does when things go wrong that trust takes time to accumulate.
So you start where trust already exists. Vaults. Structured capital. Rule-bound execution that institutional participants already understand. The authorization layer in this context has to be precise and auditable every transaction checked against programmable rules before settlement, every decision producing a signed attestation. That's Newton's pre-settlement policy enforcement doing exactly what vaults require.
Then RWAs. Real-world assets introduce a different kind of complexity. Credit risk that changes. Regulatory requirements that vary by jurisdiction. Counterparties that exist off-chain. The policy layer has to handle all of that which is why Credora risk ratings integrated into pre-settlement checks matter here more than anywhere else. The enforcement has to be as sophisticated as the asset class.
Then AI agents. Autonomous systems executing strategies without human approval at each step. By this point, the authorization infrastructure has been stress-tested across two prior stages. The slashing mechanics, the EigenLayer security model, the RedStone price data integration, the zkPermissions boundaries all of it has been running in production long enough to know what holds and what doesn't.
That's not a coincidence. That's a sequencing strategy.
The numbers suggest the first stage is already working. 1.1M+ registered users. 600K+ verified agent transactions. 350K+ activated agents. Mainnet Beta live since June 23, 2026 with VaultKit SDK. Newton SDK on NPM one integration, the whole policy layer available to the 200K+ developers in the Magic Labs ecosystem.
The infrastructure runs as an EigenLayer AVS $12B+ in restaked ETH, 2,000+ operators securing the network. Magic Labs behind it, 57M+ wallets, SOC 2 Type 2 and HIPAA certified. PayPal Ventures and Polygon backing it.
On supply — 139M NEWT unlocked June 24, Core Contributors unlock coming July 24. At $0.04 and $12.6M market cap, the near-term pressure is real. dPoS staking at 8.5% APY with 14-day unbonding and slashing for misbehavior gives operators skin in the game, but thin liquidity means unlock events matter more than they would at higher market caps.
Worth being honest about that rather than burying it.
The roadmap makes structural sense to me. The sequencing is right. What I'm still working out is timing each stage transition depends on factors outside the protocol's direct control. Regulatory clarity on RWAs. Institutional appetite for AI agent automation. Market conditions that make the unlock schedule manageable rather than suppressive.
So here's what I'm genuinely unsure about...
Where on that roadmap — vaults, RWAs, or AI agents — do you think the real value actually concentrates? And does the answer change depending on which stage you think we're actually in right now?
#Newt @NewtonProtocol $NEAR $NEWT $EVAA

I've been thinking about what happens when autonomous agents become the normal.
Not as a distant possibility. As something already in motion.
350K+ activated agents running on Newton right now. 600K+ verified transactions executed without a human approving each step. The agentic economy isn't a roadmap item it's already operating at a scale that makes the philosophical question practical.
If agents can act independently, what stops them from doing something you didn't intend?
Most people answer that question with trust. You trust the developer who built the agent. You trust the logic they wrote. You trust that the edge cases were thought through and the incentives are aligned. That's the default model for almost every automation system in crypto right now.
But trust is a fragile foundation when agents are executing financial transactions autonomously at scale. Trust doesn't have a slashing condition. Trust doesn't produce a signed attestation. Trust doesn't enforce anything it just assumes.
Newton's authorization layer is the alternative to trust as enforcement.
zkPermissions create cryptographic boundaries that define exactly what an agent can do. Not what it should do what it's structurally capable of doing within the execution environment. Outside that scope, execution doesn't proceed. The boundary isn't advisory. It's enforced at the protocol layer before settlement.
Every policy check runs against RedStone live price data — 1,000+ assets, 100+ chains, zero mispricing events and Credora risk ratings before anything settles. Each check produces a signed attestation. A verifiable record of what the agent knew, what conditions it evaluated, and what constraints it operated inside at the moment it acted.
The network runs as an EigenLayer AVS $12B+ in restaked ETH, 2,000+ operators securing the infrastructure. Magic Labs behind it, 57M+ wallets, 200K+ developers, SOC 2 Type 2 certified. This isn't a new team asking for trust. It's an existing infrastructure provider extending a system that already runs at production scale.
1.1M+ registered users. Mainnet Beta live since June 23, 2026. VaultKit SDK available. Newton SDK on NPM one integration, policy enforcement live for any developer in the ecosystem.
On tokenomics — worth being direct about the timing. 139M NEWT unlocked June 24, roughly 37% of circulating supply. Core Contributors allocation unlocks July 24. At $0.04 and $12.6M market cap, consecutive unlocks on thin liquidity create real ceiling pressure that has nothing to do with whether the protocol is performing. That tension is worth sitting with honestly rather than explaining away.
dPoS staking at 8.5% APY with 14-day unbonding and slashing for misbehavior means operators carry genuine downside exposure — not just upside incentives. Bad behavior has a cost built into the economic model, not just a reputational one.
But here's the question I keep coming back to.
As agents become more capable and more autonomous — acting, paying, verifying, executing without human approval at each step the authorization layer becomes the last meaningful point of human control in the system.
What happens to human agency when agents no longer need our approval to act and the only thing standing between intention and execution is a cryptographic policy we set once and rarely revisit?
#NEWT @NewtonProtocol #Newt $NEWT $POWER $EVAA

I have been gazing at Newton's numbers for a week.
Not because of their bad. However, the price does not match and I can't explain why.
$12.6M market cap. $0.04. These are preliminary figures. It's the kind of valuation that you observe in projects that will be differentiated from the first real users and were also in the process of running a testnet to prove the concept that it's working as is supposed to be.
Then I check the rest of it out.
1.1M+ registered users. 600K trusted agent transactions. 350K+ activated agents. Mainnet Beta has been live since 23rd June 2026. It came with VaultKit SDK.It is part of the VaultKit SDK during release. Embedded on policy enforcement layer is RedStone and Credora. Two teams of magic Labs behind it — 57M wallets, 200K developers, infrastructure that handled $3B+ ELEC night volume for Polymarket.
That's by no means a project funded at the beginning. That's a production network that a lot of protocols have been going to for years to get to.
This is a speculation on an yet-to-be event, set up for a price.
I've been as much a wrong man on one side as the other trying to explain that difference (apprehending it as I thought and actually, I realized I hadn't and then again the other way). I've referred to undervalued and witnessed their persisting for far longer than any thesis could have endured. I also have written off the supply pressure as a short-term thing and proved correct on that one as well.
In the mechanical explanation here it's true. With thin liquidity at $0.04 per token, 139M NEWT were unlocked June 24 representing some $7.6M. That kind of supply event, however, brings a ceiling which is not related to network performance. If there are continuous unlock events, price can remain below fundamental value for months without shifting.
And there's yet another coming. July 24—Core Contributors allocation. A particular type of headwind is 2 unlocks in a row on a relatively illiquid token. Sometimes or often the market may just be right. Perhaps it was simply rightly valuing the short-term supply situations while the underlying network continued to expand under it.
The positive interpretation is that. The cynical version of that is that the number of users isn't always the best indicator of value: 1.1M registered users at $0.04 tells you more about how they're behaving — how well they're retaining, how well they're monetizing, and/or how big their addressable market is — than just the number of users.
Supported by Paypal Ventures & Polygon. Owning the operator with $12B+ of restaked ETH securing the EigenLayer operator network. Developed by a certified SOC 2 Type 2 and a 10-year infrastructure-experience team.
Well, I've seen this from many angles now, and I am no longer sure which I am more comfortable with.
The gap is real. These are the reasons for it; they are real. I don't understand which is working more?
What's the significance of this space? Is it a warning or alert? What would make the difference in your interpretation?
@NewtonProtocol #Newt #NEWT $NEWT $EVAA $SOL

I remember the first time I saw a null value break a live protocol. It was a small position. Manageable loss. But I stayed up most of that night not because of the money — because of how stupid the failure was.
The contract hit an edge case nobody tested for. Data feed returned null. Logic halted. Transaction reverted. Funds sat locked while I waited for a manual fix that took six hours to deploy.
The system didn't fail because it was hacked. It failed because it didn't know what to do when it didn't know something.
Most DeFi protocols are built this way. Binary logic baked into immutable contracts. If the expected input isn't there, the system stops. Sometimes that's the right call. But stopping isn't always safe either — especially when positions are open, markets are moving and "try again later" means something different than it did five minutes ago.
The deeper problem is that smart contracts were designed to be deterministic. Same input, same output, every time. That's a feature for simple transfers. It's a liability for complex automation running in volatile conditions.
Newton approaches this differently and it's the part I keep sitting with.
The pre-settlement policy layer doesn't just execute or halt. It resolves. RedStone live price data and Credora risk ratings are integrated into the decision environment before anything settles. When a data gap appears, the system has sources to consult before deciding what to do. Not "shouldn't proceed" structurally "can't proceed without resolution."
Each decision produces a signed attestation. A verifiable record of what the system knew, what it consulted, and what it concluded. That's a different failure mode than a null exception in a contract that nobody can patch until the next deployment.
600K+ verified agent transactions have already run through this layer. 57M+ wallets sit in the Magic Labs ecosystem this plugs into. 1.1M+ registered users. The scale suggests this isn't being stress-tested in ideal conditions only.
But here's what I'm still working through honestly...
Newton runs as an EigenLayer AVS. That means it inherits Ethereum's economic security through restaking — which is genuinely powerful. It also means correlated slashing risk is real. If something goes wrong at the AVS layer, it doesn't stay contained to Newton. And liquidity at $12.6M market cap is thin enough that the July 24 Core Contributors unlock — coming right after the 139M NEWT that hit in June — could create drift that has nothing to do with the protocol's actual performance.
Those aren't dealbreakers. They're the parts that deserve honest attention rather than footnote treatment.
The null value that kept me up years ago was a reminder that edge cases aren't rare — they're inevitable. The question is whether you build systems that halt when confused, or systems that resolve when confused.
Which do you trust more when real money is on the line?
#NEWT @NewtonProtocol $NEWT
$EVAA $SOL #Newt

Here are systems that most people do not consider when investigating the Settlement, The Settlement Check That Most systems Skip.
Most of the time, the DeFi systems enable transactions to complete prior to verifying the transaction. Thinking in opposition to Newton!
I've read it, read it, read it again: why this time is so crucial . . . . . . . ?
It's a situation in which once you are through with the settlement you are always reacting. Transaction executes. Value moves. Flag gets raised. The time for doing anything towards prevention is over by that time. So which is risk management and which is risk documentation?
That's how in real life, most compliance and risk systems actually operate. Not that anyone did it on purpose to react though. Prevention is more difficult than reportation! It requires the check to not occur at the same time as execution itself, to occur during execution.
All the protocols that I know of were not conceived to be.I didn't know half the protocols that were there were not designed that way. Compliant done by post-execution through off-chain screening, centralized front-ends and legal deals, without having to interact with execution. This will not be a blockage to the transaction.The transaction will not be held up till its settlement.
It's different when Newton shows up before the settlement. A series of rules programmed in the policy enforcement layer and embedded in the live price data in RedStone by Credora risk ratings assess all transactions. No separate consultation for the purposes of this project. Piñon-juniper woodland is a component of an agent's decision context.
There was an attestation for each check made. Something tangible given of what the system learned, what it evaluated and what it said; without either anyone "sinking in" or anyone being "sunk" into. That's a different way of having an audit trail than logs after the fact!
The potential outcomes are just some of the possibilities. The risk conditions policy gates will be in effect before the settlements are established. An attempt to trade at a bad price feed, at a poor credit quality party when the trade does not settle, does not affect the trade but the party with poor credit quality is flagged. Has no impact on running execution.
Prevention is the best way to go - not documentation.
On this layer 600K+ agent transactions have been successful since June 23, 2026 on the Mainnet Beta. 1.1M+ registered users. 350K+ activated agents. VaultKit SDK provides this to the 200K+ developers who are currently developing on Magic Labs infrastructure the same way (as pre-settlement check) without having to build it on their own. The status of the result is already “In the stack”.
Magic Labs has been certified SOC 2 Type 2. This isn't something that’s crypto-native — this is enterprise security infrastructure. Security of EigenLayer AVS architecture says: not just the good world, it's a message meant to withstand the test of the real world!
That said, the valuations of both are certainly not cheap relative to usage, and both have a high user-to-cap ratio of $0.04 and $12.6M. On 24th June approximately $7.6M (37% of 139MNEWT) was unlocked without causing the structure to collapse.Of the amount, 139M NEWT was unlocked without collapsing on June 24, which was 37% of the funds. The operators are stakes to potential gains as well as losses, with dPoS requiring only a stake as tiny as 8.5%, and slashing penalties for misbehaving.
So far the one that I am still juggling with are doing it in an honest to God way.
Then it's better to be early than late rather than suffer the repercussions than prevent the issue. To be able to act on the rules however, somebody must program them. The ruling will be made by the person writing the rules and what will be stopped will.
What would be the one rule you would want to have taken to the Governor if you knew and could point to him?
#Newt @NewtonProtocol $NEWT $VANRY $AAPL.US

Compliance that is not an after-thought...
I have seen the ways of compliance in most of the DeFi protocols. It's done by hand, old-fashioned and delicate. Transactions execute. Then one reads them to see if they ought to have. The flag is raised when after the value has moved. When caught, there is no time to change to prevent the harm.
It is not a compliance system. That's a fake reporting system!
This is a structural issue. Compliance was not a core layer of most protocols. It is bolted on later via centralised front ends or off chain screening tools or through legal agreements that do not involve the execution environment. The deal is not regulated, but only the transacting entities.
Newton's Architecture approaches compliance differently. Certain policy conditions, often referred to as sanctions checks, KYC conditions and AML rules, are assessed before any settlement is provided (as opposed to generated after). The enforcement takes place, not at the time someone looks back on what happened, but at the time she points.The enforcement occurs when the agent tries to perform it, not when she looks back.
It is a distinction worth noting! Pre-settlement enforcement equates to no flag, a gate. The transaction doesn't go through and it is marked for review. You perform either, you don't perform neither.
This policy layer also integrates RedStone price data as well as Credora risk ratings, eliminating the need for separate systems to run in parallel with execution. It's part of the decisions environment in which an agent works.
I am still dealing with the exception cases in this. Rules change. There are variations between jurisdictions in regulatory laws. What is 'ok' in one place is 'not ok' in another. Immutable execution layer leads to its own inflexibility and inflexibility in the fast-moving regulatory landscape entails flexing in multiple ways.
However, it's not letting the direction be structurally wrong. Manual is hard to adhere to. While this is an obvious rule of compliance, it is the only realistic one when the compliance is implemented through the autonomy of execution agents and occurs less in their presence.
There were numbers that indicated this is the way that adoption is going. 1.1M+ registered users. 600K+ Real Agent transactions verified. Since launching of Mainnet Beta on June 23, 2026, more than 350K agents have been activated, and VaultKit SDK has facilitated the integration for the 200K+ developers already onboard Magic Labs' ecosystem.
That amount of user-to-valuation compression is still not easily explainable at those valuations for the $0.04 and the $12.6M market cap. This is either because the market hasn't got to the production size, or there is some bizzaro going on in the supply 139M NEWT is unlocked on 24th June, which is about $7.6M.
One additional level of complexity: operators have a “downside” risk for committing misbehaviour, while those enforcing compliance have a “downside” risk for misbehaviour.The operators also have a "downside" risk if they commit misbehaviour, and the people who are enforcing compliance have a "downside" risk if they commit misbehaviour due to the inclusion of "slashing" for misbehaviour in the 8.5% dPoS staking APY.
Now I'm not so sure on this one!
Is full automation feasible or would it be more critical to have human judgment somewhere in the mix in the real world?
#Newt @NewtonProtocol $NEWT $LAB $AAPL.US

数か月前、私はボットにウォレットへのフルアクセスを渡しました。それはミスでした。
致命的なことは起きませんでした。ですが、その後それと向き合っているうちに、ふと気づいたのです。単純な疑問に対する答えがない——「自分が意図していないことを、ボットがやってしまうのを何が止めるのか？」と。正直な答えは、止めるものは何もない、コードが書かれたとおりに動くだけだ、ということでした。そしてコードは、「書かれたとおりに動く」限りは問題ないのですが、動かなくなる瞬間まではそうなのです。
それが、誰も真正面からは語らないDeFi自動化の隠れたコストです。
多くのユーザーは今でも、手動でリバランスし、利回りを回収し、奇妙な時間に清算閾値を監視することで何とか対応しています。疲れます。明らかな解決策は自動化です。でも完全な自動化は、通常、完全な信頼を意味します。鍵を渡して、開発者がテストするはずだったあらゆる状況下でもロジックが保つことを願うことになるのです。