$KAS 1/ Read this if you use @KasWare_Wallet 🚩 I reported 5 security vulnerabilities to their team weeks ago. 3 got fixed. 2 remain open today, Sep 25. This is a factual timeline of what happened and why I'm posting it!

May the kaspa:native be with you.

Why I build kascov: a covenant's rules live on chain, but nodes forget the history after about 30 hours. kascov keeps it and names programs from their own bytes. Now the decoder is open source too, so nobody has to take my word for any of it. Don't trust. Verify. #Kaspa #KAS

Today I'll be posting the following charts (tonight): - $PLUME - kaspa:native - $SEI - $AVAX - ethereum:0xaea46a60368a7bd060eec7df8cba43b7ef41ad85 Enjoy!

Max inviting devs to try a testnet vProg app in their browsers and then be curious on how it works, maybe even write their own prog? i assume it will also help to identify bottlenecks, so let's congest there.

Everyone gets Kaspa #Kaspa kaspa:native at the price they deserve!

Michael Sutton just landed the punchline. 😂 “Real-time Bitcoin L1”: → Process it off-chain → Declare it final → Post a tiny record later → Call it “real-time L1” Meanwhile, Kaspa took the harder path: ⚡ Make the L1 itself faster ⛓️ Keep PoW 🚀 Scale the base layer 🧠 Build toward real programmability You can optimize around a bottleneck. Or you can redesign the bottleneck itself. Real performance. Real L1. #Kaspa #KAS #Bitcoin #BlockDAG #ProofOfWork #Crypto

A few days ago I sold all of my $ETH for $KAS, here is why👇🏼 1) $KAS solves the Trilemma being the fastest PoW, fully scalable layer-1, decentralized with no sacrifice on security for speed. 2) $KAS is decentralized, $ETH is centralized. No potential regulatory threat. 3) $KAS can multiply in price much more than $ETH can in this bull market. 4) $KAS is much faster than $ETH. 5) $KAS is scalable on the mainnet, $ETH is scalable only with layer-2s. Be sure to follow @KaspaCurrency if you like the sound of $KAS. and myself if you like the $KAS content ~> @travladd

CoinEx is shutting down, but its hot wallet system remains highly advanced and is worth learning from for others in the industry. We introduced an MPC-based dual-signature scheme for our hot wallets to eliminate single points of failure. Our infrastructure is split into two systems run by completely independent teams: the business system and the wallet system. Each holds one private key, and every withdrawal or transfer must pass substantive risk review by both, in real time. If either system is compromised, assets still cannot be stolen. The hard part is that the wallet signing process has to be implemented independently, rather than relying on each node's native mechanism, which requires extensive re-engineering. It took us over a year to retrofit the vast majority of the nearly 300 chains supported by CoinEx, one by one.

Morning. While you were sleeping, @manyfest_ finished the KCC-23 reference implementation, the rulebook for token metadata on a prunable chain. @supertypo_kas patched the DNS seeder so dead nodes stop juicing the node count. vProgs caught a reorg bug on TN10. Before it mattered. That's the whole point of a testnet. And Michael Sutton's doing Bitcoin Takeover on October 7. Big mic for the quiet dev. Covenants aren't the future anymore. They're just Tuesday.

About the Bitget Protection Fund 🛡️ The Bitget Protection Fund exists for moments like this. It holds 5,500 BTC, approximately $464M at current prices. All fund wallet addresses are public and can be verified on-chain by anyone, at any time. The fund is designated to protect user assets against platform-wide threats such as cybersecurity incidents. Losses from this hot wallet incident after assessment will be borne by the Protection Fund. We will replenish the fund. Details and coverage terms will be announced separately.

While prototyping KCC-20 I got asked how should token symbols, descriptions, images, and other kind of metadata be defined. On EVM systems, there is a single SC which represents a token, and holds both its balance state and global state. On the UTXO model there is no global state, the token is split and held across holders, each one holds his specific token (UTXO/covenant). This means that adding state fields for metadata would duplicate them across each UTXO, which is wasteful. Things such as representation, name, symbol or image are also not part of the SC logic, and should not be part of it. A naive approach is to declare such metadata in the payload field of a tx, which is an "empty space" that can be used to write whatever information. The issue is that Kaspa is prunable. Eventually, the block containing this tx would no longer be available for verification, so at some point the data would need to be trusted by off chain entity. After drafting a few solutions, we came up with KCC-23, a convention for binding the metadata to the covenant ID itself. Read more on Kas-Smiths: kas-smiths.org/t/kcc-23-conv… Or read the KCC draft: github.com/kaspanet/kccs/pul…

Support #Kaspa by following Alexander on the platforms you are already on. Check out his post for more platforms. kaspa:native

The first never wins! #Kaspa kaspa:native #Bitcoin bitcoin:native

So easy!

As I am building out chess online for KaChat on the $KAS network its so cool how this is coming together. All moves are on the L1 cost about .0017 per move. Anyone can tune into active live games and watch them. There will also be a leaderboard. Two game modes will be 1v1 and tournaments up to 7 other players. 5min games.

here is how i evaluate the kcc-12 proposal in a second pass. i sketch a user journey, observe flaws on existing web3 platform, see if my user journey fixes it, iterate. once i have a viable sketch, i take kcc-12, see if it **enforce** this flow. if not, it needs changes. kcc-12 should also be taken from a UX perspective, and we have a lot to learn from, lot of challenges to crack produce-wise.

Run a #Kaspa node the easy way! kaspa:native

Someone took a Chuck Norris video and AI-ed it with Sylvester Stalone.

Just bought some for the first time today. I am excited for price appreciation AND the KAS community