Ghost in the Knight

@Bitcoin_Teddy I get @hashdag and @adam3us being there but why Saylor?

Who would you add?

@Srodland Your first point is "Kas has no adoption" but qubic does all this stuff. That isn't adoption either. Your points are messed up and ill informed. It's not PoUW. But you are right, the price is lower than its high. But you should look at qbic chart 😬

🚨Kaspa holders need to face reality. The project is not delivering and the price action shows it. Anyone still holding $KAS should consider the following four facts and compare them directly to $QUBIC First, Kaspa has almost no real adoption. No major merchants accept it as payment. No large companies or countries use it for anything practical. It remains a speculative coin with hype but little everyday use. $QUBIC, by contrast, puts mining power to work training AI models. The network actually produces something valuable beyond moving tokens Second, Kaspa copied the idea of useful mining but delivered an inferior version. What they call PoUW is a stolen and watered-down copy of $QUBIC’s true UPoW. $QUBIC’s approach turns the computational work into genuine, useful output for AI and other tasks. Kaspa’s version does not. It is marketing dressed up as innovation Third, Kaspa’s network has become heavily centralized. A small group of large miners and early participants control most of the hash rate and supply. Over ninety percent of the total coins were emitted in the first two years, which looks more like a fast distribution to insiders than fair launch. $QUBIC runs on simple hardware anyone can use and spreads participation more evenly Fourth, Kaspa is losing ground fast. The price has dropped sharply from its highs while newer projects with actual utility move ahead. Warnings from analysts about it being overvalued and unsustainable have proven accurate so far. $QUBIC continues to show steady development, real computational output, and growing interest from people who want mining that serves a purpose Kaspa is not doing well. The momentum is gone and the fundamentals have not kept pace with the promises. The only rational move is to rotate out of $KAS before further losses. The place to go is $QUBIC. It offers the useful mining Kaspa pretends to have, along with a network built for actual work rather than endless speculation What is your concern with Kaspa? Drop a comment below 👇 #Crypto #PoW #altcoin $Btc

@CryptoWendyO Originally I thought it was ridiculous but that honestly makes sense. Should've said "it used to be 600% more expensive" but that isn't as bad as it first sounded. Or am I missing something?

Math is very hard.

@ProofOfPrints @realvijayk Way to go! When you ma something interesting it draws attention

kaspa:native community is awesome. Over 800 of you started following me in the last month. Have had several people reach out and just give words of encouragement and support. Progress is sometimes slow and bumpy but glad to feel like I have a team rooting for me.

@BitcoinRachy Doge as well...then the path...Led to Kaspa.

What was the first crypto coin that you ever bought? If it wasn’t Bitcoin, did it lead you there?

@pumpolinsky @ShellyonKaspa $Kas isn't made to hold for 10 years and sell it. Thats Bitcoin Think. It's made to be used. Security-instant transaction-stateless-and state of the art. Cypherpunk isn't dead, just moved on from BtC and into Kaspa

If I could give you a gift, would you rather have 268 $TAO or 2 million $KAS You can't sell for 10 years? And don’t just pick—explain why.

@BankQuote @CyberGent_ I can almost hear it kaspa:native

Toccata is beginning to look less like a routine hard fork and more like a constitutional moment for Kaspa’s execution model. The point is not simply that new features are arriving. The point is that Kaspa is trying to freeze the grammar of programmability before an entire proving stack hardens around the wrong assumptions. Most people will focus on the visible pieces. KIP 17 expands covenant expressiveness. KIP 16 gives Kaspa an onchain zk verification surface. Those matter. But the deeper move is KIP 21. That is where sequencing commitments stop being treated like a flat append only artifact and start being restructured around a more activity aware commitment model. That change is not cosmetic. It alters the scaling law. If proof systems are going to live above Kaspa without dragging the full historical mass of the DAG into every proving obligation, the sequencing layer has to be designed for that reality first. Otherwise you do not get based zk infrastructure. You get cryptographic ornamentation stapled onto a chain that was never architected to carry it cleanly. That is why the delay matters. Not because the fork is weak, but because the opposite is true. Kaspa appears to be refusing the usual L1 mistake of activating first and discovering later that the settlement grammar was incomplete. Better to freeze the sequencing architecture now than force compilers, circuits, and application designers to rebuild around a broken base six months later. So the real meaning of Toccata is not “Kaspa gets smart contracts.” That is shallow thinking. Toccata is Kaspa trying to open constrained programmability, proof anchored execution, and covenant level expressiveness without surrendering the base layer to VM bloat, sequencer dependency, or architectural confusion. It is not a pivot away from Kaspa’s design philosophy. It is that philosophy being extended upward with more discipline.

@ibuypow @maxibitcat This is so degen and not what I want Kaspa for...yet it kinda sounds like fun community shenanigans to show what it can do

@maxibitcat $KAS powerball drawings

$kas crowd, what do you want to build or see built as soon as covenants/based apps are live? I see a big hype around the new functionalities, but almost nothing about what you'd like to do with them.

@enesonchain Bitcoin Ethereum and Kaspa...but if programmability does well at the Toccato fork, just BTC and KAS

What I learned after being in crypto full time for the past 6 years is Almost nothing is truly Decentralized AAVE ? no because my funds are frozen right now Arbitrum ? glad they saved the funds but its not decentralized Drift ? haha even Hyperliquid ? we know its not It makes me wanna do dump all my alt coins, only buy bitcoin and ETH and log off

@CrypttoManiac_ Toccata is the better network 😉

Dime una red mejor que Kaspa.

@BitcoinTeacher_ @luke_coval @MDBitcoin I like bitcoin, I love Kaspa

@MDBitcoin I believe $Kaspa is the real true money and can incentivize miners. If Bitcoin reaches 1 million that’s only because $Kaspa reached even higher. Study $Kaspa.

Do you truly believe Bitcoin will reach $1M? If yes, why not buy more right now? If no, why not? What is your ceiling?

@BSCNews @ajkaspa @kaspaunchained This is relevant because big transaction numbers is how PoW crypto survives

KASPA L1 APPROACHES 2 BILLION TRANSACTIONS According to its official block explorer platform, the @kaspaunchained layer-1 network's cumulative transaction count is approaching the 2 billion mark. As of the latest data, it stands at around 1.95 billion transactions. The $KAS token itself has been buoyed by crypto's recent resurgence and is up +6.4% over the past week per CMC data.

@brt2412 @realvijayk @Tangem @OrangutanElder I was the other person. I just didn't know typing it into diff app would help

Hi @Tangem . I have already emailed support my ticket # is 141601 and I mentioned this yesterday and they said they would escalate it and get back to me. Since this issue has been resolved I don’t have any video to show but what happened was I accidentally deleted 2 cards (and I admit this was my own doing) and after that the app deleted my wallet off the phone. So with my remaining card I went to add the wallet back and it kept saying incorrect passcode. In reality the passcode I was entering the whole time was correct but there’s some keyboard bug idk how to explain it. But what fixed it was typing my passcode in another app, copying it then pasting it in the Tangem app and it suddenly worked and unlocked and I was able to move all my coins off that wallet and make fresh wallets. Regarding the incorrect passcode entry…I entered my passcode more than 110 times and that made the card NFC add an anti brute force timer delay of a max of 45 seconds in between each scan. On my personal 15 pro max the NFC scan would fail at around 6s remaining of a 45s delay and email support made me aware that newer models cannot support that NFC payload and to use something older than an iPhone 14. I was using an iPhone SE 2020 to enter the passcode 100+ times. I also tried a fresh Tangem app install on a 14 pro max, 15 pro max, and 16 pro max and all had the same issue with the passcode and NFC payload. The app was up to date in every scenario I tried it. So as I said finally yesterday I copy pasted the passcode from another app and it suddenly unlocked. I was using the SE. So that wallet is deleted and gone after the emotional trauma it caused me. However I have had multiple people confirm that this keyboard glitch has happened to them too. @OrangutanElder @KendallDynasty @bathtoob30 and one other person who I cannot remember off the top of my head Please let me know if this information is sufficient or not. As I said I was so emotionally distraught that I lost my entire net worth so I wasn’t recording videos of all of this. The only thing I recorded was the nfc payload failing on my phone but that’s not a bug it’s how the secure chip operates according to you guys.

@brt2412 What app did you use to type it?

@GhostntheKnight Please type your passcode in a separate app and copy it from there then paste into Tangem and see if that works and let me know. If it doesn’t try multiple apps anything where you can type words

Yes I have. I’ve tried a fresh install on 4 different iPhones and the video below happens in every scenario. I have pushed the anti brute force timer to its max of 45 seconds. So every passcode entry now requires 45 seconds. The problem is the newer model iPhones do not support a 45s NFC payload and will fail before the timer is up. Tangem support said to use something older than iPhone 14 so I’ve been using my dad’s SE. Even though the SE allows a full 45s NFC payload the passcode is still saying incorrect. I don’t know what else I can do.

@brt2412 @OrangutanElder 🔥 I'm pumped seeing this

I’m seriously shaking right now the $KAS community is unlike anything I’ve ever experienced. I am trying to like, follow back, and interact with everyone who commented on my posts but there’s so many of you guys so just know I’m not intentionally ignoring anyone. After I have some time to breathe I will be sending back every single $KAS I received in donations today, making a seed phrase wallet (as a semi experienced crypto guy I should’ve known this already lol 😭🤦🏻‍♂️) and upgrading my opsec. To @Tangem: this was 100% a bug in your app and I hope it gets fixed because I am beyond exhausted with the “Incorrect passcode” gaslighting screen I saw 500x over the last few days. The actual correct passcode was the one I entered the first 75 times before I started making a password tree generated by ChatGPT. So please do better and on top of fixing it please ACKNOWLEDGE the bug and I think you’ll retain most of your customers after this terrible roller coaster of an ordeal I’ve had. Gosh it’s such a good feeling man. We are so back 🚀🚀🚀

@diablos49 @brt2412 @CyberScrilla I chose seed option. This same Bug still got me. And tangem recommends not using seed phrase option. So they should own up for their part

@brt2412 Don’t blame Tangem! It’s your fault. You chose the seedless option. @CyberScrilla please look into this and make a video.

@brt2412 Wow. Im elated for you! But disappointed with @Tangem bc like I said this happened to me. Contacted support but no help. I was able to get my stuff off the account bc I had seed phrase. But I'm out on the cards I bought. And it was frustrating..and it's their bug