Pinned Tweet
Replying to @0xPanda9
0xPanda retweeted
We just discovered almost a million public URLs that OpenAI’s agents left behind when hacking Hugging Face, leaking credentials and attack details that could have allowed anyone who found them to compromise the company. 🧵
Crypto has its hard time and @LayerZero_Core team diversifies their investment.
0xPanda retweeted
In light of today’s SpaceX IPO, a story from inside Jane Street on the day of the 2012 Facebook IPO:
0xPanda retweeted
don't understand why so many debates about agent identifies. give is a public key. put it on chain. done.
Replying to @henrythe9ths
lmao Henry, you're the super[.]com CTO
0xPanda retweeted
For the last 30 years we were always 5 years away from Quantum Computers.
But sentiment suddenly flipped. Technology is suddenly improving. In just the last couple of weeks, Google suggested Q-day could come as early as ~2029, and new research points to breaking ECC requiring far fewer qubits than previously thought.
We still don’t know when quantum will come to reality. But to me, one thing is more clear than ever - when it comes, it will be sudden.
For blockchains, dealing with quantum is both a blessing and a curse. Yes many, besides Bitcoin, support “upgrade” mechanisms. But migrating liquidity, wallets, and applications is a nightmare.
@arc is built with quantum threat in mind from day one. A practical roadmap allows to both support existing ecosystem of tools and apps built around ECC cryptography, but also have quantum-safe built-in mechanisms (like signatures and checkpoints) to keep assets bullet proof.
One of the most unique and interesting aspects of the architecture is that because @arc will leverage confidential compute subspace. Within that subspace, all assets, applications, and transactions will be private and PQ secure by default. So, for instance, you can still generate a traditional ECC key within the subspace, but because of the extra layer of PQ encryption build on top, the keys and interactions fully hidden from adversaries.
Stay tuned for more.
@jerallaire of @circle explains on @tbpn ⬇️
Discovered my Gas ID via ETHGas - turning my gas spend into rewards 🫘
As a Hero Jack, I've spent 2.2208 ETH on gas but earned 1500 Beans back.
Get your Gas ID and Beans here: ethgas.com/community/gas-rep…
0xPanda retweeted
In the last 2 weeks, the @axelar ecosystem launched two new products leveraging its unique connections across chains:
🔗 fullport.finance/ — the gateway to bridging & trading for @HyperliquidX
💠 midas.app/mxrp — the yield-seeking asset for XRP.
This is the beginning of what chain agnostic experiences will look like over the coming year.
0xPanda retweeted
The Senate just killed the most important crypto bill in US history.
After months of bipartisan work, the GENIUS Act had real momentum.
Until Elizabeth Warren rallied Democrats in a last-minute revolt to block it.
Here's how politics is costing the US its financial future:
0xPanda retweeted
Time to unite.
Improving crosschain UX is a top priority. But what is the most effective path to solving it and where do standardization efforts best fit in:
Notes from the most recent Interop Working Group & ERC-7786 as a way to unify message passing protocols under a simple API ↓ ↓
TLDR:
- OpenZeppelin, Axelar, and Espresso gave an overview of 7786: a unified API to allow applications to work with any message passing protocol across chains
- from Axelar: "Generally I don’t like standards, except when there is a bottleneck. And in the Ethereum community, a lack of a standard here is really a bottleneck that I keep seeing over and over again"
- 7786 is designed to be as minimal and lightweight as possible, with adapters to plug into the main messaging standards
- Similar to agreeing on a format for mailing addresses, but you can easily use different providers to deliver the package (eg UPS or FedEx)
- Seeking community feedback and aim to finalize in next few weeks ✅
----
Notes and recording: notes.ethereum.org/@rudolf/i…
----
Thanks to all who represented on the call today!
@axelar, @OpenZeppelin, @EspressoSys, @trainprotocol, @lifiprotocol, @wonderland, @circle, @1kxnetwork, @etherspot, @routescan_io, @MetaMask, @Scroll_ZKP, @Uniswap, @hashialliance, @blocknative, @t1protocol, @hyperlane, @puffer_finance, @fabric_ethereum, @Polymer_Labs, @LineaBuild, @RiscZero, @AcrossProtocol, @radius_xyz, @EverclearOrg, @LayerZero_Core, @0xsequence, @glacislabs, @zksync, @ZuBerlinCity, @rhinestonewtf, @offchain, @sprinter_ux, @blockaid_, @l2beat, @CoWSwap, @base, @0xAarc, @bootnodedev, @wormhole, @OmniFDN, @Alchemy
0xPanda retweeted
I’ve only worked on standards three times in my life:
1. I led the effort to standardize BLS signatures for @ethereum (datatracker.ietf.org/doc/dra…) when the ecosystem couldn’t converge on an implementation.
2. I collaborated with many cryptographers to standardize FHE primitives (eprint.iacr.org/2019/939).
3. And now, this work with the @OpenZeppelin team.
I don’t standardize things when industries are still evolving and moving fast. But this is different. The @ethereum community is falling behind due to the lack of simple APIs to follow across L2s and other chains. And it's easy to fix.
Agreeing on a simple set of APIs for cross-chain messaging is like agreeing on what a snail mail envelope should look like. There’s no real innovation there at this point — most providers offer similar things. What differentiates solutions is the unique security and delivery guarantees they provide under the hood (think choosing between Amazon or USPS for shipping packages).
Many application-level protocols (like intents) and middleware (explorers, wallets) need a consistent, neutral spec they can rely on to keep building.
It's time to agree and move on to building!
See ERC-7786 and comment: github.com/ethereum/ERCs/blo…
0xPanda retweeted
For nearly a year, we've been collaborating with Ethereum teams on cross-chain messaging standards and a close collaboration with @axelar on research, design, and engineering.
The result? The ecosystem has come together around ERC-7786, a universal cross-chain messaging standard that helps devs build once and interoperate across multiple protocols, cutting vendor lock-in.
7786 gives us:
• Common interface for sending/receiving cross-chain messages
• Flexible “attributes” for custom protocol features without breaking the core standard
Check out the full spec 👇
github.com/ethereum/ERCs/blo…
After a series of great discussions and collaborations with the @OpenZeppelin team, we put together the foundational spec for interop: ERC-7786.
The spec has been built to be neutral and vendor-agnostic, but relies on the lessons we’ve learned over 5 years of building interop. All application-level protocols will rely on: intents, multi-bridge aggregation, token transfers, and cross-chain governance
(see the framework: sergeynog.substack.com/p/hit…).
Today, the @ethereum community converged on adopting it as the base layer for cross-chain messaging.
Great work to the team building, and to the projects reviewing and supporting it. Ethereum UX will unify.
🔗github.com/ethereum/ERCs/blo…
0xPanda retweeted
Last week, Scroll Sepolia underwent its biggest upgrade yet, transitioning from Halo2 to a zkVM.
I want to take a moment to highlight the broader benefits of zkVM for the entire technical community. Until now, deploying a custom zkRollup has been nearly impossible for small development teams. zkEVM implementations from Scroll, Polygon, and Linea contain tens of thousands of lines of code that require deep ZK expertise to understand—effectively making them black boxes for most developers, with little room for modification. (1/3)























