Ashton

ashton.kas on @kasiamessaging
on discord/tg I'm @argonmining
developing @kommsapp @enclavefi
volunteering at @kaspa_kat
$KAS $TAO $BTC
Don't Trust, Verify.

[Ashton @argonmining]

@KaspaDollar @asaefstroem @kccforum So cool! If @asaefstroem is involved I'm def interested.

[IzioDev @IzioDev]

Kas the coin can also be 'tokenized' as a kcc-20.

the need may not be very clear to everyone, but basically: my L1 app may want to uniformly manage kcc-20 and Kas the coin, without extra 'custom code'.

@manyfest_ details one of the direct use-case.

i have been convinced that designing kas-20 correctly only gives benefit with no tradeoff.

is it possible to have such an atomic covenant transaction that:
1. convert Kas to kas-20
2. trade it for the Many kcc-20 token

(=without adding one extra conversion step)

[Ashton @argonmining]

Because the path forward is migration - the KRC20 Vault were duplicative tokens. They backed L2 tokens when bridge routes where live. But L2 Tokens will migrate directly to KCC20, not to KRC first, so those Vault tokens were a potential source of further inflated supply if they somehow also got migrated. While thats unlikely to have ever happened, moving them to the official burn address makes it impossible.

[Ashton @argonmining]

@gimodeaz @ExTriage @NachotheKat @ScapeSquad @DrDanCrypto 🔥🔥🔥

[Ashton @argonmining]

Yes, I agree with @IzioDev. There are multiple methods/strategies to migrate and it depends on circumstances. For example, KRC20 tokens that have L2 ERC20 representations need a different solution that just snapshot. But a direct KRC20 -> KCC20 migration for a fully minted KRC20 makes a lot of sense to me.

[Hans Moog @hus_qy]

I like! This is a really simple and inexpensive way to significantly reduce the quantum threat to Kaspa users.

Traditional addresses expose the public key controlling the funds. A sufficiently powerful quantum computer could derive the private key from that public key and steal the funds.

KIP-22 proposes a simple change: instead of exposing the public key, an address commits to a cryptographic hash (a fingerprint) of the spending conditions. The public key stays hidden, and unlike elliptic-curve cryptography, strong cryptographic hashes remain highly resistant to quantum attacks.

Only when we spend the funds do we reveal the necessary information for the network to verify the transaction.

There is still a theoretical attack vector where an attacker could intercept a spending transaction, derive the private key, and attempt to front-run the original transaction. But since PoW relies on hashing, which is far more resistant to quantum attacks, the network should remain operational and continue confirming transactions, leaving an attacker with only a very narrow window to act.

Exploiting this would require not just a quantum computer capable of breaking public-key cryptography, but one powerful enough to do this faster than the network converges. On Kaspa, that means just a few seconds. That's a much stronger "theoretical adversary," and it's unclear whether such a machine will ever exist.

Personally, I doubt quantum computers will ever be able to break public-key cryptography at realistic key sizes (I suspect that Hilbert space itself is discrete and has a much coarser resolution than commonly assumed, but that's a different topic).

So TL;DR: KIP-22 isn't a "complete" post-quantum solution, but it's an elegant, relatively low-cost way to significantly reduce the attack surface for quantum adversaries.

[Ashton @argonmining]

Check out @UseArtisan 👇 I was lucky enough to get in as an early beta tester and it is amazing!

Visa Card, Bill Pay, 6%+ Yield, and Send Payments straight to Venmo, Paypal, CashApp, your Landlord, and even the Pool and Landscaping guys.

All from a self-custodial wallet! If you're in the US, you can now live your financial life sovereignly and onchain.

[mick.artisan.cash @IdMintThat]

My boss told me not to post this.

Roast him.

[Gerhard (Bitcoin Strategy) @BitcoinStrat]

🚀 Kaspa Miners Are Staying

Kaspa miners earn about a third less than three weeks ago, and they have not switched off. The hash rate sits at about 379 petahash. A mining machine pays off over many…

$KAS #kaspa #cryptomining

Try Premium for 7 days:
https://t.co/rHLpZX2v2y

[Olaf Weller @WellerOlaf]

Kaspa Privacy Initiative — Development Update

Following my conversation with @michaelsuttonil, we set out to test whether Kaspa's Based Apps and KIP-21 could provide the foundation for a shielded native KAS protocol.

The feasibility PoC on TN10 is now complete!

Across PRs #31–33, we've demonstrated:

✅ Real Kaspa L1 lane ordering
✅ Execution with cryptographic ZK proofs
✅ Proof-based settlement accepted by Kaspa
✅ Rejection of deliberately omitted operations
✅ State reconstruction and successful native KAS withdrawal after executor downtime

This is a significant step forward. Rather than building our own transaction-ordering infrastructure, we can potentially build on capabilities already available in Kaspa.

We've also added a new design principle in PR #34: future protocol upgrades should preserve users' access to their funds and aim to enable privacy-preserving migration between versions.

Now comes the part we've been working towards: actual financial privacy.

Our next milestone is a shielded payment cycle: Alice deposits native test-KAS, privately pays Bob, and Bob withdraws native test-KAS.

We'll begin by designing the private notes, commitments, nullifiers and ZK proof rules needed to make that possible.

The Based App PoC demonstrates technical feasibility within its tested scope. It is not yet a privacy protocol, an independently audited system or a final architecture decision.

But we're moving from proving the infrastructure to building the privacy layer itself.

All research remains open source. Technical feedback and contributions are welcome!

https://t.co/h4gdcS0FpP

[Kaspa Couple 𐤊 @KaspaCouple]

Let's get Ted to chart Kaspa, $KAS! 💚

Reply to his post with the ticker and let's get his attention for some free exposure! 👇
https://t.co/Gnhdijo7yW

[Kaspa Commons @Kaspa_Commons]

We’re excited to see this! Great work, @kaspagrowth

[Ashton @argonmining]

@wen_RH_69 @Kaspa_KAT @NachotheKat This is not exhaustive but its a good start - https://t.co/KRKKKmVjKc

[Ashton @argonmining]

Your NACHO will get to L1 for the very first time ever as KCC20 when migration tooling and standard is ready. This is the same for Igra/Kasplex L2 holders. Everyone is in the same boat and proportionally affected. We only have the attacker and the kasplex indexer to blame.

Nacho has a community call to discuss plan options tomorrow. Then a vote for community to approve whatever plan chosen. Community decides everything, please join the call in Discord if you can.

[Ashton @argonmining]

@brt2412 @bitrefill Nice. Pls post the outcome when you've decided. Data usage seems pretty accurate to me. If FT is audio only it shouldnt use much.

[Ashton @argonmining]

I feel similar, that was the motivation for the question. Going full data-only + OTT apps has been tempting for years. Doing it no kyc w/ crypto on prepaid like bitrefill makes it even better. Probably worth trying to live with for a few weeks and see what I miss. 911, kids schools, etc are the main concerns for me atm

[Ashton @argonmining]

@brt2412 Yeah but most of them are Wi-Fi only now. They used to have a pretty cool CBRS smallfi setup but they all went away. I made some good money operating those CBRS radios a few years back but its basically just an MVNO for tmobile with some wifi hotspots now