
Cardano SPO @DIGI_StakePool | Midnight Validator | USN Senior Chief (ret) | Former Ocean Systems Engineer @ Progeny | Stake Ada at https://xitter.twitterapi.xyz/t.co/BGdeNiutYd | USA ๐บ๐ธ
Virginia, USA
Joined December 2011
- Tweets2.2K
- Following7.9K
- Followers85.2K
- Likes15K
I love grinding my own coffee at home. About 30 cents per cup.
I had some of the best coffee in the world like at Gaeta, Italy for Italian, Antalya Turkey (my favorite), and Haifa Israel at a local coffee shop. So now I get to experiment at home making various types. Kinda nice.
10
45
2,539
Just cut my freshly planted grass that I put down in September. Looking pretty good.
At least we got something green on X. ๐
8
70
1,538
Great news from SPO call, benchmarking is looking good to use LSM on Cardano validators using very fast SSDs. Meaning that ledger state can be stored on SSD vice RAM, keeping node requirements lightweight while expanding capacity.
Guidance will be in 11.2.1 release notes. ๐ฅ
On Cardano SPO call right now, node version 11.3 in December will have Linear Leios capability.
Still needs testing and tuning on testnet, but happy we are getting closer! ๐
Cautious rollout to monitor performance & optimizations considering the absolutely massive throughput.
I killed off my old grass (mostly weeds and clovers) almost 3 months ago then planted new grass two months ago. Pretty happy with how itโs growing before winter.
So today a $200 million dollar privacy layer blockchain vaporized that was founded or funded by Sequoia, Electric Capital, a16zโฆ etcโฆ the usual shitcoin culprits who are fckn up everything about crypto
The bottom is nigh folks, hang in there ๐ช
Later today, we are officially ending all remaining support for the Iron Fish network.
A few days ago, we observed abnormal activity involving wIRON and the ChainPort bridge. After working with ChainPort and reviewing their logs, we discovered that the cause was an inflation bug in the Iron Fish blockchain itself.
We traced the bug to a commit from early 2019 in the Merkle tree implementation. The developer at the time implemented a standard Merkle tree. However, because of nuances in how a noteโs nullifier is calculated (the mechanism that lets a normal user spend their funds), the attacker was able to spend the same note more than once.
The attacker then compounded the exploit, aggregated their notes, and exited through the ChainPort bridge. This code path was within the scope of both our external and internal audits, but the bug wasnโt caught during review.
For closure, weโve committed the patch for the exploit, with a detailed postmortem included in the PR, before shutting down and archiving the ironfish repo.
The meta-analysis here is that software that canโt be upgraded immediately (most of crypto), is in an extremely precarious position. The ability to find and exploit vulnerabilities in technically complex code is becoming commoditized. Safety guardrails on US frontier models make it difficult for companies to use them to patch security vulnerabilities, while abliterated open-source models are approaching frontier capabilities.
We wish everyone all the best, and we hope crypto finds a path through this.
Thank you all.
Never deleting this app ๐คฃ๐คฃ๐คฃ
Hey @grok, if civilization collapsed tomorrow and we had to rebuild society from scratch, what 10 professions would become the MOST valuable overnight? Rank them and explain why.
So two new major blockchains launched this week to enable AI autonomous agent payments blah blah blah blah umpty fck releasing more coins into an already heavily diluted market even tho 16 blockchains recently deactivated. Congratulations to whoever made this novel innovative never before seen thing-a-ma-bob widget.
hashtag the future of finance is nigh













