abi (@0xabi96) header
abi (@0xabi96) profile picture

owner @noctralabs_ | digital assets, central banking, capital markets, blockchain stuff @bundesbank

Germany
Joined November 2020
Photo by abi (@0xabi96)Photo by abi (@0xabi96)Photo by abi (@0xabi96)Photo by abi (@0xabi96)Photo by abi (@0xabi96)Photo by abi (@0xabi96)Photo by abi (@0xabi96)Photo by abi (@0xabi96)Photo by abi (@0xabi96)Photo by abi (@0xabi96)
glad to have contributed to the prividium whitepaper as peer-reviewer with @bundesbank and @zksync
The financial industry requires private, incorruptible systems connected as one global network. Citi, Deutsche Bank, Mastercard, and 30+ top global institutions joined us to explore the power of Prividiums. Unveiling The Prividium Breakthrough Initiative.
6
4
1
61
6,873
See you in Madrid!
We're thrilled to reveal the 12 startups selected for the MERGE Madrid Startup Contest! This lineup covers the sharpest edges of Web3 and TradFi convergence. Meet them all: @veridexalethia · @OrionFinanceAI · ChainATM · Shellment · @alpha_aml · @FolksMobile · @blockvaultapp · @datablocks_app · @ChainComply · @themuxic · IdenQ · @investaxes Want to experience a full day of Web3 and crypto entrepreneurship? Attend the pitches, talks and networking for free. Register here: luma.com/socgruap
2
5
167
wtf just read about it, from @Quicknode to @privy_io . who else? metabase zero-day (unauthenticated SQLi, CVSS 10) exploited around Aug 3 hit multiple firms including privy via their analytics provider. reports indicate some end-user emails and metadata were exposed. wallet infra, auth, and keys stayed isolated and unaffected, but scary though. watch for phishing.
1
1
4
908
are you there with your company or as a visitor? let’s talk!
See you soon @money2020 🫡 Connect with the Noctra Labs team in Amsterdam, NL!
84
unpopular opinion: the idea of source code being out of scope is completely irrelevant in a security context imo. this is a part I really hate about this industry. whitehats find real issues but withhold them because they won’t get paid. but: no component is out of scope for a blackhat. this delta is where real exploits happen because these issues are chained together.
1
4
230
abi retweeted
Replying to @immunefi
@immunefi just solved duplicates for everyone. looks pretty neat!
it’s really a hate love. 🤞🏽 is there a valid way for whitehats to verify duplicates on @immunefi? the provided links don’t work.
4
4
1
26
1,679
no token allowlist is crazy work
🚨 @rhea_finance on NEAR was exploited for ~$18.6M In what on-chain data shows was a fully rehearsed, professional operation. Root cause: Rhea priced collateral from Ref Finance liquidity pools. The attacker minted their own worthless tokens, seeded their own pools with them, and Rhea's oracle happily valued the fakes as real, then lent real USDC, USDt, ZEC, and NEAR against them. Oracle manipulation + no token allowlist.
1
3
464
insane. next exploit. just 2 hours ago, bridged DOT on Ethereum has been exploited and dumped in the market. price is on a free fall. etherscan.io/tx/0x240aeb9a8b…
5
2
135
unbreakable
2
38
the hacker was testing 11 days ago xitter.cf/seunlanlege/status/203…
Lmao the uniBTC exploiter is testing @hyperbridge I hope you have a quantum computer bro bscscan.com/tx/0x2d30704b977…
1
112
Polkadot(@Polkadot) has been exploited. 🚨 The attacker minted 1B $DOT and dumped it all in a single transaction for 108.2 $ETH($237K). etherscan.io/tx/0x240aeb9a8b…
Readers added context they thought people might want to know
The exploit was on the Hyperbridge gateway contract, not Polkadot's core network. The attacker minted and sold 1B bridged $DOT tokens on Ethereum for ~$237K. x.com/CertiKAlert/st… etherscan.io/tx/0x240aeb9a8…
1
46
#CertiKInsight 🚨 We have seen an exploit on the @hyperbridge gateway contract. skylens.certik.com/tx/eth/0x… The attacker slipped through a forged message to change the admin of Polkadot token contract on Ethereum and profited ~$237K from minting and selling 1B tokens. Stay Vigilant!
1
50
if you’re a vc, hear me out: if you believe in founders, the location shouldn’t matter.
3
66
i’m 29. i wrote my first lines of code in 2016. i‘ll tell you how to get a job (works for any industry). this is 10 years of knowledge aggregated. it‘s my personal experience and a genuine tip on how to lead a conversation with strangers. not some engagement bait, ai slop or some bullshit psychological manipulation tactic. read closely. - find expired job offer - write hr if it’s possible to submit and that you just noticed it too late (email is always at the bottom) - take the chance to introduce yourself in 1-2 sentences in this same email - you will stay in their mind because you came last and they might have been already going through the applications important: don’t attach your cv in the first email. if they are interested, they will keep going and ask you for it. it gives you the spotlight without answering generic questions in a survey and enables direct contact to the decision maker, which also signals interest and isn’t pushy. if they want to meet you: schedule meeting in last weeks of applicants screening to even stay longer in their minds. but don’t stretch the process unnecessarily. make yourself rare and expensive, not desperate. people hire based on gut feeling, if skills are equal in a hypothetical scenario of multiple potential good candidates. don’t say that you can’t find a job. you’re literally an email away. you don’t have to send 50 applications per week or track your rejections in excel sheets.
1
1
5
192
mhm not really. try to work where no one is. make yourself rare. don’t apply at tech companies. send your cv to banks who are in need of these kind of people but don’t have the knowledge inside their company. i just met someone who worked at @Polkadot and now found a job inside a bank, surprise surprise
In a network of people whose contracts holding millions of TVL without a hack and struggling to find their next role I have seen my CTO friend in not actually getting any role. In my network in last 2 month only 1 dev get hired, that too part time. Web 3 developers are cooked.
3
207
very interesting to see @OpenAI experimenting with EVM. and you say crypto isn’t mainstream?
2
4
178
multi-agent setup wins in general, but opus is so fucking good
1
61
@AnthropicAI did the same in 2025 by the way.
New on our Frontier Red Team blog: We tested whether AIs can exploit blockchain smart contracts. In simulated testing, AI agents found $4.6M in exploits. The research (with @MATSprogram and the Anthropic Fellows program) also developed a new benchmark: red.anthropic.com/2025/smart…
1
90
everybody wants to be the Head of XYZ. nobody wants to do the work. i hate the wording that’s used in corporate. wdym the people that deliver are called *working group*? it’s literally degrading wording. better call them experts. cause without these experts, you will always be in search for someone who can execute the planning and ideas in your slide deck.
6
122
i have a weird feeling about the ecosystem as a whole. if your L2 can’t solve a problem for a very specific niche group, it will die soon with ethereum scaling up. if you just focused on performance and gas, sorry ngmi. ethereum mainnet will forcefully be the source of truth. also a weird sentiment is going on about people leaving this space. like literally 5 people alone I closely followed. what’s happening?
There have recently been some discussions on the ongoing role of L2s in the Ethereum ecosystem, especially in the face of two facts: * L2s' progress to stage 2 (and, secondarily, on interop) has been far slower and more difficult than originally expected * L1 itself is scaling, fees are very low, and gaslimits are projected to increase greatly in 2026 Both of these facts, for their own separate reasons, mean that the original vision of L2s and their role in Ethereum no longer makes sense, and we need a new path. First, let us recap the original vision. Ethereum needs to scale. The definition of "Ethereum scaling" is the existence of large quantities of block space that is backed by the full faith and credit of Ethereum - that is, block space where, if you do things (including with ETH) inside that block space, your activities are guaranteed to be valid, uncensored, unreverted, untouched, as long as Ethereum itself functions. If you create a 10000 TPS EVM where its connection to L1 is mediated by a multisig bridge, then you are not scaling Ethereum. This vision no longer makes sense. L1 does not need L2s to be "branded shards", because L1 is itself scaling. And L2s are not able or willing to satisfy the properties that a true "branded shard" would require. I've even seen at least one explicitly saying that they may never want to go beyond stage 1, not just for technical reasons around ZK-EVM safety, but also because their customers' regulatory needs require them to have ultimate control. This may be doing the right thing for your customers. But it should be obvious that if you are doing this, then you are not "scaling Ethereum" in the sense meant by the rollup-centric roadmap. But that's fine! it's fine because Ethereum itself is now scaling directly on L1, with large planned increases to its gas limit this year and the years ahead. We should stop thinking about L2s as literally being "branded shards" of Ethereum, with the social status and responsibilities that this entails. Instead, we can think of L2s as being a full spectrum, which includes both chains backed by the full faith and credit of Ethereum with various unique properties (eg. not just EVM), as well as a whole array of options at different levels of connection to Ethereum, that each person (or bot) is free to care about or not care about depending on their needs. What would I do today if I were an L2? * Identify a value add other than "scaling". Examples: (i) non-EVM specialized features/VMs around privacy, (ii) efficiency specialized around a particular application, (iii) truly extreme levels of scaling that even a greatly expanded L1 will not do, (iv) a totally different design for non-financial applications, eg. social, identity, AI, (v) ultra-low-latency and other sequencing properties, (vi) maybe built-in oracles or decentralized dispute resolution or other "non-computationally-verifiable" features * Be stage 1 at the minimum (otherwise you really are just a separate L1 with a bridge, and you should just call yourself that) if you're doing things with ETH or other ethereum-issued assets * Support maximum interoperability with Ethereum, though this will differ for each one (eg. what if you're not EVM, or even not financial?) From Ethereum's side, over the past few months I've become more convinced of the value of the native rollup precompile, particuarly once we have enshrined ZK-EVM proofs that we need anyway to scale L1. This is a precompile that verifies a ZK-EVM proof, and it's "part of Ethereum", so (i) it auto-upgrades along with Ethereum, and (ii) if the precompile has a bug, Ethereum will hard-fork to fix the bug. The native rollup precompile would make full, security-council-free, EVM verification accessible. We should spend much more time working out how to design it in such a way that if your L2 is "EVM plus other stuff", then the native rollup precompile would verify the EVM, and you only have to bring your own prover for the "other stuff" (eg. Stylus). This might involve a canonical way of exposing a lookup table between contract call inputs and outputs, and letting you provide your own values to the lookup table (that you would prove separately). This would make it easy to have safe, strong, trustless interoperability with Ethereum. It also enables synchronous composability (see: ethresear.ch/t/combining-pre… and ethresear.ch/t/synchronous-c… ). And from there, it's each L2's choice exactly what they want to build. Don't just "extend L1", figure out something new to add. This of course means that some will add things that are trust-dependent, or backdoored, or otherwise insecure; this is unavoidable in a permissionless ecosystem where developers have freedom. Our job should make to make it clear to users what guarantees they have, and to build up the strongest Ethereum that we can.
3
140