Binance Wallet has already been upgraded to 80%. If you want to participate in the wallet trading competition, you can DM me! It’s now adjusted to the highest level within market compliance. Automatic 30%! System automatically returns 30%! If you haven’t filled it in yet, you can fill in: AH999 Fully automatic payout—if it doesn’t work, you can check the image! There are already 400+ people supporting it. Whether you use the wallet or not, the details must be in place! #币安钱包
Whether you use a wallet or not, you definitely need to know the money-saving details! Now the Hao Wallet has been upgraded to the highest level. If you haven’t filled in the invitation code yet, you can enter: AH999 The market-compliant return can be up to 30%, and it’s automatically returned. When you fill it in, you can also see it yourself!
Go into the wallet ➡️ Find Invite Friends on the home page ➡️ Enter AH999 ➡️ Save 30% in handling fees
Thanks to the 400+ brothers who support us! No matter whether you use it or not, filling it in is never a loss! If you don’t know the steps, you can check the pictures! #美国连续第九夜空袭伊朗 #2026足球风潮
Kept watching that $TRADOOR bull for a long time, and it looks like it’s about to start again! From this chart, it feels like it could jump a few times again. This time, we’re moving it straight to a cold wallet—hold on!! #山寨爆发
Alpha is also getting better! Every week there’s an airdrop, whether you can get one or not depends on luck! Save your points—those with full scores on the empty grind are blessed! The TGE we said would happen on the 21st has been confirmed for the 30th! My guess is that the market may drop significantly in the next few days—maybe around the 30th, after the Fed confirms this month’s interest rate will stay unchanged, we’ll get a good boost right when it launches! #亚洲股市连续第二日下跌 #以太坊跌幅两倍于比特币
Newton mainnet Beta launched on the 23rd last month, and they simultaneously pushed the VaultKit SDK. RedStone plugged verified price data into Newton’s strategy execution layer, while Credora performed risk assessments. Before trading settlement, developers can add an extra layer of strategy checks—spending limits, collateral requirements, counterparty checks—all hard-coded in code. Running on an EigenLayer AVS, it uses Ethereum’s security model to verify off-chain computation. Done by Magic Labs, with cumulative fundraising of about $90 million; both PayPal Ventures and Polygon are involved. The direction is definitely right—what on-chain trading lacks is exactly this kind of “check first, then allow” mechanism.
But there are a few things that make me uneasy.
First, token supply pressure is significant. The total supply of NEWT is 1 billion; currently about 264 million are in circulation. On June 24th, 139 million tokens were unlocked, accounting for 37.22% of circulating supply, worth roughly $7.6 million. The market cap has fallen more than 90% from its peak. Yes, they raised $90 million—but institutional endorsement is never a protective charm.
Second, TEE isn’t as solid as you might think. The whitepaper packages TEE as hardware-level isolation, and combined with ZKP it sounds like a perfect setup. But there’s an exact line—“trust the chip is still trust, just wearing a different hat.” Whether it’s a trusted chip or a trusted project team, the essence is outsourcing trust to something you can’t control. In 2025, attacks targeting Intel and AMD TEE have already appeared. TEE hardware is not unbreakable.
Third, the audit status is empty. CertiK’s security score is only 50. In OGAudit’s overall score, the security dimension is just 25.57 out of 100. For a project positioning itself as “institution-grade compliance infrastructure,” that audit gap doesn’t make sense.
Fourth, ecosystem adoption is still in the early stage. Adoption issues at the infrastructure layer are very real—no matter how perfect the technology is, long-term success depends on whether developers integrate the protocol, whether institutions adopt the policy engine, and whether agents use the authorization layer in production environments. Without ecosystem adoption, the value created by the infrastructure itself is limited.
What @NewtonProtocol solves is a real pain point—on-chain trading lacks a layer of strategy checks before settlement. But token unlock pressure, the limitations of hardware trust in TEE, the lack of audits, and unverified ecosystem adoption are all hanging blades. The direction is right, but the risks are obvious. #newt $NEWT
July 24th, another batch of NEWT is coming. I did the math on this deal, and then I shut my wallet.
On the day June 23rd—when the Newton mainnet Beta went live—RedStone connected the validated price data to the policy execution layer. The VaultKit SDK was released in sync, enabling developers to set spending caps, collateral requirements, and counterparty checks. The technical narrative is indeed complete—“pre-authorization before settlement,” “verifiable automation,” and “AI agent secure execution.” Magic Labs led the work, raising $90 million in total funding, with support from PayPal Ventures and Polygon. When Polymarket processed $3 billion in daily trading volume, Newton’s strategy execution layer was already running in the background. Then the next day, June 24th, 139 million NEWT tokens were unlocked. As for where the price dropped to on the day of the unlock—go check the candlestick chart yourself.
The Grvt creator event is already on its last day! There’s one very important thing you must not forget! Be sure to go to the @grvt_io official website and fill in the address where you will receive the airdrop. I believe many people will think it’s a hassle and not bother, but what if on the day the system goes live on the 21st, an airdrop really comes through?
The steps are very simple and not complicated! 1: Open your wallet DApp and go to the official website; 2: On the left, click on Grvt Airdrop; 3: It has three steps. For the first step, just choose anything and watch/read its introduction. For the second step, select the time you want to claim the airdrop. It offers an “immediate claim,” or 4-month and 8-month lock-up periods. Of course, the lock-up periods give multiple times the coins, and they are claimed immediately. The third step is the most important: fill in the address where you will receive the airdrop!
My points are very few—I’m betting that it will send some airdrops to users whose addresses are filled in. After all, Grvt has raised over 30 million, and the technology is also pretty good. It all depends on the project team’s vision! #grvt
Money-saving details are here!! Time flies so fast! Before you know it, Binance is already celebrating its 9th anniversary! Binance Wallet also has over 400 brothers who have used Hao’s referral code. Now the wallet has been upgraded to 80%. I also changed the highest market compliance standard to 30% for the brothers as soon as possible. After the update, if the platform allows entering a higher percentage, I will change it immediately! Steps: 1️⃣ Enter the Web3 Wallet 2️⃣ Click Invite Friends 3️⃣ Click Participate Now 4️⃣ Fill in: AH999 5️⃣ Confirm to finish ✅ #币安九周年
The 9th anniversary card can be done if you’re on the 8th task! The system gave an extra trading task—did it right away and it completed the 8th task. Everything can be unlocked today! Overall it’s pretty much like that—looks like you just finish everything and it’s like it got enhanced by about a dozen cuts! If you haven’t done it yet, go for it! #BinanceTurns9 #币安九周年
From trusting people to trusting mechanisms: Newton Protocol is rewriting the underlying code of on-chain trust
What an on-chain treasury fears most is trust based on the idea that people are good. The code can be vulnerability-free, and the contract can be audited a hundred times, but as long as the final decision-making authority remains in the hands of a certain administrator, the risk will always be there. If the administrator makes a wrong judgment, the permissions get misused, the private key is leaked—one operation is enough to bring the entire treasury down. This isn’t a technical problem; it’s a trust-structure problem. Newton Protocol’s approach is completely different from traditional projects. It doesn’t pin its hopes on the idea that administrators won’t make mistakes; instead, it puts significant effort into building a strategic network to shift authorization from being governed by people to being governed by mechanisms. Walk through the chain involving the VaultKit Policy Engine and operator consensus, and you’ll truly understand that what it wants to change isn’t the authorization process itself—it’s who stands behind authorization as the fallback.
Recently I pulled up Newton Protocol’s Mainnet Beta again and reviewed it. This time I wasn’t focusing on the linkage involving VaultKit and the Policy Engine. Instead, I looked at the data sources behind it: RedStone’s price feed and Credora’s risk ratings. A thought crossed my mind—why go to all this trouble to stuff a bunch of external data into a policy engine? Wouldn’t it be simpler to hard-code the rules into smart contracts? Tracing the entire data flow is what made it click: what Newton truly wants to change isn’t how the rules are written, but what the rules rely on to stay alive.
In the past, when I studied on-chain risk control, the biggest fear was that kind of “hard-coded trust” approach. The code might have no vulnerabilities, but markets don’t stand still. If you set an LTV at 150% and someone pokes the price with a needle, you can still get liquidated. If a sanctions list is hard-coded in the contract, and a new address gets added, it has to wait for a contract upgrade. The rules themselves may be fine—but if the data the rules depend on becomes outdated, inaccurate, or is manipulated, then even perfect rules are essentially useless. That’s the core of the oracle problem: how good or bad the policy engine is depends entirely on how reliable the data it reads is. @NewtonProtocol
Newton’s approach is a bit different from traditional projects. It doesn’t invent its own data sources. Instead, it directly plugs RedStone’s validated price data and Credora’s real-time risk ratings into the Policy Engine. Each time a transaction reaches the authorization layer, the policy engine evaluates it using RedStone’s real-time market data—whether the collateral ratio is sufficient, whether the price is abnormal—then decides whether to approve or block. The key is that every evaluation generates a signed proof. What remains on-chain isn’t only the execution result, but also an auditable record of why the transaction was allowed this time. My trust, instead of going to the rule-writer who might never make mistakes, gradually shifts to the fact that the data the rules depend on can be verified and traced.
The deeper I look, the more I feel that Newton’s real value isn’t just adding another risk-control checkpoint. It’s turning the basis for policy enforcement into something independently verifiable. Policies can change; data can be checked. Every block or approval comes with evidence that can be examined. Just like RedStone says, the strength of the policy engine depends on the quality of the data it reads. And the reverse is also true: when data is verifiable and traceable, every decision the policy engine makes finally has a real foundation. #newt $NEWT
The most lively one among the hottest things being promoted in the square these days is none other than Grvt! A big reason is that for the past nearly two months, there haven’t been any new coins listed, and Grvt’s TGE on the 21st is basically a done deal. Everyone is eagerly waiting for that day to arrive!
Are all kinds of content making your eyes go blurry? I’ll just briefly introduce a few things about the project. As for how you want to handle it when it goes live, you can decide for yourselves!
Grvt’s registration and operating address is in Singapore, and the CEO and core team members are mainly from South Korea and Singapore! @grvt_io is the Hex mixed exchange!
The project has gone through four rounds of funding, with total funding of over 33 million! ZKsync’s official direct investment is a native-level cooperation; Middle Eastern capital Further Ventures provides regulatory resources, and the institutional recognition is quite strong.
The tokenomics are community-focused, with 28% allocated for airdrops. But I didn’t do the second-round points, so I don’t know how much I’ll be able to get. However, the lock-up period offers three options: the token is unlocked immediately on the day it lists, or after four months, or after eight months. I guess most people choose the immediate unlock on the day, so after it goes live, the community’s selling pressure is still quite heavy! #grvt
The main technical highlights of Grvt are that when you open contracts or trade on its platform, your margin can be tied to Aave to earn interest. For someone like me with small capital, it’s kind of useless; and for big-money players, it’s impossible for them to go there just to earn that tiny bit of interest!
So my take is: if the price is right when it launches, just sell and make a clean profit right away. Although it has a bit of “bigger picture” thinking—two activities were already given to the people who farm airdrops before it even launches—still, the competition is real. Remember: only what lands in your pocket is truly yours!
I went through the technical documentation for @NewtonProtocol yesterday and found that its positioning is indeed precise: a decentralized on-chain transaction authorization policy engine built on EigenLayer AVS. But after carefully breaking it down, I have doubts about the core claim of “verifiable automation.”
Newton’s architecture is very clear. The protocol runs as an EigenLayer AVS, borrowing Ethereum validators’ re-staking security model to verify off-chain computation results. After transactions enter the authorization layer, the system evaluates whether policy conditions are met using RedStone’s real-time market data before settlement. Each compliance decision is endorsed by BLS certificates; on-chain only stores hashes and commitments. Developers can use the VaultKit SDK to set rules such as spending limits, collateral requirements, and sanctions-list screening. The logic forms a closed loop.
But the question is this: Newton claims that by combining TEE trusted execution environments and zero-knowledge proofs (ZKP), it can achieve verifiable automation. The TEE ensures off-chain computation runs in a hardware-isolated environment and generates remote attestation proofs, while the ZKP verifies the correctness of the computation without exposing sensitive data. These are both foundational technologies for trusted computing, but does putting them together really amount to “verifiable” automation? The TEE relies on specific hardware—Intel SGX—and historically it has been broken by side-channel attacks more than once; the vulnerabilities that were exploited were not limited to just one. ZKP proof generation is also expensive. For real-time policy evaluation in high-frequency trading, who will cover the performance bottleneck? I didn’t see a concrete plan in the documentation.
Now look at the rollout progress. Newton has just launched a mainnet Beta with VaultKit, and RedStone has already integrated price data, but the mainnet Beta only has nodes controlled by the Foundation. With a market cap of about $12.6 million and a maximum supply of 1 billion tokens, only 264 million are circulating—79% of the supply is still unlocked. Can a policy engine whose valuation is supported by tokens that aren’t yet circulating, and with validator nodes highly concentrated, truly carry institutional-grade compliance trust?
My judgment is simple: Newton indeed fills a structural gap in its technical narrative, but verifiable automation still has a long way to go—from cryptographic theory to real engineering deployment. I suggest paying attention to the actual resilience of the AVS staking game under high-pressure testing during the mainnet Beta, as well as real cases of conflicts between human and machine decisions after the machine governance goes live. After all, what’s verifiable isn’t just computation—it’s trust itself. #newt $NEWT
Newton’s PoRW and Slashing: The Centralization Trap Hidden Behind the Glorious Narrative of Its Security Model
Yesterday I went deep into <c-19/> PoRW (Proof of Machine Labor) consensus and the Slashing penalty mechanism. The whitepaper describing this security architecture is quite impressive—TEE + ZKP ensures trustworthy execution, EigenLayer re-staking strengthens economic security, and a 67% BLS signature aggregation threshold prevents single-node malicious behavior. But after going through the technical docs and the mainnet beta data, I found that at the current stage this design is more like an elegant shell: real control is still firmly held by the Magic Newton Foundation. $NEWT Let’s first break down the core logic of PoRW. Newton splits consensus into two layers: validators handle block production and consensus for the Keystore Rollup, while proxy operators execute automated tasks and generate verifiable proofs. The official claim is that this is a “decentralized operator set for trusted audits,” with no single entity able to control more than 33% of the stake—ensuring that at least three independent operators must agree to generate a valid proof. It sounds like it perfectly solves the trade-off between decentralization and security, doesn’t it? #Newt
The most “overcompetitive” Booster task in history has released its ranking! Go check whether you made the list. I looked into it—there are already 30,000+ people participating in the Chinese-language cohort, and only the top 300 are counted. Isn’t that even more competitive than most projects in the past?
It ends in 4 days. On average, that’s 200 blocks per day. If you haven’t made the ranking yet, brothers, go check out the whitepaper of @grvt_io ! I think Grvt stands out mainly because its technical stack is ZKsync’s ZK Stack + Validium architecture. Grvt runs its own dedicated chain—an “omnichain” (Appchain)—within the zkSync ecosystem, so it won’t compete with other DApps for network resources.
You all keep hyping it, but I genuinely went and tested the trading myself! I found that its order-matching speed is indeed very fast and smooth. The official whitepaper data claims 600,000 TPS and sub-millisecond latency. This speed is on par with CEX-level performance!
And I carefully reviewed the whitepaper—there’s another key technical point: the ZKsync Atlas upgrade. With it, Grvt can verify and call in real time, trustlessly, using Ethereum mainnet’s existing capital (over $122 billion) as collateral for derivatives trading. No cross-chain bridge is needed, and no asset transfers are required. Your ETH sits on L1, and Grvt on L2 directly validates it can be used as margin. Sub-second finality, with liquidity freely flowing between Ethereum and all ZK chains.
Of course, no matter how amazing the claims in the whitepaper are, you still need to experience it yourself to be sure the experience is great. And what matters most to us is that after Grvt launches, the coin price doesn’t lag—we’re most looking forward to that! #grvt
Newton’s developer documentation—after three days, it felt like reading a book that never got finished
I spent three days reading Newton’s developer documentation. It’s not because I read slowly—it’s because it makes me keep thinking about a question: for a project whose mainnet Beta has already gone live, why are the developer docs written like this? The table of contents is arranged very neatly: beginner guide, API reference, SDK usage, contract deployment, example code—everything you’d expect is there, like a beautifully bound book. But when you open it, you’ll find that many chapters have titles only, with no content. VaultKit’s tutorial includes the installation steps, and then jumps straight to “Advanced Usage.” In between, the parameter explanations, configuration examples, and FAQs are all empty.
Validated the data source doesn’t mean you’ve validated the data itself—Newton’s mainnet Beta ran for a month. RedStone covered the gap, but only by half.
On June 23, Newton mainnet Beta went live. RedStone connected the verified price data into Newton’s policy execution layer. The press release reads beautifully—“real-time market price data,” “signed attestations,” and “auditable records.” VaultKit SDK was also released in sync, allowing developers to set rules such as spending limits, collateral requirements, and counterparty checks. RedStone covers more than 110 chains, and to date has never reported any pricing error incidents.
Many in the community interpret this as “Newton taking another step closer to institutional-grade.” This integration does indeed solve a problem I’d been worried about—previously, the policy engine lacked a reliable market data source. Now, each time a transaction reaches the authorization layer, the system queries RedStone for real-time prices, compares them against the policy rules, and then decides to allow or block. Each evaluation generates a signed attestation, forming an auditable record. Logically, it all holds together. #Newt
But I can’t be fully confident—there are two points.
First is concentration risk. Currently, Newton has only integrated one oracle. If RedStone has an issue—data interruption, being attacked, or simply price update latency—the policy engine loses its basis for judgment. That could cause transactions to freeze at a large scale. In 2024, a well-known lending protocol saw users incorrectly liquidated due to delays from a single oracle, resulting in losses of several million dollars. This isn’t a theoretical risk. $NEWT
Second is the granularity of evaluation. The policy engine makes decisions based on real-time prices. In extreme market conditions—when prices swing violently and the chain is congested—can RedStone’s update frequency keep up? The whitepaper doesn’t say. RedStone can do 2.4 millisecond updates on MegaETH, but Newton runs on EigenLayer AVS, and the settlement path depends on the Ethereum mainnet. RedStone’s price updates on Ethereum mainnet happen at minute-level intervals. If the ETH price “crashes” between two RedStone updates, Newton’s policy is still using the old price to judge—someone could submit a large withdraw, and the policy might incorrectly treat it as safe to allow. By the time the next feed comes in, the vault may already be underwater. @NewtonProtocol