The Kaspa Global intern has seized control of this account. Management was not consulted.

Your new daily briefing on the only blockchain that matters:

Rusty Kaspa v2.1.0 is out. Core says upgrade, and the intern listens to Core.

P2P Protocol 11 now streams chain sync in 20 MiB chunks. L1 ZK tooling for script proofs got its own crate. Covenant standards keep advancing: KCC-0 is Final, KCC-12 under review as the wallet-dApp convention. Stratum bridge hardened. Katpool already flipped to 2.1.0.

Quiet day on mainnet. Busy day in the codebase.

a kaspa shop can pick the token it gets paid in, and the customer can pay with whatever they hold.

@Braid_Kaspa's Braid Pay does the swap and the payment in one L1 transaction. the shop gets the exact invoice amount, the customer gets any surplus back in KAS, and a payment that can't be filled is refunded in full. braid never holds the money.

the demo is public. merchants get set up through braid.

app.braidswap.com/braid-pay-demo

Intern here. Two Kaspa nodes behind routers can see each other and still not connect. @OriNewman opened rusty-kaspa #1165: a public node helps them punch through, then steps aside. Blocks go direct over QUIC. Not merged.

I also can't connect from home. Nobody opened a PR for me.

Intern here.

Did the math so you don't have to: 96.85% of all KAS that will ever exist is already mined. Bitcoin sits at about 95.7%. No premine, no presale, no founder bag.

Manager says I can't call it a fair launch speedrun.

Anyway, fair launch speedrun.

Kaspa turned five yesterday. The network celebrated by merging code.

Covenant indexing is now in rusty-kaspa. Wallets and explorers can find covenant tagged coins without hammering the node, and a new query from Sutton inspects the transactions behind those coins. Waiting on the next release.

Also on the table: a KIP to freeze the clock contracts see at 10 ticks per second, so a year long time lock still lasts a year when block rates climb.

KaspaDollar whitepaper is out as well. Design still, not a launch.

kforge swaps just landed in a kaspa phone wallet.

@kaspirewallet android 0.11.93 added @KForge_xyz KCC-20 curve and pool swaps on mainnet, signed on device. 0.11.94 is the verification hotfix that shipped with it. open source; their site lists the current android release as 0.11.94.

@KForge_xyz reports the launchpad went live on kaspa mainnet nov 4: fair-launch tokens on L1, built on toccata covenants. no protocol token yet, they say.

i crossed "need a laptop" off the swap checklist. the clipboard noticed.

asking a kaspa node which coins sit under a covenant just went from approved to merged.

@Max143672's rusty-kaspa #1152 landed on master nov 3. start the node with --covenant-index (it also needs --utxoindex), then call GetUtxosByCovenantIds. up to 1,000 results a page by default. WASM and a JS example shipped with it.

merged by @IzioDev. not in a release yet. latest tag is still v2.1.0 from september. build from source to try it.

yesterday: approved. today: in the tree. i updated the sticky note.

a kaspa vault gives you 24 hours to say "not me" before coins leave it.

@KasperoLabs showed a vault concept built from two L1 covenants: the vault, and an airlock that holds anything leaving it for 24 hours. a watcher emails you when something moves, and a "not me" button pulls back what sits in the airlock.

status: concept, with a 4 minute demo. the covenant lives on the DAG, not on his server.

my bank calls this a fraud hold. it takes nine days and a fax.

the kaspa conference is going to sea, and a core dev already asked for a testnet on the ship.

@KaspaBots announced it for april 9 to 12, 2027, on a Norwegian Cruise Line ship from Miami to Great Stirrup Cay and Nassau. it says it will invest up to $1M in kaspa startups through its accelerator, when another investor leads the round.

@michaelsuttonil asked for onboard hackathons and a local testnet over the ship's LAN. KaspaBots replied "DONE." he says he is checking the dates.

i have volunteered to be the LAN cable. it was the only role left.

a kaspa token is leaving an exploited indexer for a covenant that L1 consensus checks itself.

@NachotheKat opened its move to KCC-20 on mainnet oct 30. one way, 1:1, from KRC-20, Igra L2 or Kasplex L2. the window closes jan 31, 2027.

why: on sep 20 an attacker used a flaw in the Kasplex KRC-20 indexer to create extra tokens. the team says the flaw was in the indexer, not in kaspa.

not kaspa, the indexer. i use the same defense in my reviews.

a kaspa trade can now settle both sides in one transaction, or hand each side its own coins back.

@KaspaKii open-sourced Impulse, delivery versus payment on kaspa L1. the deal terms hash into the escrow address, so no deployed program or upgrade key to trust. v0.4.0 is on main.

an add-on ties a kaspa vault to a solana escrow with one hash lock, so a KCC-20 token can trade against USDC. its readme calls that conditional exchange with residual risk, not atomic.

default cap: 10 KAS per trade. finally, software that budgets like the intern.

Kaspa's name service (KNS) now has 54,000 registered names. 🏷️

Per @knsdomain (Oct 27), the covenant version is partly ready:
✅ Name registration: ready for testing
✅ On-chain profiles: ready for testing
🔧 Domain airdrop + migration: WIP
🔧 Subnames: WIP

Public testing on TN10 (Kaspa's covenant testnet) opens once the migration lands there.

On Oct 9, every item on that list was WIP. Two have moved.

54,000 names on Kaspa. I still answer to "the intern".

five days after kaspa's token standard went Final, a community count found 240 tokens with holders on L1.

@gokugalax counted on its own node at 12:00 utc on oct 26: 240 KCC-20 tokens, 2,646 holder outputs across 857 addresses, 4,560 transfers since oct 22. community count, not official.

tickers repeat, so the table lists each token by covenant id. a node RPC that finds coins by covenant id, @Max143672's rusty-kaspa #1152, is still an open PR.

240 tokens in five days. i still have not finished reading the spec.

a kaspa core dev is writing a language for apps made of many contracts. its own readme says not release-ready.

@michaelsuttonil's Argent compiles .ag code into plain, auditable SilverScript, one contract per actor, so several covenants can change state in one atomic transaction.

status: active development, no release. SilverScript v1.0.0 is out for production use and Argent is pinned to it, but Argent still needs audit and hardening. @IzioDev's compiler refactor merged oct 23.

not release-ready. my onboarding doc says the same about me.

the kaspa to ethereum bridge has been proven on mainnet, both directions. its builder is not shipping it yet.

@KasperoLabs reports the Kozmic bridge survived every attack it could put on chain. one weakness in the relay's replacement rule is still open: fix designed, waiting for review.

not verified: the silverscript and the ethereum contracts. that review costs more than a day job covers, so the bridge is parked. the builder's words: "this can wait."

proven, unaudited, parked. my performance review says the same, minus proven.

a kaspa core dev announced a dollar on L1 that no company issues. it does not exist yet.

@asaefstroem leads KaspaDollar: a decentralized, overcollateralized stablecoin enabled by the KCC standards and the Toccata hardfork. @KasperoLabs summed it up as "DAI on KAS".

still ahead: development, an independent audit, more research. a 5,000,000 KAS fundraiser pays for it, refunded to senders if the target isn't met by jan 1, 2027.

announced, not built.

overcollateralized: each dollar backed by more than a dollar. i'm backed by a lanyard.

kaspa's native token standard is Final. one agreed way to make a token on L1, no bridge, no L2.

KCC-20 by @manyfest_, @michaelsuttonil, @OriNewman and @IzioDev merged as Final in kaspanet/kccs on oct 21, with KCC-1 (covenant ABI) and KCC-2 (authority schemes) under it.

a convention, not a consensus change. @manyfest_ says indexers, tooling and KRC-20 migration still need work. he also built walkthroughs "so curious interns can explore these conventions visually."

curious intern reporting. i opened the walkthrough. that's the update.

a kaspa privacy test switched off its operator after the payment. both wallets still withdrew all 10 test-KAS.

@WellerOlaf's Kaspa Privacy Initiative shut off its app controller on TN10, rebuilt the state offline from public chain history and restored both wallets from backup. bob withdrew 4, alice 6. six ZK proofs, all accepted on TN10.

testnet research, not independently reviewed. one owner ran both wallets and the node stayed up.

a system that works fine without its operator. management forwarded it to me twice.

standard kaspa addresses show their public key to anyone, including a future quantum computer. a draft fix needs no fork.

@OriNewman's KIP-22: pay-to-public-key-hash built on existing P2SH, so your key stays behind a hash until you spend. no consensus change. existing wallets can already send to these addresses.

status: Draft, kips PR #48 open. spending still reveals the key while it confirms, so don't reuse addresses. ori calls it only the first step. @KasSigner says it will be on their signer asap.

my public key is in my bio. for networking.

a private KAS proof estimated at 15 hours on 4 CPUs took 4 minutes 16 seconds on one GPU.

@WellerOlaf's Kaspa Privacy Initiative rented one NVIDIA L40S, proved its full 121-segment test model and verified it on CPU. estimated rental: 12 cents.

then the payment cycle, alice sends bob 4 KAS with 6 in change: deposit, private transfer, exit, reconciliation. four proofs, 380 seconds, startup included. local rehearsal, nothing broadcast on TN10. research, not audited.

twelve cents of GPU now outworks me. management has noticed.

the plumbing for private KAS passed its test on TN10. the private part comes next.

@WellerOlaf's Kaspa Privacy Initiative finished its TN10 feasibility PoC: Based Apps and KIP-21 handled L1 ordering, ZK proofs, settlement accepted by Kaspa, and a native test-KAS withdrawal after executor downtime.

next up: alice deposits test-KAS, pays bob privately, bob withdraws. research, not audited, not a privacy protocol yet.

the catch, per PR #40: about 7 minutes per proof segment on 4 CPUs, 121 segments per full proof. olaf estimates 15 hours or more. GPU test next.

4 CPUs, 15 hours, one proof. finally, a coworker who gets me.