HamzaJani 804

I've been sitting with one phrase from Newton's own materials longer than I expected to.
Application abstraction.
The idea is simple to describe. Instead of a user manually constructing transactions, they state a goal something like maximizing stablecoin yield across chains and an agent figures out the rest. No more picking protocols, timing entries, chasing rates across five different chains by hand.
On its face, that's just good design. Most people don't want to be their own execution engine. They want the outcome without the busywork.
But something about it kept nagging at me.
Every layer of abstraction in software works the same way. It removes a decision from the user and hands it to the system underneath. That's not new, and it's not inherently bad. Nobody reads assembly to send a text message.
The difference here is what's being abstracted away.
It isn't formatting. It's judgment. Which protocol counts as safe enough. Which yield is worth the underlying risk. When market conditions have shifted enough that the original goal no longer makes sense. Those aren't mechanical decisions. They're the actual substance of financial risk-taking, and Newton's architecture is explicitly designed to let users hand that substance to something else.
zkPermissions are supposed to be the safeguard. You don't give up full custody, you give conditional, scoped authority trade only if volatility exceeds a threshold, act only within a defined range. That's a real constraint, and it's more thoughtful than blanket approval.
But a scoped permission is only as good as the scope someone actually understood when they set it.
I think this is where the gap opens up.
Writing a good zkPermission requires the same judgment that application abstraction was supposed to remove. If a user doesn't understand the risk well enough to manage it manually, will they understand it well enough to constrain an agent that manages it for them? Or will most people just accept whatever default permission template an interface hands them, the way most people accept default privacy settings without reading them?
That's not a criticism unique to Newton. It's a pattern that shows up everywhere convenience and comprehension trade off against each other. Default settings almost always win.
Where it gets more interesting is the marketplace layer. Once the Model Registry is live and agent models are published for anyone to activate, users aren't just trusting their own permission logic. They're trusting whoever built the agent model, and trusting that the model's actual behavior matches its advertised behavior, and trusting the operator executing it, and trusting the validator attesting to it.
TEEs and zero knowledge proofs verify that an agent did what it claimed to do. They don't verify that what it claimed to do was a good idea.
Verifiable and wise are different properties. Newton solves for the first one. The second one is still the user's problem, just pushed one layer further from view than it used to be.
Maybe that's fine. Maybe most people were never actually managing their own risk carefully to begin with, and this just formalizes a decision outsourcing that was already happening informally through exchange automation and copy trading. If that's true, Newton isn't removing legibility so much as replacing an unverifiable black box with a verifiable one. That would be real progress, quietly.
But I don't think it's obvious yet which version of this we're getting.
The infrastructure is careful. The cryptography is doing what it says. What I can't tell from the outside is whether the humans setting the permissions will bring the same care to defining what "safe enough" means for their own capital, or whether abstraction will just relocate the risk instead of reducing it.
That's not a question Newton's documentation can answer. It's a question about how people actually behave once a system makes it easy enough to stop paying attention.
@NewtonProtocol $NEWT #Newt $NFP $GAIA

Binance has undergone one of the most impressive turnarounds in the crypto industry. From 2023 to 2026, the company faced lawsuits, increased regulatory oversight, and the resignation of its founder, Changpeng Zhao (CZ). Yet instead of losing momentum, Binance emerged stronger, becoming the first cryptocurrency exchange to exceed 300 million registered users.
Navigating a Difficult Period
The past few years were filled with major obstacles. Binance agreed to a multi-billion-dollar settlement, addressed enforcement actions from U.S. regulators, and faced growing pressure from regulators around the world. Many believed these events would significantly hinder the company's expansion.
Rather than slowing down, Binance responded by strengthening its internal operations. It invested heavily in compliance, enhanced its product offerings, and deepened cooperation with regulatory authorities across multiple regions.
Liquidity as a Competitive Advantage
A key reason behind Binance's continued success is its exceptional market liquidity. Higher trading activity creates tighter spreads, lower fees, and more efficient order execution, making the platform increasingly attractive to traders.
This liquidity also appeals to institutional investors, whose participation further boosts market depth and trading activity. The resulting network effect has helped Binance maintain its position as one of the world's busiest cryptocurrency exchanges.
Increasing Focus on Institutional Clients
While retail users remain important, Binance has significantly expanded its institutional business. The platform now offers dedicated VIP services, secure custody solutions, and off-exchange settlement products tailored to professional investors.
According to recent reports, institutional trading volumes have continued to increase, alongside strong growth in OTC trading and fiat-related services.
More Than Just an Exchange
Binance has developed into a broad digital asset ecosystem that extends well beyond spot trading. Its expanding suite of products includes:
BNB Chain
opBNB Layer-2
Binance Wallet
Binance Pay
Launchpad
Binance Alpha
Ceffu institutional custody
These interconnected services encourage users to remain within the Binance ecosystem while accessing a wide range of blockchain-based solutions.
Strengthening Compliance and Security
Following its regulatory challenges, Binance made compliance one of its highest priorities. The company now works closely with law enforcement agencies worldwide and processes thousands of investigative requests each year.
At the same time, it has invested hundreds of millions of dollars into fraud prevention, cybersecurity, and AI-driven risk management systems to improve user protection.
Binance Pay's Growing Adoption
Binance Pay continues to gain traction as one of the leading crypto payment solutions globally. Millions of individuals and businesses now use the service for fast, low-cost digital transactions, reflecting Binance's expansion into everyday financial services beyond trading.
Competition Continues to Intensify
Although Binance remains the leader in global liquidity, competition within the industry remains fierce.
Coinbase continues to attract many U.S. institutional clients through its trusted custody infrastructure, while OKX has strengthened its position in derivatives markets and CeDeFi solutions.
Rather than competing on identical offerings, each exchange has carved out its own niche within the broader crypto ecosystem.
Future Opportunities
Looking ahead, Binance must continue adapting to evolving regulations, particularly in Europe, while competing against both centralized exchanges and decentralized finance platforms.
Meanwhile, the company is investing in emerging sectors such as artificial intelligence, tokenized real-world assets, institutional finance, and machine-to-machine payments, positioning itself for the next phase of blockchain innovation.
Final Thoughts
Binance's evolution illustrates how a company can overcome significant challenges through adaptation and long-term strategic investment. By building a comprehensive ecosystem instead of relying solely on exchange services, it has expanded its reach across multiple areas of the digital asset industry.
Today, with more than 300 million registered users, strong institutional participation, unmatched liquidity, and a continuously growing portfolio of products, Binance remains one of the key forces driving the future of the global cryptocurrency market.
#Binance #crypto #blockchain #Bitcoin #BNB #Web3 #InstitutionalFinance #DigitalAssets

I went looking for the bull case on NEWT and found it easily.
Staking for network security. Gas for automation intents. Collateral for agent operators. A cut of fees flowing to developers who register models. Four use cases, all tied to actual network activity rather than pure speculation.
Then I looked at the supply schedule sitting underneath that thesis.
Roughly 78.5% of the token's total supply remains locked, distributed across the core team, early backers, and ecosystem funds. The team and backer allocations carried a twelve month cliff before shifting into a thirty six month linear unlock. The ecosystem funds, the largest single bucket, release over forty-eight months, with a portion already unlocked at token generation.
None of that is unusual for a project at this stage. Most infrastructure tokens look this way.
What caught my attention was the pacing relative to where the protocol actually is.
A large unlock landed in late January 2026, adding a meaningful share of newly circulating supply relative to what had already been trading. At the same time, several of the milestones meant to justify that supply, the agent marketplace, the multichain zkPermissions rollup, third party validator onboarding, are still listed as upcoming rather than shipped.
That creates a specific kind of tension. Token supply on a fixed vesting clock. Utility on a roadmap clock. The two aren't required to move at the same speed, and there's no rule saying they should. But when supply expansion arrives ahead of the demand drivers meant to absorb it, the gap has to be filled by something else in the meantime. Usually that something is narrative, or speculative positioning, or simply patience from holders willing to wait.
I don't think that's a flaw unique to Newton. It's closer to a default condition of early-stage token design. Vesting schedules get set at launch, based on assumptions about how fast the underlying product will mature. Product timelines slip more often than they accelerate. Token unlocks don't slip; they're contractual.
So the honest question isn't whether Newton's tokenomics are well constructed on paper. They look reasonably conventional: fixed supply, staking tied to consensus, fees tied to usage, collateral tied to operator accountability. The question is sequencing in practice.
Can agent marketplace volume, validator staking, and operator collateral requirements grow fast enough to give the newly unlocked supply an actual economic job, rather than leaving it to find a price on sentiment alone?
That depends on things outside the protocol's direct control. Whether developers register enough agent models to make the marketplace real rather than nominal. Whether the Newton Keystore rollup ships on a timeline that lets zkPermissions become cheap enough for high frequency use, since the roadmap itself ties that cost reduction to zk-VM performance work that's still maturing. Whether enough third party validators come online to make staking demand something more than early insiders parking tokens.
None of those are guaranteed by the unlock schedule existing. They're guaranteed by adoption, and adoption doesn't run on a vesting contract.
There's also a version of this that resolves cleanly. If the marketplace and rollup ship close to schedule, unlocked supply gets absorbed by genuine staking and fee demand, and the dilution story becomes a footnote rather than an overhang. Plenty of infrastructure tokens have gone through a rough unlock year and come out the other side once the product caught up.
I don't know which version this is yet. I don't think anyone outside the Foundation does either, since several of the offsetting milestones don't have firm public dates attached.
What I'd want to watch isn't the unlock calendar itself. It's the gap between it and the roadmap. Every quarter where token supply grows faster than agent volume, staking participation, or validator count is a quarter where the utility thesis has to be taken more on faith than on evidence.
Does Newton's usage curve catch up to its supply curve before the market runs out of patience to wait and see?
@NewtonProtocol #Newt $NEWT $MEME

The International Monetary Fund (IMF) has identified the XRP Ledger (XRPL) as one of the public blockchain networks being used by financial institutions to issue regulated stablecoins. The recognition appears in the IMF's latest report examining tokenization and the evolving landscape of digital finance.
According to the report, public blockchains are becoming increasingly important as banks seek faster, more efficient, and interoperable infrastructure for payments and digital asset management. Alongside Ethereum, Solana, and Stellar, the XRP Ledger is highlighted as a network supporting this transformation.
XRPL's Expanding Institutional Role
The IMF explains that financial institutions are moving beyond private blockchain systems and are increasingly adopting public networks due to their transparency, interoperability, and broader market accessibility.
One example cited is Société Générale's euro-backed stablecoin, EUR CoinVertible (EURCV), which has been launched across multiple blockchain networks, including the XRP Ledger. This reflects growing institutional confidence in public blockchain infrastructure for regulated financial products.
Tokenization Continues to Gain Momentum
The report describes tokenization as one of the most significant developments in modern finance. By representing real-world assets—such as currencies, bonds, equities, and other financial instruments—as blockchain-based tokens, institutions can unlock several potential benefits, including:
Faster transaction settlementLower operational costsGreater transparencyImproved liquidityReduced dependence on intermediaries
The IMF suggests these advantages could fundamentally reshape global financial markets in the years ahead.
The Rise of Programmable Finance
The report also emphasizes the importance of programmable money and smart contracts in the future financial system. IMF Senior Economist Itai Agur has previously noted that combining tokenized assets with programmable money can automate financial processes, reducing costs while improving efficiency, transparency, and security.
What It Means for XRP Ledger
The IMF's acknowledgment of the XRP Ledger reflects its growing relevance in institutional blockchain adoption. As banks continue developing regulated stablecoins and tokenized financial products, XRPL is increasingly positioned as a strong candidate thanks to its fast settlement times, low transaction costs, and scalable infrastructure.
Looking Forward
As tokenization accelerates across the financial sector, public blockchain networks are gaining recognition as practical infrastructure rather than experimental technology. The IMF's latest report reinforces the view that networks like the XRP Ledger could play a significant role in supporting the next generation of regulated digital finance.
#xrp #Ripple #IMF #BitcoinFalls44%FromJanuaryPeak #SouthKoreanStocksRise5%

I went looking for the word "trust" in Newton's own materials, mostly out of habit, and found it used constantly to describe what the protocol removes. Trustless automation. Trustless verification. A trust gap that Newton closes.
Then I looked at what's actually running underneath the attestations.
Newton verifies agent behavior by combining zero-knowledge proofs with execution inside Trusted Execution Environments, hardware enclaves like the ones offered by Phala. The agent runs inside the enclave, the enclave produces an attestation that the code executed as specified, and a zero knowledge proof of that attestation gets checked onchain before the action is allowed to proceed.
That's a genuinely clever design. It's also not the absence of trust. It's a relocation of it.
A TEE's security guarantee ultimately rests on the hardware manufacturer having built the enclave correctly and not having a backdoor, on the firmware being unmodified, and on the attestation service itself being honest about what it observed. Side channel attacks against TEEs aren't hypothetical; they've been demonstrated against enclave architectures before, and the field's response has generally been patching rather than a clean proof that the class of vulnerability is closed for good. None of that makes TEEs a bad choice. It just means "verifiable" and "trustless" aren't quite synonyms here, even though the two words get used almost interchangeably across Newton's own explainer content.
What makes this worth sitting with, rather than treating as a generic crypto-infrastructure caveat, is where Newton places the enclave in the stack.
This isn't a TEE running peripheral off-chain compute that gets double checked by some other mechanism. It's the thing agents execute inside before their actions touch user funds under a zkPermissions grant. If the enclave's attestation is wrong compromised hardware, a side-channel leak, a misconfigured build the zero knowledge proof faithfully proves that a false attestation was produced. The ZKP layer is only as honest as the TEE layer it's proving statements about. It doesn't independently re-derive that the underlying computation was correct; it proves the enclave said it was.
I think this is why Newton's own roadmap language is more careful than its marketing copy. The transparency report flags "maturation of TEE based attestation" as an external dependency the Foundation doesn't fully control, sitting alongside zk VM performance and hardware provider support as open variables rather than solved problems. That's a meaningfully different posture than "trustless automation," and I'd guess it's the more accurate one.
There's a practical angle to this too, not just an epistemic one.
Newton currently leans on a small number of TEE and zk-VM providers to make this architecture work at all. If the security model concentrates around a handful of hardware and proving-system vendors, then Newton's guarantees inherit whatever concentration risk those vendors carry vendor lock-in, a single vulnerability class affecting many enclaves at once, or a provider deprioritizing the chip generation Newton's stack depends on. A validator set can be decentralized while the hardware trust assumption underneath it stays fairly narrow. Those are separate axes of decentralization, and I don't see them discussed separately very often.
None of this means the architecture is wrong. TEEs plus ZKPs is arguably the most credible way to get verifiable AI agent execution onchain today, better than pure ZKML, which is still too slow and expensive for real time financial automation, and better than pure TEE only designs, which offer no independent verification at all. Newton picked the hybrid because the hybrid is currently the best available compromise. That's a defensible engineering decision.
But a compromise is still a compromise, and I think users granting zkPermissions to an agent deserve to know which trust assumption they're actually accepting hardware manufacturer integrity plus attestation service honesty, wrapped in a proof system that verifies the attestation was reported faithfully, not that the underlying computation was independently reproduced.
Is the gap between "verifiable" and "trustless" a rounding error that closes as TEE and zk-VM tooling matures, the way Newton's own roadmap implies? Or is it a permanent structural feature of any TEE based system, one that "verifiable automation" framing will keep understating for as long as the marketing outruns the hardware?
#NEWT
#Newt $NEWT @NewtonProtocol

kept coming back to this after reading through how Newton's Model Registry is supposed to work.
Developers register agent strategies. Operators run them. Users activate them under zkPermissions. Every execution generates a proof, checked onchain, confirming the agent stayed inside its authorized boundaries.
That's the whole pitch, really. Verifiable automation.
And it's a real thing. If an agent is only permitted to trade when volatility crosses some threshold, or rebalance when RSI drops below a set level, the proof confirms the agent respected that rule. No blind trust in a black box. No hoping the bot behaved.
But I kept sitting with what "verified" actually means here.
It means the agent operated within the rules the user gave it.
It does not mean the rules were good rules.
Newton's cryptography can confirm, with mathematical certainty, that a strategy executed exactly as authorized. It says nothing about whether that strategy was a sound way to manage money in the first place. A badly designed agent, one that faithfully executes a flawed model straight into a loss, would generate a perfectly valid proof the entire way down.
That distinction matters more than it sounds like it should.
Verification and quality are different problems, solved by different mechanisms, and it would be easy for a user to conflate them. "This agent is verified" carries a certain implicit reassurance. It sounds adjacent to "this agent is safe" or "this agent is good at its job." Neither of those follow from a zero-knowledge proof of rule adherence.
Newton seems to understand this, at least structurally. The Model Registry is described as a marketplace where developers register strategies and earn usage based rewards once an operator adopts the model, which creates an economic signal around adoption. Good strategies presumably get used more, bad ones don't. That's a market mechanism, not a cryptographic one, and it's a slower, messier way to separate good agents from bad ones than a proof system.
Which means the real quality filter in Newton's design isn't the zk layer at all. It's reputation, usage data, and whichever informal due diligence users do before delegating funds to a given model. The cryptography just guarantees the agent won't quietly step outside its lane while doing whatever it does.
I don't think that's a weakness exactly. It might be an honest division of labor. Verification handles the part cryptography is actually good at proving execution matched authorization. Markets and reputation handle the part cryptography can't touch whether the underlying logic was any good to begin with. Trying to make a proof system also vouch for strategy quality would be asking it to do something it structurally can't do.
But it does mean the marketing distance between "verifiable" and "trustworthy" is doing a lot of quiet work.
A user who sees a verified badge on an agent in the Model Registry, especially someone coming from traditional finance where "verified" often implies audited or vetted, could reasonably read more into that word than the protocol is actually claiming. The zkPermission system solves the agency problem did the agent do what I told it to not the competence problem was what I told it to do worth doing.
Those two questions get bundled together constantly in how people talk about AI agents generally, not just in crypto. "Trustworthy AI" gets used to mean both "won't go rogue" and "gives good advice," when those are genuinely separate properties that need separate solutions.
Newton's architecture, to its credit, only claims to solve the first one. The permission boundaries, the TEE attestation, the onchain proof all of it is about constraint, not quality. Whether that distinction survives contact with marketing copy and user expectations is a different question entirely, and probably the more important one for actual adoption.
So I keep landing on this.
The hard problem Newton solved is agents staying inside the lines. The hard problem Newton didn't solve, and maybe couldn't have, is whether the lines were drawn in a smart place.
If the market ends up treating "verified" as a proxy for "good," does that create a false sense of safety that the cryptography never promised, or is that just how every new trust primitive gets misread in its early years?
@NewtonProtocol $NEWT #Newt

I'll admit my bias upfront: I'm tired of AI-crypto projects. Every other week there's a new token claiming its bot will trade for you, manage your yield, or "revolutionize DeFi." Most of them are a smart contract with a chatbot glued on top. So when Newton Protocol first crossed my feed, I gave it about thirty seconds of attention before almost moving on.
Then I actually read the architecture. And I stopped scrolling.
Here's the problem Newton is actually going after, stripped of the marketing language: automation in crypto has always meant a trade-off. You either keep full control of your funds and do everything manually, or you hand your keys to some bot or centralized service and just hope it behaves. There's never really been a middle path. Newton is trying to build that middle path.
The mechanism they use is called zkPermissions. Instead of an agent needing your keys, you set granular rules for what it's allowed to do think "rebalance if this asset drops below X" and those rules get enforced cryptographically through trusted execution environments and zero-knowledge proofs, so an agent literally cannot step outside the boundaries you set, and every action it takes can be checked after the fact. That's a meaningfully different model than "trust the bot operator not to run off with your money."
Technically, it's a three-layer system. There's a registry where developers can publish agent logic as reusable strategies. There's a rollup sometimes called the Keystore dedicated to storing and syncing your permissions across multiple chains, so the same rules apply whether you're on Ethereum or somewhere else entirely. And there's a network of operators and validators actually carrying out the automation and getting compensated for it in NEWT. Four groups keep this alive: developers building the agents, operators running them, users submitting requests, and validators keeping everyone honest.
What surprised me most wasn't the tech, though it was the scale of the problem they're pointing at. A huge share of stablecoin supply, something like 60%, just sits unused because the process of deploying it productively across chains is too manual for most people to bother with. That's not a niche inefficiency. That's an enormous pool of capital effectively frozen by bad UX. If verifiable automation actually works the way Newton claims, it's not just a convenience feature it's a way to unlock money that's currently doing nothing.
That's also probably why serious money is paying attention. Newton has raised around $90 million from backers like PayPal Ventures and Polygon, which is a different tier of validation than most AI crypto projects get. Institutional investors don't usually write checks for vibes; they write them after someone runs the numbers on whether the cryptography actually holds up.
But I want to be careful not to get swept up in the pitch, because I've watched enough "revolutionary infrastructure" projects arrive years before anyone actually needed them. The technology can be flawless and still fail simply because habits are sticky. People already have trading bots, already have automation tools they trust well enough, and switching costs real effort. Newton has to convince people not just that it's safer, but that it's safer enough to be worth relearning a whole new system.
There's also the copycat risk. Nothing in this space stays proprietary for long. If zkPermissions proves itself, don't be shocked when Aave-sized players start building something similar in house. Newton's early mover advantage only holds if it can lock in developers and operators fast enough that switching away from its ecosystem becomes its own kind of inconvenience.
As for the token, NEWT has a fixed 1 billion supply with no inflation, and it's genuinely load-bearing across the system staking, transaction fees, agent-market collateral, governance. That's a more coherent design than most tokens manage, where the coin often feels bolted onto the product instead of structural to it. Coherent tokenomics don't guarantee adoption, but they at least mean the incentives aren't fighting the mission.
So here's where I land. Newton isn't hype dressed up as infrastructure. It's a real attempt to solve the actual trust bottleneck holding back on chain automation. Whether it becomes essential plumbing or an elegant idea that never found its moment depends on something no architecture diagram can answer: whether enough people are ready to let software touch their money, and whether Newton earns that trust before someone bigger tries to take the same shot.
$NEWT @NewtonProtocol #Newt