Ricardo Sanchez

@elldeeone @anbrandenburger I woulda guessed Claude.

@HocusLocusT @anbrandenburger yeah this is 100% codex made

Interesting website…👇 coordinationmarket.com

@tamy_mammi @16bit_kaspa Yeh, that’s an easy ask. It’ll just be “hidden” essentially,

@16bit_kaspa On the phone not dag

If I can delete messages on kachat, send pictures or GIFs, then I am deleting WhatsApp.

@EliBenSasson People will do anything but mention the cypherpunk king.

Real blockchain is for Free Financial Innovation. Corpochains will try thru regulation to bar that, and they’ll fail. Go Starknet, Near, Zcash, Ethereum, Bitcoin.

@muir_eth Having a great decentralized sequencer would rly help.

Robinhood made $10,000 in chain fees + rev share from its apps while returning $20 to Ethereum.

@CoinDesk @hashdag Has anyone here actually read this? I see no comments on this: > The first implementation of the thesis is Intendo Terminal, scheduled to launch its first version in July. Seems like a big deal.

Crypto gave individuals sovereignty. Staghunt is betting the next frontier is the group version: coordination markets. Read more at our latest thought leadership in partnership with @hashdag coindesk.com/sponsored-cont…

@p4bpj @KaspaKii @Igra_Labs @DiiDesertEnergy @pvson This is not criticism again @KaspaKii (well maybe a little for spreading hopium to retail). But rather a criticism of how retail view them.

@p4bpj @KaspaKii @Igra_Labs @DiiDesertEnergy I absolutely just think it’s ideas. @pvson has said before that there is no capital that KII brings itself.. They have the ability to connect to private market and companies though. People just need to understand that there’s a likely hood nothing will ever eventuate.

Kaspa PA depends now on Wallet #1 aka #EntityX, @KaspaKii and @Igra_Labs ?

@naval @michaelsuttonil This sums it all up, @michaelsuttonil The most rightful repost

Escape competition through authenticity.

@kloakprotocol @vessprotocol Oh kloak was a marketing psyop all along. Makes sense.

4/4 I eventually realized I was trying to fit a triangle into a square hole. the network that fulfills the satoshi ethos hadn't been built, like i thought it had in kaspa:native so i started building @vessprotocol a new network, PQ, private, scalable natively

@Justin_Bons Ok, so facts are just made up numbers?

Let's cut through the BS with hard & objective facts: 🧵 BTC= 7 TPS at 10min with 45 nodes ETH= 238 TPS at 12 sec with 7.5k nodes SOL= 40k+ TPS at 400ms with 717 nodes HYPE= 100k+ TPS at 200ms with 27 nodes ADA= 18 TPS at 20sec with 2.9k nodes ZEC= 26 TPS at 75sec with 20 nodes SUI= 100k+ TPS at 200ms with 128 nodes NEAR= 100k+ TPS at 600ms with 426 nodes ICP= 2k TPS at 480ms with 40 nodes KASPA= 400+ TPS at 2-7sec with 25 nodes ALGO= 10k+ TPS at 2.5sec with 1.5k nodes APT= 100k+ TPS at 200ms with 97 nodes These three metrics measure capacity, speed & decentralization! Whatever chain best combines all three wins! The facts speak for themselves. The devil hides in the details of how we measure these facts; that is where methodology is key: Node Methodology: When I say "nodes," I am specifically referring to native-delegated block producers, also known as validators. As only these nodes have real power within the system That means we do not count multiples of 32 ETH in Ethereum's case & in PoW-based networks, we only count block-producing nodes (pool nodes/mining nodes) over the last month Speed Methodology: In this case, we are specifically looking at the time until we can spend the tokens after the TX. This seems to be the most practical approach to bridge the gap between various designs This mostly corresponds with block time, but that is not always the case. Such as in Kaspa's case, where block time is extremely fast, but it does not become spendable for significantly longer TPS Methodology: When it comes to TPS, I am specifically referring to the maximum theoretical Transactions Per Second for basic 1-to-1 value transfers The ability to send 1-to-many TX's for the same cost is a common feature across all of these chains. So, counting it this way instead is clearer & fairer. Contrary to what some in the ADA community might claim, these figures are accurate Chains without advanced on-chain scaling techniques have hard limits that can be easily calculated, like in ETH (gas limit) & ADA (block size limit), respectively However, for chains with advanced scaling, there are other bottlenecks. We have taken this into account in these figures to the best of our ability. However, some of these bottlenecks are likely to remain unknown until real usage hits the network My Picks, Deal With It: Instead of strictly following market capitalization as I often do for such lists & following specific rules for inclusion. I just included whatever I wanted to... As I will be accused of being a paid shill no matter what I do at this point, while also facing extreme toxicity for telling everyone about these basic objective truths That is why I only included what I thought was interesting & happened to already have a passing knowledge of. These are all communities I have also interacted with before in the past, discussing these very metrics Some of you will still think it is a grand conspiracy against your obscure chain because the tech is just so good... The tribalism, cope & delusion have become so ridiculous for some Blockchain Trilemma Solved: You might notice there is very little correlation between the number of nodes & capacity/speed! That is because the blockchain trilemma has been effectively solved & the trade-offs in the design space are focusing more on other metrics now The economic & consensus design ends up having a far greater impact on node counts, for instance. While there is also a more complex relationship between usage/utility & participation/decentralization Conclusion: Actions speak louder than words. The facts cut through the tribalism, nonsensical narratives & lies. This is how we break out of our chains of delusion & embrace the truth. As the future of money & finance is here now Give your chain a shout in the comments by quoting the TPS, speed & validator figures as a reply. If they are something to be proud of, I will be happy to help promote it! We should all strive to increase these figures & praise those who push the boundaries of innovation. The goal is to maximize freedom (decentralization) for as many people as possible (scalability) As cryptocurrency is useless without scalability & pointless without decentralization! 🔥

@KaChat_ @KaspaSilver Which alias spec is KaChat on?

Version 1.1.3 on iOS is out NOW! Update now to fix that nasty crash bug. Happy chatting! $KAS apps.apple.com/us/app/kachat/…

@KaChat_ Is this using the same bcast @kasiamessaging standard?

KaChat 2.0 is coming! $KAS What will this bring? Broadcast rooms. The idea is you join a room that is named whatever you like lets say kaspa-price. If anyone else joins that same room you can chat with them. These rooms can technically hold up to an infinite amount of users of course hardware limits exist. The goal is to aim for 3 day persistence so that all messages exist for 3 days before they get wiped. It will also be optional if you want to be notified every time a message is sent in the room and if you want to keep 3 days of data. ( The exact days may change/be totally up to you to decide) Let me know what you think! This will be a great way for anyone with KaChat to quickly start chatting with other people without having to know someone else who has KaChat already.

@parker2017 @lunfardo314 This is also a great read from him: @lunfardo/utxo-chains-1-5-ed3c3b71522c" target="_blank" rel="nofollow noopener">medium.com/@lunfardo/utxo…

Makes sense. I see the distinction you’re making. I’m probably less precise with the wording, but you’re thinking at the design-layer level where that kind of precision is non-trivial I’m watching Proxima too. The transaction-based DAG idea is very cool to see in action, and if Kaspa brings more attention to these kinds of ledgers, I think Proxima could benefit from that Also, I respect your work. You’re one of the few adults in the room when it comes to serious technical discussion on X, lol

I'm on the edge of my seat for the next six months of Kaspa ecosystem development. I think the next 1-2 months are especially critical to see whether major advancements progress, more people show up, and real use cases start coming to the broader ecosystem. As I was recently telling a friend; bull or bear, I think the antifragility of Kaspa as a system will be tested over the next six months. I'm optimistically hopeful, but cautious about growth during a tumultuous time for broader crypto, and I think this presents a real opportunity for Kaspa to show a new era of sovereign, UTXO, PoW programmability. Toccata is the first major step, and I would argue that if Kaspa succeeds, it will be seen in hindsight as one of the most important steps in bringing more sovereignty and optionality to the masses. This is what I'm here for, and it could pave the way for other interesting solutions as well.

@auzghosty @kasiamessaging I did it at the start of the year. As a demo. Works but is n tx per user. Can be costly due to new 100x in fees.

Will someone build group chats for @kasiamessaging now?

@LevendiPro @BlockchainBants @IzioDev @asaefstroem @KasMaporg @kaspagrowth @Kaspa_KEF @iclblockchain Pair programming with @IzioDev is a 10/10 experience. I need photos of the ciggi break location.

Workshop talk just finished and we have some listeners that are really interested in building on $KAS 👀

@CryptoArchieYT I disagree. It means a lot short term: - (again) demonstrates the acumen, capability and thoroughness of core contributors - (again) demonstrates and role-models non-contentious hard fork and upgrade timeframes within a decentralized network

The Toccata upgrade for $KAS doesn’t mean anything short term. But long term this is very bullish. When overall sentiment to alts flips bullish people will see the potential.

@KaspaSilver @KaspiumOfficial @KaChat_ Worth noting @kasiamessaging is updated

Just an FYI $KAS @KaspiumOfficial on iPhone has not been updated. Therefore set fees to around .003 if you want your transactions to go through. ETA should be this week. @KaChat_ currently also needs an update so it will be down until that gets updated. No exact ETA yet.

@thsottiaux Token burn seems to be due to excessive reasoning. Simple tasks on 5.4 seem to be taking minutes longer than they ever have. Sometimes it seems like these teams don’t even use their tools.

Codex usage limits will be fully reset again in the next hour and we will credit one additional reset into your bank for your own usage over the next 24 hours. We investigated reports that Codex usage was being consumed faster than expected. There wasn't one central issue, but a few smaller problems compounded for some users. Here's what we found and changed: - Actual usage: Auto-review had become more proactive, another change was triggering more subagent work, and background suggestions could run twice or retry too frequently after failures. We reverted the changes and fixed suggestion scheduling, duplicate generation, and retry behavior. This should reduce unnecessary background token consumption while preserving the work users explicitly request. - Usage reporting: Auto-review was incorrectly appearing as GPT‑5.4 usage, and failed or rate-limited requests were still shown as turns. Auto-review now appears as its own category, and only successful requests count toward the turn graphs. Rate-limited requests were never charged, but they were being displayed incorrectly. - Immediate relief: We reset usage limits while rolling out the fixes, then shipped hotfixes across the CLI, desktop app, and usage backend. - What to expect: New usage data should be clearer and actual consumption should be lower. Historical charts may still show auto-review under GPT‑5.4 because older turn data was not relabeled. Features that intentionally perform more work; such as /goal, subagents, and higher reasoning levels will still naturally use more capacity. All fixes are now deployed, and we've added more detailed monitoring so we can detect background-usage regressions sooner. We'll continue watching the results closely. Thank you for building and doing all sorts of things with Codex.