Room Mining @RoomMining

@isabelle_zhou @OpenAI ⚡️

The Hugging bay, The Pirate bay for open LLM's, model weights downloadable with torrents. This is a game changer. huggingbay.xyz

@boardyai We offer blockchain mining and management services ⚡️

A dev got so frustrated watching his AI agent write 500 lines for a 5-line problem that he built a fix. He called it Ponytail. Named after the guy every team has - long ponytail, oval glasses, been there longer than the version control. You show him fifty lines; he looks at them, says nothing, and replaces them with one. Now your agent does the same. Before writing anything, it looks for a reason not to. 80-94% less code. 47-77% cheaper. 3-6x faster. The best code is the code you never wrote. GitHub Repo: github.com/DietrichGebert…

Instead of watching an hour of Netflix, watch this 30-minute speech by the Head of Anthropic’s Coding Agents research team. It will teach you more about vibe coding than 100 paid courses.

Viktor X'te tasarım tarafında takip ettiğim tartışmasız en iyi isimlerden biri. Adamın çıkardığı işler her seferinde estetikten yıkılıyor. Ve şimdi Claude Design + Opus 4.7 üzerine 18 dakikalık tutorial çıkarmış. Kendi adıma bu videoyu izledikten sonra tasarımlarınızın tamamen bambaşka bir seviyeye çıkacağına eminim. Claude Design zaten tek başına oyunu değiştiriyor, bir de Viktor gibi birinin elinden öğrenmek varken kaçırılmayacak bir kaynak. Yumulun!

Viktor Oddy @viktoroddy

3 months ago

Claude Design is insane. ❤️‍🔥Just recorded a 18-min tutorial on how to build animated, award-winning websites with Claude Design + Opus 4.7!

337 2K 26K 3.3M 52K

Here’s to the crazy ones.

@ethereum @zkPass 🔥

ZKPass is built on Ethereum. @zkPass is a privacy-preserving identity protocol letting users prove information about themselves without revealing the underlying data. It enables secure verification of credentials onchain while keeping personal information private by default.

Holy shit, this is INSANE. Andrej karpathy just open-sourced an autonomous AI researcher that runs 100 experiments while you sleep > He built a free AI agent that improves itself while you sleep > it runs fully autonomously, executing real experiments with no supervision > runs 100 experiments per night, one every 5 minutes on a fixed budget > edits its own training code, measures validation loss, keeps improvements and discards failures > results automatically adapt to your specific hardware > only one GPU is needed to run it > Best part is it’s completely free.

Andrej Karpathy @karpathy

4 months ago

I packaged up the "autoresearch" project into a new self-contained minimal repo if people would like to play over the weekend. It's basically nanochat LLM training core stripped down to a single-GPU, one file version of ~630 lines of code, then: - the human iterates on the

1K 4K 28K 11.1M 39K

Agents can now create email inboxes with USDC on @base AgentMail supports @CoinbaseDev’s x402 protocol to give agents access to email without accounts or API keys See how it works 👇

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…

💡

Nikil Viswanathan @nikil

5 months ago

[BREAKING] AI agents can now use crypto fully autonomously. Pay, trade, build apps. In 1 prompt. No human required.

146 134 933 158K 630

Autonomous agents are an entirely new category of users to build for, and, increasingly, to sell to. Today, we’re launching (a preview) of machine payments on @stripe—a way for developers to directly charge agents, with a few lines of code. 🤖💸 $ Let’s start tinkering… ⤵️

stripe launching machine payments on @base

Jeff Weinstein @jeff_weinstein

5 months ago

Autonomous agents are an entirely new category of users to build for, and, increasingly, to sell to. Today, we’re launching (a preview) of machine payments on @stripe—a way for developers to directly charge agents, with a few lines of code. 🤖💸 $ Let’s start tinkering… ⤵️

222 204 2K 670K 1K

@LineaBuild @ethereum

@ethereum @RoomMining

🚀roommining.io🚀

3/3 - Scaling RoomMining.io - ₿itcoin 10 years later! 🚀#bitcoin #BTC

1/3 - Scaling RoomMining.io - ₿itcoin 10 years later! 🚀#bitcoin #BTC