709 Photos and videos
ً retweeted
Jun 12
thank you to the @Keycard_ team for this partnership! we do more than just funding 🙌
Jun 12
Protocol Guild is excited to announce that all members will receive complimentary @Keycard_ Shell hardware wallets
The tools they rely on should reflect the same values they bring to their work: open source, self-custodial, and uncompromising on security
2
17
1,221
ً retweeted
New post: a history of account abstraction in Ethereum, from EIP-86 to Frame Transactions. The trade-offs, how the thinking evolved, and why we're still talking about it.
paragraph.com/@cethology/acc…
2
5
23
2,221
ً retweeted
Jun 10
EIP-7708 will fix this in the next upgrade, Glamsterdam! - learn more at the link:
forkcast.org/eips/7708
Jun 10
First, the problem. On Ethereum, native ETH transfers emit NO events.
If you want to track them, you need to trace every single transaction with a tracing node and build your own indexer. Expensive, slow, painful.
5
14
77
14,963
ً retweeted
Jun 5
The Zcash engineers are my family, and everything good in my life traces back to Zcash. I couldn't live the rest of my life knowing I committed that kind of betrayal.
15
42
450
43,319
Jun 4
EIP-8037 is scheduled for Glamsterdam and will increase the gas cost of creating new accounts and writing to new storage slots by 5-8x.
What protocols have hard-coded expectations about state gas costs? What is at risk of breaking?
10
24
136
16,703
ً retweeted
May 26
Great website. Looks like native account abstraction is possible in next-next upgrade.
Early 2027 probably.
May 25
Easy-to-have-missed update to the @ethereum governance process: the "Scheduled" status has a new definition that makes it easier for you to plan for upcoming features
A thread 🧵 for
1. what changed
2. why it matters for the ecosystem
↴↴↴↴↴
1
5
1,472
ً retweeted
May 26
I like the body of work emerging around frame transactions.
This specific EIP allows transactions to reference specific application roots instead of fluctuating live state. The result is safer and more predictable inclusion.
For block construction today, this makes some transactions more self-contained, which is a big plus for multi-party block building.
May 26
New EIP-8272: Recent Roots for Frame Transactions
by @soispoke, @nero_eth and @VitalikButerin
Another EIP to enable native, trustless, censorship-resistant privacy on Ethereum.
tldr: Private transactions on Ethereum often need to prove against a recent commitment tree root. This EIP lets a FrameTx carry that root directly in its signed envelope.
The protocol checks that the root was written onchain for the referenced slot and is still inside the usable window. This means validation can use the root without reading arbitrary application storage.
The goal is to help private transactions get FOCIL inclusion guarantees by making recent roots part of the partial state attesters will store after the transition to zkEVM.
Target fork: Hegota
Links below 👇
1
14
1,616
ً retweeted
May 25
The Infinite Garden needs gardeners that plow the fields, weed the weeds and plant the seeds.
Not everyone can water the plants or count the buds.
11
6
67
3,299
ً retweeted
May 20
Hegota is for Hardness
- Censorship Resistance with FOCIL
- Native, trustless privacy with Frame Transactions and Keyed Nonces
May 20
Short-term things being done to shift Ethereum toward native privacy:
* AA FOCIL (makes privacy protocol txs, among many other things, first-class with strong inclusion guarantees)
* Keyed nonces: x.com/soispoke/status/205163…
* Access-layer work (Kohaku, private reads...)
2
5
42
4,006
ً retweeted
May 19
Most python libraries (like web3.py) previously maintained by the @ethereumfndn, will now be maintained by @ApeFramework. Super excited for the next chapter!
No action needed for devs. All issues, PRs etc have been migrated.
Installing also is exactly the same
May 18
An important update from us:
paragraph.com/@apeworx/intro…
4
5
42
8,321
ً retweeted
May 15
I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.
I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really).
It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely.
The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture.
We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying.
I worry.
512
1,901
15,328
1,586,213
May 15
Important Announcement
Trading on THORChain is currently halted after a vault was compromised. Initial indications are user funds are safe and only protocol owned funds are affected.
The network automatically detected abnormal behavior and halted signing activity, which alerted the broader community and prevented further outbound transactions.
The investigation is still ongoing to determine the root cause. Contributors are actively working on the issue and we will report updates as we progress toward a solution.
What we currently know:
* One of the six Asgard vaults appears to have been compromised.
* Current estimates place the loss at approximately $10.7m USD
* The network automatically detected the abnormal behavior and halted signing activity, preventing further outbound activity.
* Nodes securing the vault were subject to their bonded RUNE being slashed as a result of the unauthorized outbound transactions.
* Churn activity has been paused while the investigation and remediation efforts are ongoing.
* Onboarding additional chains and operations requiring churns will be delayed until the network is stabilized.
* Initial indications show no individual user swaps were affected.
We are asking all node operators to immediately review their infrastructure, hosts, key management systems, and operational security for any signs of compromise or abnormal behavior, and to report anything suspicious in Discord.
Node operators participating in the affected vault are requested to securely provide Bifrost logs to the dev team for analysis using 'make relay' .
38
32
388
30,639
i look at pure research with a bit of contempt. it's for people who don't get their hands dirty and don't want to take the risks of seeing their idea perform in production. you just spent years in an insulated ivory tower, while others have a live feedback loop collecting data in the trenches.
14
8
118
13,123
ً retweeted
May 12
0/ Clear signing is now live.
An open standard to end blind signing, making human-readable transactions default.
This effort brings a major UX and Security upgrade to transaction signing on Ethereum.
160
443
2,180
323,718
ً retweeted
May 11
🔐 EIP-8250: Keyed Nonces for Frame Transactions 🔐 was just merged, also check out this nice EIP explorer 👀
eips.sh/eip/8250
7
6
50
2,566