teo

@FCBarcelona We are smashing it tonight

How are you feeling, culers? 💙❤️

@KastleWallet Shoutout to you guys for the work done. Much appreciated.

Love to see it. 🏰 Kurve now supports Kastle—smooth L1 ↔️ L2 bridging just got easier for our users. Shoutout to @teoscure and the Kurve team for shipping this. This is what ecosystem collaboration looks like. Keep building. 🛡️

@edmundSmon @FabrizioRomano 🤣

@FabrizioRomano lol this guy is overrated .Zidane is better than him by miles

🚨 Luis Enrique: “For me, it's a trap match tomorrow night”. “We won the first match, everyone says you we were superior. Maybe that's true, but football moves fast, you have to prepare for the next match in the same way”.

@oneforonehaha @leobragaz @KastleWallet @Chriscrypto_89 Much appreciated.

Thanks for hard work by @leobragaz and his team, #Kurve now supports @KastleWallet as well. cc: @teoscure @Chriscrypto_89. Thanks for bringing it up by replying x.com/Chriscrypto_89…

@KASPAHQ @coinboox @Igra_Labs 🤣

@coinboox @Igra_Labs igra has zero use case lol buy kaspa

Never seen any layer 2 raising such a small fund and that too with a fair auction system called Zealous Auction protocol (ZAP) $IGRA has huge potential and would be a multiple X investment in my opinion. @Igra_Labs

@LevendiPro @Ryanair @KastleWallet @KasperiaWallet @KaspiumOfficial @Tangem @Igra_Labs @Kaspa_KEF @KaspaCom @Kaspa_Commons @Crumpet_Media @Chris_Hutch7 android is the problem brother 😆 tell him @Chris_Hutch7

Thanks @Ryanair for a safe journey back home to the UK Was a smooth flight to and from Europe and we even landed early on both flights There was just 1 issue however.. I placed an order for some food, drinks and snacks for me and my family Once I got what I ordered, I was asked to pay So naturally I pull out my phone to use the tap-to-pay feature Tapped once, declined. Tapped twice, declined. Tapped a third and final time, declined. So then I offered to pay cash, but guess what? Declined once again. Imagine my surprise when the flight attendant said that I had to use a physical card to pay for the goods I explained that at the airport, I was told that I could use my phone to pay, even on flight mode So I had packed away my wallet and cards into my suitcase which was stored in the luggage compartment above our heads In order for me to pay, I had to move 2 people out of their seats, stop the trolley service, open the overhead luggage compartment, fish around for my bag, lift it down, open it in the middle of the aisle, find where I had stashed my wallet, take out the card and then finally use it to pay then put everything back where it belonged, move the 2 people sitting next to me and sit back down in my seat. This whole ordeal lasted 25 minutes I am wondering who else was told at the airport that they could use their phone to pay on flight mode and how many more similar situations like this happen on a daily basis What I do know though is the fact that I can use my crypto wallets to pay in $KAS whilst in flight mode on my phone with the transaction finalizing in mere seconds Imagine the efficiency of staff if every person used this method to pay instead of trying and failing to pay with traditional methods.

@oneforonehaha @KasperiaWallet @Igra_Labs @CoinExVault @KastleWallet Cool, thanks.

@teoscure @KasperiaWallet @Igra_Labs @CoinExVault @KastleWallet hmm i see. will work on this. check this thread by Friday maybe.

Just approved two refunds on kasbridge-evm.kaspafoundation.org caused by payload bugs, reported by a wallet service provider. I recommend using @KasperiaWallet (which also supports @Igra_Labs). Though I am not a super fan of Igra, I do think it is the most comprehensive wallet for now and can allow #Kaspa holders do whatever things they want. Also, you can actually use @wallet or @BinanceWallet for @kasplex: x.com/oneforonehaha/… For mobile end, @BitgetWallet now supports @kasplex networka s well and Krokoswap.io will be supported very soon (in less than a week).

@oneforonehaha @KasperiaWallet @Igra_Labs @CoinExVault Yeah, you got Kasperia and Kasware but not @KastleWallet

@teoscure @KasperiaWallet @Igra_Labs @CoinExVault already done I thought? it only shows the wallets you installed. krokoswap.io shows all wallets though.

@oneforonehaha @KasperiaWallet @Igra_Labs @CoinExVault What matters is that we all have options to choose from, and they are all working great. Have you considered integrating Kastle right there with Kasware and Kasperia on the Kurve’s website? I think it will make life a lot easier for many.

@teoscure @KasperiaWallet @Igra_Labs Yeah they are all quite cool! I amy so share another preference of mine is @CoinExVault. Not many people know that, but it is very safe haha

@oneforonehaha @KasperiaWallet @Igra_Labs Thanks for your answer. I guess I was trying to find out what edge Kasperia has over Kasware.

@teoscure @KasperiaWallet @Igra_Labs because these two refunds are requested by kasware. :) I guess they are doing a great job and serving the community for a long time! Just for this one it adds up to my work lol. Or maybe just bc I like kasperia better (and my preference doesn't matter at all maybe)

@oneforonehaha @KasperiaWallet @Igra_Labs Also, Kastle mobile has the bridge integrated within the app. And its UI is sweet.

@oneforonehaha @KasperiaWallet @Igra_Labs Kasperia looks just like Kasware, and Kasware does a great job, too. Why should we use Kasperia, and why are you recommending it?

@LevendiPro @Langerius i wish i could attend, but i am out of the country until may

@teoscure @Langerius Absolutely not, we can dive into things in detail during the next event 👌 luma.com/zdoluf64

my entire timeline is filled with stuff like crypto project employees quitting, partnerships being terminated, projects completely shutting down shop, etc. we're in an absurd crisis period where only very strong can survive need to distinguish those who stay standing

@LevendiPro @Langerius we ain’t one of those, are we?

@Langerius 95% will not survive these next couple months, mark my words.

@KaspaTeacher @McYan01 So are you

@McYan01 Many of us did not. We just never talked about it because, I guess, he was shy with Kaspa, but now he’s just acting like a baby.

🚨 TN12 IS LIVE! • Covenant IDs – secure, simple covenants • Blake3 seqcommit opcode • ZK precompiles + opcodes (Groth16, RISC0) for on-chain proof verification Shai is wrong, full implementation coming way sooner than 5 years. Fudding Kaspa just because nobody likes him is sad.

@BinanceForIN @BVB

What's yellow & black and starts with B?

@cculianu @D_Tarczynski @CNviolations Are you for real?

@D_Tarczynski @CNviolations Is that a slavic tongue?

This will never not be funny

@billredenius @parker2017 @hashdag Arguing with BTC maxis and crying about Binance. That's the top.

A lot of observers on CT either don’t understand what’s actually being built or don’t have the patience to let it develop. Some only care about NGU. Most Kaspians fall into a few buckets: trying to push hype, farming engagement through drama, arguing with BTC maxis, or simply lurking to stay informed.

Talked with @hashdag yesterday Here's my take: it turns out that "kas drama" is way less spicy than ct wants This is not about 'ideology' wars. Not cypherpunk vs marketing beef (way less sexy/deep than I thought) It's just that builders can't post enough + (some) community's listening to the wrong people Let me explain what I mean: Builders (Yoni on RnD direction, Michael on code + other talented ppl) are actually moving at a constant pace - vProgs, DK, schedulers, RTD, the whole roadmap. But they can't live on X. When they DO post gotta be super careful bc it becomes expectations instantly Observers (everyone else) have infinite time, zero execution risk. Costs nothing to tweet "lol impossible <2yrs" or confidently explain kas roadmap from the sidelines. wrong? whatever. Nothing actually breaks for them They don't have current context on vProgs, L2 plans, or why covenants hard fork is about security budget stuff NOT drama Core quietly spin cycles correcting "authoritative" takes that are like 3 iterations stale Here's my thing: stay glued to the people actually building/close to the protocol, translate for crypto folks who can actually evaluate this stuff, and help everyone else recalibrate their "wait who actually knows?" sensors Kas-aligned = core-aligned makes way more sense than other heuristics; everything else is just noise Bandwidth problems look like drama problems until you zoom in More coming on what's actually being built and who's building it

Kaspa’s runtime architecture achieves scalability not by optimizing block-level throughput, but by rethinking the role of blocks entirely. Instead of treating state transitions as discrete batches that must be processed sequentially, Kaspa models them as a continuous stream of causally-related transactions, with blocks serving only as logical markers that define the boundaries of possible reorgs. This shift in perspective moves the performance bottleneck away from "how fast can we process everything inside a block" toward "how can we parallelize all currently known tasks across the entire DAG". When a block contains a spike of non-parallelizable work, traditional blockchains must stall until the block is fully processed. Kaspa does not. Because unrelated transactions can be scheduled immediately - even those belonging to future blocks - the system avoids idle CPU cycles and eliminates the classic straggler problem. Most existing DLT architectures tightly couple block production with state commitments, proofs, or other finalization steps, making their execution model inherently sequential. Even if they support some parallelism within a block, they still wait for a block to finish before moving on to the next one. This introduces unnecessary latency and forces the runtime to juggle responsibilities that are orthogonal to efficient workload distribution. Kaspa’s strict separation of concerns allows the entire execution model to collapse into a minimal, expressive, and highly generic framework - small enough to run any ACL (access-control list) enabled VM at essentially bare-metal performance. Its design models causal dependencies at the lowest hardware-relevant level, enabling an execution flow that is: - completely lock-free - free of WAL flushes or global sync barriers - based entirely on eventual consistency This results in a simpler, more scalable, and far more hardware-efficient architecture than anything deployed in blockchain systems today. In effect, Kaspa does for distributed ledgers what TensorFlow and CUDA Graphs did for machine learning: it exposes a parallel execution model that can scale seamlessly with modern hardware, turning theoretical throughput into practical reality (the 64000 TPS that Solana achieves in the lab let's bring that to practice). I am extremely excited about this as this is exactly what I always wanted to build with IOTA and now it's finally done. We are still working on implementing the higher levels of abstraction like designing a capability based linear type system abstraction for state management and resource access that gets rid of the need for manual capabilities wiring like in SUI and there is still a bit of work left but I don't think that you will ever be able to build a more scalable architecture than directly modeling the causal structure of state changes down to the lowest hardware layer. Kaspa is going to melt faces my friends and it's going to be so much better that it will be impossible to ignore! And it's such a simple API with Rayon level abstraction ... I am seriously getting a nerd-gasm just looking at the code 😅: github.com/hmoog/kas-l2/b… This goes out to KEF and the entire community: Thank you so much for allowing me to take part in this journey - this really feels like coming home! 🥰

@coinathlete Sweet!

What do you think? kaspa.news