derek (@dereklowrey) header
derek (@dereklowrey) profile picture

head of legal at @newtonlabs

Joined April 2010
Photo by derek (@dereklowrey)Photo by derek (@dereklowrey)Photo by derek (@dereklowrey)Photo by derek (@dereklowrey)Photo by derek (@dereklowrey)Photo by derek (@dereklowrey)
We published the private key to a wallet. The key alone still isn't enough to move its funds. @RektHQ asked our co-founder and CTO @0xdenniswon what stops a transfer once an attacker has the key. Full story: rekt.news/is-the-internet-re…
4
3
1
16
32,214
Private shares come with conditions that don’t disappear after issuance. The question we’re working on at Newton Labs is how to keep a fund’s terms enforceable as the token moves, with a record of each decision that investors and auditors can verify.
Tokenized pre-IPO shares carry rules: who can hold them, how much, for how long. They’re mostly checked once, at mint. In a lending market, they usually stop applying. We’re building @NewtonLabs to check them before every transfer, loan and liquidation. Read more in the blog 👇
1
2
4
343
Tokenized pre-IPO shares carry rules: who can hold them, how much, for how long. They’re mostly checked once, at mint. In a lending market, they usually stop applying. We’re building @NewtonLabs to check them before every transfer, loan and liquidation. Read more in the blog 👇
6
4
1
28
146,429
Newton Protocol's policy layer keeps expanding! 19 policy packs covering sanctions, transaction security, stablecoin risk, identity, and portfolio exposure More data sources. More enforceable rules. Current integrations cover: @arkham: Counterparty, Entity, Risk @Balancer: Pool risk @blockaid_: Transaction security @chainalysis: Sanctions and risk screening @PharosWatch: Redemption, Safe Mode, Treasury @redstone_defi: Oracle divergence @safe: Multisig security @sumsub: KYC and applicant status @vaultsfyi: Vault risk @mywebacy: Stablecoin depeg risk @withpersona: KYC and identity @xerberus_io: Common Cause, Liquidity Exit, What If Explore the packs: github.com/newt-foundation/n…
2
3
2
21
2,907
Earlier today, the attacker behind the recent @binance exploit, apparently in error, sent approximately 8.0M NEWT directly to the NEWT token contract address (0xd0ec028a3d21533fdd200838f39c85b03679285d), along with 17 other tokens: $ANIME, ethereum:0x8290333cef9e6d528dd5618fb97a76f268f3edd4, $ARPA, $BARD, $CELR, ethereum:0x3597bfd533a99c9aa083587b074434e61eb0a258, ethereum:0x0f81001ef0a83ecce5ccebf63eb302c70a39a654, $FTT, $GLM, $HIGH, $HOT, $KNC, $LQTY, $RARE, ethereum:0x259338656198ec7a76c729514d3cb45dfbf768a1, $SIGN and $WOO. These tokens are worth roughly $3.5 million at current prices. To be clear, the NEWT token contract itself was not compromised. We have reviewed the contract carefully, and unfortunately these tokens cannot be recovered. The NEWT token contract was built to be immutable: it has no owner or admin, all admin rights were renounced onchain in 2025, and upgrades are permanently disabled. That design exists to protect holders, so that no one, including the Foundation, can ever move or alter their tokens. These safeguards mean there is no way for anyone to retrieve tokens sent to the contract itself. These tokens are now permanently locked. They are out of the attacker’s control and can never be sold into the market. We have shared our findings with Binance and we will keep helping however we can.
51
36
29
394
140,649
proud to be part of this exciting new partnership with @l2iterative
Today we are excited to announce our private-market tokenization platform, targeting $500 million in tokenized holdings, with @l2iterative joining as founding partner!! 🎉 Read more ↓
1
29
Instead of telling people a system is secure, put the key out there and let people try to prove it isn't.
We published the private key to a Safe on purpose. The Safe holds test USDC. Take the key and try to withdraw the money: safe-totp-demo.newton.xyz Sign all you want. Without a 2FA code matched to the exact recipient and amount, @newton_xyz denies the transfer.
1
43
An early warning only helps if tools can act on it before the exit liquidity is gone. A dashboard that flagged risk and a vault that was still allowed to sit there are two different failure points.
Watch the SVB dip on this chart 👀 Circle disclosed $3.3B stuck at SVB on a Friday night. By Saturday USDC was at $0.87, and everyone heading for the exit was going through the same few Curve pools.
2
1
49
The data backs this up: by dollar value, most losses trace to compromised keys, not contract bugs. A step-up check in front of the signing action, not just around it, is key for operational security.
Most crypto hacks aren't smart contract bugs. Look at the data by dollar value and the majority come from compromised keys. Once an admin key breaks, nothing stops it. "Other than stopping blockchain." @0xdenniswon, co-founder of Newton Labs, on why opsec, not code, is the bottleneck for DeFi, and how Newton puts 2FA in front of a Safe wallet. Full episode 🔗 youtu.be/TxrfTSpqMiw
1
1
39
Everyone already has address intelligence. It's that the decision to allow, cap, or deny gets written down at the moment it happens, signed, checkable by anyone with the transaction hash. That's the difference between "we have a counterparty policy" and "here's the policy that ran, and here's proof it ran."
$104B reached sanctioned entities last year. None of it announced itself. @arkham labels the entity behind the address. Newton checks the label before your agent's transaction settles. Read more in the blog 👇
1
3
62
Escrow, clearing, and letters of credit all worked by putting a trusted third party in control of the asset. What's being built here is closer to the opposite: authorization without custody. The rule gets enforced before the transaction settles, but nobody has to hand over the keys to get that enforcement.
Escrow exists because "trust me" doesn't scale. Every system that moves money built a place where the rules hold. Onchain finance is building its own right now.
1
2
47
Honestly, any of them, as long as breaching the rule makes the transaction fail instead of generating a notification after it settles. A rule that can only alert you but fails to stop the harm isn't helpful.
If every crypto fund or vault came with ONE built-in safety rule, what should it be? (max loss circuit breaker? strict asset limits? something else?)
2
32
Monitoring has never once stopped a breach. That's not what it's for.
Replying to @NewtonLabs
4/ The industry's answer so far is monitoring. Dashboards, alerts, risk scores. Monitoring tells you the mandate was breached. It has never once stopped a transaction. That's not what it's for.
1
3
26
Every cycle has an unpriced risk. This cycle it's curated TVL with unenforceable mandates.
$100,000,000,000+ now sits in onchain vaults. ~$9B of it is run by curators. Amount protected by risk limits the curator physically cannot break: almost none. This is the biggest unpriced risk in DeFi right now.
1
2
29
Curating an onchain vault means real power over depositor capital — and today the only thing behind it is trust. @newton_xyz VaultKit checks every curator action against policy before it reaches the vault. Inside the rules, it executes. Outside them, it fails closed.
4
2
28
1,282
1/ Institutional capital moved onchain faster than the controls meant to govern it. Today that changes. Magic Labs is launching VaultKit, the SDK curators use to make a vault's rules enforceable onchain, alongside @newton_xyz mainnet beta launch! 🥳 🧵 vaultkit.newton.xyz
5
4
41
6,311
Newton Mainnet Beta is live! 🎉 VaultKit, the SDK that makes your vault’s rules actually enforceable onchain. Newton checks the rules before any transaction settles, then writes a signed attestation anyone can verify.
363
320
97
1,277
883,997
Introducing the @withpersona data oracle for Newton Protocol. Developers can use verified identity and residency attributes like age, nationality, and jurisdiction to define policies that enforce compliance before transactions execute onchain. No UI-level workarounds. No post-hoc monitoring. Read more: blog.newton.xyz/newton-proto…
8
6
2
102
7,841