A couple of days ago, I chatted in a group with a few developer friends about all the new projects that have popped up recently in the DeFAI space. One of my friends suddenly sent a screenshot and said, “Look at this—an address that has already been blacklisted by the whole internet, yet it still managed to successfully transfer a large amount of assets from a contract.”
The group instantly blew up. Some people cursed the project team for being inactive. Others blamed malicious nodes. And some even spun conspiracy theories, saying it was done by an insider.
But after staring at the transaction record for a long time, the question that kept nagging me was: if this system has been running for so long, why was there no mechanism in place beforehand to stop such an abnormal operation?
Following that doubt, I went through the whitepaper of @NewtonProtocol and found that Section 9.3 specifically discusses a controversial dispute-resolution mechanism. In short: during the challenge period, anyone can submit a zero-knowledge proof, using pure mathematical logic to prove that a given signature or operation is invalid. Once the verification passes, the staked tokens of the malicious node are directly slashed.
And the threshold is low. You don’t need to hold $NEWT , and you don’t have to be a node. As long as you have the technical capability, you can act as a challenger/oversight participant.
At its core, this design hands the network’s security over to the community, rather than relying on some centralized team. In the DeFAI field, Newton uses a combination of ZKP + TEE, providing two layers of proof—cryptographic and hardware—for operations like cross-chain rebalancing and loss mitigation. Compared with execution schemes that are completely black-box, the transparency is indeed higher.
However, when I checked its CertiK audit page, I found that some modules are still in an unverified state, and the code security score still has room for improvement. No matter how beautiful the technical architecture is, if audits can’t keep up, that’s still a risk.
Verifiable execution is definitely a plus, but in the long run, we still need to see whether real on-chain activity and the ecosystem can actually take off. Let’s wait for the next audit updates—then we’ll go by the on-chain data to see the truth. #Newt
The group instantly blew up. Some people cursed the project team for being inactive. Others blamed malicious nodes. And some even spun conspiracy theories, saying it was done by an insider.
But after staring at the transaction record for a long time, the question that kept nagging me was: if this system has been running for so long, why was there no mechanism in place beforehand to stop such an abnormal operation?
Following that doubt, I went through the whitepaper of @NewtonProtocol and found that Section 9.3 specifically discusses a controversial dispute-resolution mechanism. In short: during the challenge period, anyone can submit a zero-knowledge proof, using pure mathematical logic to prove that a given signature or operation is invalid. Once the verification passes, the staked tokens of the malicious node are directly slashed.
And the threshold is low. You don’t need to hold $NEWT , and you don’t have to be a node. As long as you have the technical capability, you can act as a challenger/oversight participant.
At its core, this design hands the network’s security over to the community, rather than relying on some centralized team. In the DeFAI field, Newton uses a combination of ZKP + TEE, providing two layers of proof—cryptographic and hardware—for operations like cross-chain rebalancing and loss mitigation. Compared with execution schemes that are completely black-box, the transparency is indeed higher.
However, when I checked its CertiK audit page, I found that some modules are still in an unverified state, and the code security score still has room for improvement. No matter how beautiful the technical architecture is, if audits can’t keep up, that’s still a risk.
Verifiable execution is definitely a plus, but in the long run, we still need to see whether real on-chain activity and the ecosystem can actually take off. Let’s wait for the next audit updates—then we’ll go by the on-chain data to see the truth. #Newt