GetStable (π¦,π) retweeted
I could not be more bullish on EIP-8288.
It's very rare in technology to see such an inversion where a property which was hindering scaling (in this case, the highly decentralized Ethereum node ecosystem) is flipped to now *enable* scaling.
Over the past few weeks I've gone from thinking leanPCS is total bull to being a total bull. So let me explain some of these buzzwords in more detail.
At the core, 8288 is about hyper-scaling data and execution for any computation that needs to get performed on a piece of data once, the chain learns the answer, and then we never need to see that data again. This sounds very specific, but it includes most "heavy" things happening on Ethereum:
* Signatures
* STARKs
* Merkle branches
* FHE computation
* ...
Really the first two are the most important.
Once we go quantum-safe, signatures get bigger (65 bytes ECDSA -> 1-6 kB WOTS/SPHINCS depending on params) and ZKPs get much bigger (200-1000 bytes with groth16, PLONK, etc -> 128 kB with STARKs). This is unsustainable to put on chain, and 8288 fixes this.
8288 works by aggregating STARKs in the mempool. First, you as a user generate the STARK or SPHINCS signature or PCS opening (more on that last one later), and publish it. Then, each node listens. Each tick, each node takes all of the new objects that it has seen, and generates a STARK containing a list of "claims":
"pubkey P has signed message M"
"program X run on data D has output Y"
"p(X) = Y for some polynomial P whose hash is H"
and a proof that it has seen a signature, STARK or PCS opening verifying those claims. So the only information getting re-broadcasted is:
(i) hashes of inputs and outputs (~64-96 bytes per claim)
(ii) a single STARK proof per tick
These aggregate proofs themselves get re-aggregated, and eventually you get to a single "master proof" in the block, that verifies that all of those statements are true. And so the only other data that has to actually go on chain is the statements (the (P, M), (X, D, Y), (X, Y, H) tuples I described above), not the actual signatures or proofs. This gets put into a specialized frame type.
Now, let's get into the leanSPHINCS vs leanSTARK vs leanPCS part.
The core distinction is: *what is the underlying object that the user is creating?*
In leanSPHINCS, it's a signature, and specifically this particular type of purely-hash-based signature: ethresear.ch/t/sphincs-minusβ¦
If we add leanSPHINCS, then users will be able to make quantum-safe accounts, and pay only a little bit of gas (4096 for the 64 bytes) for each signature. So we get scalable quantum-safety for regular accounts, multisigs, etc. But it's only one specific signature scheme, you can't do anything else.
In leanSTARK, it's a STARK. This means it's fully general: the user runs whatever computation they want, and publish a STARK of it. So you can use it for:
* Any signature scheme (including eg. lattice-based ones if you like those)
* A multisig that hides its internal logic
* Privacy protocols
* Private account abstraction: authorization logic that depends on some value hidden elsewhere in the state, so you can have one key that controls all your accounts without publicly linking them to each other
Basically, it's a free for all, in the same way the EVM is a free for all.
But leanSTARK has a practical downside. The protocol would have to specify the language in which users write their programs (we call this the "ISA"). So we would have to agree on that language. This is a really big deal - it's the first big case of "Ethereum moving beyond the EVM" - and so it's likely to take time to agree on the details of it, especially since the ISA would be hard to upgrade. There are benefits to taking longer on this, figuring out the ideal ISA, and then even giving access to it inside regular contracts.
LeanPCS is the third option. PCS stands for "polynomial commitment scheme": a proof that P(x) = y. The most important thing to know about PCSes is that they are by far the most important "hard" component of a STARK (see here: vitalik.eth.limo/general/202β¦ ). If you have a "magic PCS oracle" (which from the EVM's point of view, 8288 is), you can verify a STARK in ~20-40k gas.
The most important gain with PCS is that there is far less that we need to choose. Specifying a PCS only requires specifying a field, and there is a natural option: the 128 bit binary field (technically, we can go more general than that, and say the 2^k-bit binary recursive tower field, going up to 256)
LeanPCS is less efficient than leanSTARK onchain, because you would have to put multiple claims to prove one thing. But it's arguably more efficient offchain, because you have much more flexibility to choose proof systems.
But most importantly, leanPCS gives you the same generality as leanSTARK, in a way that could potentially be implemented very quickly. And once we figure out the ISA, we can add leanSTARK later.
So there is a route to getting "the cryptographic proof singularity" much faster than any of us expected, and that route runs through 8288 with leanPCS.
firefly.social/post/x/212092β¦
GetStable (π¦,π) retweeted
Major updates: Acquisitions, Tokenomics
Katana is moving from opinionation to ownership.
Most chains rent their products. Apps arrive with the hype and leave when it runs out. The revenue leaves with them. That model is broken.
So we did something different.
We bought the protocols that provide a secure foundation for everyday DeFi activities, and open them up to anyone that wants to create utility for their asset or build on top and deliver a different user experience than our App.
The acquisitions also allow us to begin $KAT buybacks across four revenue streams, which will start next week. We are a startup and believe the majority should be reinvested into growth, but want to make it clear there is no equity and the teamβs upside is solely the token, which remains locked.
Katana has evolved from being a chain to an application with infrastructure-like characteristics, and will continue in this trajectory while focusing on user experience, distribution, and differentiation.
GetStable (π¦,π) retweeted
Earn+ caps filled up in days.
We've just opened up more space. Now there's twice as much room for you to save with 12% APY.
Open the app β Earn+ β Add money
GetStable (π¦,π) retweeted
Ethereum the only credibly neutral blockchain is sitting on a massive price base
Buying ETH today is like buying BTC in 2012
GetStable (π¦,π) retweeted
AI & crypto are going to intersect in an even bigger way than stablecoins for payments.
GetStable (π¦,π) retweeted
We're excited to announce partnership with @BitGo to launch a validator built for institutions.
BitGo's institutional clients can now stake SOL with Jupiter, directly from their existing custody accounts.
Solana's leading DeFi platform, meet the custodian institutions trust.
GetStable (π¦,π) retweeted
Aerodrome (@aeroxyz) has just flipped Uniswap to become the number one DEX in 24h holder revenue.
Built a daily dashboard to track @standard_rsv's growth and progress toward the long-term thesis I outlined in my report.
Made it public for anyone interested in following along: standardrsvmonitor.github.io
Covers key metrics from protocol revenue and stock-pool market share to reserve holdings, token supply, and banker activity.
GetStable (π¦,π) retweeted
Will Uniswap or Aero revenue be higher this week?
Currently they're neck and neck, but the market says 70.2% chance Aero revenue is higher.
You can now trade protocol revenue and exploit odds. We're partnering with Trueo to launch new prediction markets that settle based on DefiLlama data.
Revenue Markets
If you follow the revenue meta, you can now trade that directly on Trueo. We launched markets for Hyperliquid, Pump, Aero, Uniswap, Collector Crypt, and Papertrade revenue.
Exploit Markets
Hedge against exploit risk by trading the odds of total DeFi hacks and exploits of specific protocols. We have markets for whether there will be exploits of Aave and Morpho this month. We also have weekly and monthly markets for the size of the largest hack.
Other Onchain Metrics
Robinhood Chain RWA mcap, Robinhood Chain DEX volume, and whether Solana or Base ends the week with higher TVL.
defillama.com/predictions
Janus Henderson, a $480 billion asset manager, took a position in Ethena's ENA in June and plans to use staked USDe for cash management. Ethena is integrating Janus Henderson's AAA CLO strategy, JAAA, into USDe's reserves.
@ethena
GetStable (π¦,π) retweeted
ETH supply is up about 1% since the Merge.
In the same time period:
> solana:So11111111111111111111111111111111111111112 supply grew 66%, from 354M to about 589M.
> ripple:native supply grew 27%, from 49.83B to about 63.1B.
> cardano:native supply grew about 10%, from 34.18B to about 37.5B to 38B.
> bitcoin:native supply grew 4.96%, from 19.15M to about 20.10M.
> ethereum:native supply grew 1.0%, from 120.52M to about 121.7M.
GetStable (π¦,π) retweeted
V3 is live, and the first builders are already emerging. Vaults and RWAs launch soon to fuel the fire.
Options are here to stay and they'll take many forms; yield generation, hedging and chasing outsized returns. They'll be traded through institutional retail-friendly interfaces alike, integrated into wallets and incorporated into structured yield products offered by Neobanks.
The pie is growing, and there's room to build something big.
GetStable (π¦,π) retweeted
Calling all perps traders π£
The next cycle of our bi-weekly trading competition starts NOW. Rewards can be earned based on both volume and PnL.
$130,000 is up for grabs, will you get a piece of it?







































