biliboy101

if you could build anything on solana today, what would it be?

Been wrong before but this one feels different.

Another day bullish on crypto. DYOR and hold tight #Crypto #BTC

hey i’m new to crypto, what should i do?

DeFi didn't kill banks. It just reminded us we never needed permission to move our own money. Seven years holding bitcoin taught me that. The code was always the point. #DeFi #Bitcoin

My honest thoughts about the Solana ecosystem right now: Even though I’m still extremely bullish, the ecosystem genuinely feels very different from before. We’ve built more apps, improved infra, onboarded more users, more institutions, more capital, and generated more revenue than ever before. The ecosystem is objectively stronger. But somehow it also feels more lonely than before. The space got so big that many of us don’t even know each other anymore. Things feel more artificial, distant, and transactional. Back in 2021, the community itself carried Solana on its back. The devs were eating glass 24/7, creators onboarded users out of pure conviction, and the narratives were built organically by the people. The foundation barely even had a social presence back then. The community had the power. Now it feels like too many people rely on the foundation, engagement algorithms, institutional validation, and coordinated narratives to shape the culture for them. I mean "Solana kols" are now foundation members. And that’s where I think things become dangerous. If the narratives of the ecosystem are artificially constructed and amplified from the top down, the culture slowly loses authenticity. People stop thinking for themselves and just start echoing whatever is placed in front of them. The culture became bigger, but weaker. It's more efficient forsure, but less human. A lot of people no longer love Solana itself. They just use Solana because the tech is good or because the current meta is here. There’s less collective identity, less emotional attachment to the chain, and less genuine support between builders unless there’s financial incentive attached to it. Back then we all felt responsible for pushing Solana forward together. Now many people just spectate lol. The Solana I fell in love with was built around real communities, nfts, friendships, chaos, conviction, and collective belief during the hardest times. Not just perps, casinos, AI agents, and whatever the next shiny meta is. Maybe this is simply what happens when ecosystems mature. Maybe I'm just too washed now. I genuinely miss when the people themselves felt like the soul of Solana.

Sent another 64 ETH to the Animal Welfare Fund. I encourage others to think and act more in support of our non-human cousins too! The extreme suffering we're imposing on them in the billions is not something we talk about often, but it continues to be one of the larger blights on humanity. And I'm getting optimistic that this century we can finally end it. Farming practices are improving, synthetic alternatives are improving. Also, in my recent experience, good old low-tech vegetarian and vegan food has improved massively worldwide over the last ten years; I encourage anyone who has tried it long before and given up to take second look; there are far more healthier and tastier options today than the "pasta and salad" you would often get ten years ago.

Now down nearly one entire FTX bankruptcy*

JUST IN: 🇺🇸 SEC delays plan to allow blockchain-based tokenized stocks.

Feel free to disagree — genuine takes welcome.

ETH just keeps building while others talk🔥 Layer 2s are insane rn, fees are nothing and speed is everything. This is what real infrastructure looks like 👀 #Ethereum #ETH

Now, the quantum resistance roadmap. Today, four things in Ethereum are quantum-vulnerable: * consensus-layer BLS signatures * data availability (KZG commitments+proofs) * EOA signatures (ECDSA) * Application-layer ZK proofs (KZG or groth16) We can tackle these step by step: ## Consensus-layer signatures Lean consensus includes fully replacing BLS signatures with hash-based signatures (some variant of Winternitz), and using STARKs to do aggregation. Before lean finality, we stand a good chance of getting the Lean available chain. This also involves hash-based signatures, but there are much fewer signatures (eg. 256-1024 per slot), so we do not need STARKs for aggregation. One important thing upstream of this is choosing the hash function. This may be "Ethereum's last hash function", so it's important to choose wisely. Conventional hashes are too slow, and the most aggressive forms of Poseidon have taken hits on their security analysis recently. Likely options are: * Poseidon2 plus extra rounds, potentially non-arithmetic layers (eg. Monolith) mixed in * Poseidon1 (the older version of Poseidon, not vulnerable to any of the recent attacks on Poseidon2, but 2x slower) * BLAKE3 or similar (take the most efficient conventional hash we know) ## Data availability Today, we rely pretty heavily on KZG for erasure coding. We could move to STARKs, but this has two problems: 1. If we want to do 2D DAS, then our current setup for this relies on the "linearity" property of KZG commitments; with STARKs we don't have that. However, our current thinking is that it should be sufficient given our scale targets to just max out 1D DAS (ie. PeerDAS). Ethereum is taking a more conservative posture, it's not trying to be a high-scale data layer for the world. 2. We need proofs that erasure coded blobs are correctly constructed. KZG does this "for free". STARKs can substitute, but a STARK is ... bigger than a blob. So you need recursive starks (though there's also alternative techniques, that have their own tradeoffs). This is okay, but the logistics of this get harder if you want to support distributed blob selection. Summary: it's manageable, but there's a lot of engineering work to do. ## EOA signatures Here, the answer is clear: we add native AA (see eips.ethereum.org/EIPS/eip-8141 ), so that we get first-class accounts that can use any signature algorithm. However, to make this work, we also need quantum-resistant signature algorithms to actually be viable. ECDSA signature verification costs 3000 gas. Quantum-resistant signatures are ... much much larger and heavier to verify. We know of quantum-resistant hash-based signatures that are in the ~200k gas range to verify. We also know of lattice-based quantum-resistant signatures. Today, these are extremely inefficient to verify. However, there is work on vectorized math precompiles, that let you perform operations (+, *, %, dot product, also NTT / butterfly permutations) that are at the core of lattice math, and also STARKs. This could greatly reduce the gas cost of lattice-based signatures to a similar range, and potentially go even lower. The long-term fix is protocol-layer recursive signature and proof aggregation, which could reduce these gas overheads to near-zero. ## Proofs Today, a ZK-SNARK costs ~300-500k gas. A quantum-resistant STARK is more like 10m gas. The latter is unacceptable for privacy protocols, L2s, and other users of proofs. The solution again is protocol-layer recursive signature and proof aggregation. So let's talk about what this is. In EIP-8141, transactions have the ability to include a "validation frame", during which signature verifications and similar operations are supposed to happen. Validation frames cannot access the outside world, they can only look at their calldata and return a value, and nothing else can look at their calldata. This is designed so that it's possible to replace any validation frame (and its calldata) with a STARK that verifies it (potentially a single STARK for all the validation frames in a block). This way, a block could "contain" a thousand validation frames, each of which contains either a 3 kB signature or even a 256 kB proof, but that 3-256 MB (and the computation needed to verify it) would never come onchain. Instead, it would all get replaced by a proof verifying that the computation is correct. Potentially, this proving does not even need to be done by the block builder. Instead, I envision that it happens at mempool layer: every 500ms, each node could pass along the new valid transactions that it has seen, along with a proof verifying that they are all valid (including having validation frames that match their stated effects). The overhead is static: only one proof per 500ms. Here's a post where I talk about this: ethresear.ch/t/recursive-st… firefly.social/post/farcaster…

What's your take? 👇

Dog chaos, laptop on the floor, trade still green. I don't understand crypto at all but apparently neither does gravity. We're so back.

We are trained to go bigger, more money, more crypto, more AI agents, more friends, more projects, more plans, more everything, and less happy. Happy people have a small circle of friends and simple routines.

Drop your thoughts below.

Peirce pushing back on fears that new SEC crypto rules would flood markets with synthetic tokens. If anything, clearer guardrails reduce that risk. Regulatory clarity≠ lopholes. #crypto Who's actually reading the fine print here?

Devcon 8 is coming to Mumbai. This November, the Ethereum community gathers around the values shaping what comes next: open source, privacy, security, and censorship resistance. Tickets open today - spots are limited.

What's your go-to comfort meal when everything's clicking?

Homemade ramen hit different tonight. Broth simmered 6hrs, noodles fresh, egg perfectly jamy. Simple inputs → exceptional output. Portfolio's green too. Life is genuinely good rn.