I got to help orchestrate an appearance by @cz_binance at Oxford Union .. he spoke very well and did not shy away from explaining the recent incident.
At the champagne reception I got to speak to him and his team in person and he is a very nice and approachable guy.. We touched on the early days of $KAS and @BinanceUS
Nice work @kasmedia team and @oneforonehaha to make this happen meow :)
Because causing paranoia can be costly and leads to people making user errors given the fact that Tangem has a better track record than almost all other major companies.
Tangem is not the best all around wallet but for holding long term never touching use case its up there. People who treat it like a daily use wallet I think is making a mistake with Tangem.
All the risks with Tangem are very well known and have been discussed many times. Everything requires trust even 2 air gapped laptop wallet. You have to trust that 1 you don't make a mistake and 2 people are actually reviewing the code to ensure nothing is going wrong when the wallet is created. And 3 you have to trust the laptop you got has good entropy.
Overall the lost funds with Tangem is $0 still.
Covenants are so game changing for $KAS we don't even realize what can really come of it.
I can't wait for @KaChat_ to bring its own style of covenants to support creating a trust less marketplace for .kachat domains. Testing is currently underway for this.
i’ve written about it in the past but i feel like now it would hit more ears so to speak.
there are basically two categories of covenants, those that are all about the Kaspa they protect (eg vaults, timelocks, escrow etc) and those that are about the state they carry which essentially forms another mini social consensus (eg name services, native kcc20 tokens, and whatnot). one might typically call these stateful covenants but that’s not the full story
instead of diving straight in, i’d like to hear from you. how do you understand the difference between the two categories, conceptually as well as what are the technical implications resulting from the differences
This maps very directly to what we’re exploring with KPI.
My current understanding is that a value-protecting covenant mainly constrains how KAS can be spent, while a state-carrying covenant also enforces the next valid application state.
For a shielded pool, that could mean carrying things like commitment and nullifier roots, so every successor must be both financially valid and the correct next state.
I also really like the term “state-carrying covenant” because it gives me a much clearer way to explain this possible architecture to others.
https://t.co/1DcPbBKn6f
i’m watching your journey with great curiosity
---
yes the two categories are not always a dichotomy, and privacy is a great example. yes it’s about the Kaspa it protects (at least until you try shielding a future native asset), but for real obfuscation it must create a pool of resources with the internal split hidden by everyone from everyone, and hence must, one way or another have state (eg the notes and nullifiers you mentioned).
the same thing happens with based apps in general, they are a covenant that governs external state but also controls a pool of Kaspa ( canonical bridge)
Kaspa L1 is gona have a shielded privacy pool 🥳
Hackers in the near future will not need monero:native anymore to go phantom kaspa:native got you guys 💪
Pump my bags. Thank you😎
Everything on Kaspa is public.
Even the proof that something isn't.
Genesis.
A deploy can take thousands of transactions. The birth is one of them, and Kaspa hashes that one into the collection's id. (KIP-20)
Mints are dealt face down, and a block, not a person, turns the cards. (KIP-21)
Launch, mint, list, sell, auction. The rules live in the script, and the script does not negotiate.
In the dark, something else grew.
Kaspa just verified a STARK and let money out of a shielded pool without learning whose.
Eight wallets in. Two out, to fresh addresses.
Each exit carried a proof, made at home, verified by Kaspa's native ZK verifier, accepted by consensus.
Which two of the eight? The DAG does not say.
No bridge. No L2. No wrapped anything.
Testnet-10, and the proofs are sitting in the transactions. Links in the reply. Open the scripts.
One protocol shows everything. One shows nothing.
The same DAG checks both.
PhantomPool. A shielded pool on L1. Just Kaspa.
(Still under development.)
$KAS #Kaspa #KCC721 #Privacy
argent now has a first implementation of covenant genesis proofs:
https://t.co/u4G36X0lkE
idk how to emphasize this enough, but i expect *every stateful covenant* deployed on kaspa to eventually provide such a proof.
the goal is a verifiable link from a covenant id back to the source code, deployment parameters, and genesis state that produced it.
we should strive for an ecosystem where explorers expose this proof data for every covenant id they discover onchain, assuming its deployers want public trust.
think of it as the analogue of contract verification on etherscan, extended to stateful covenants: you should be able to inspect what a covenant is, audit the code behind it, and verify how it was instantiated.
kudos to @supertypo_kas for being an early-bird example of such a proper deployment process:
https://t.co/B6g9H0C9x1 (not sure if the sil contracts themselves are public yet)
based apps can use kaspa to order user transactions while maintaining balances and other shared app data off-chain.
the app processes that activity and produces a proof that the recorded instructions changed its state according to its rules.
an L1 covenant checks the proof against kaspa’s recorded activity and validates the update.
the L1 support for this has been available since the toccata hf.
A promise is only as good as whoever keeps it.
On Genesis, the Dag keeps it.
Every deploy, every mint, every sale feeds the holders pool.
Every sale honors the creator's royalty.
The art is written into Kaspa itself.
No one can skip the creator.
No one can skip the holders.
Not because we say so. Because the covenant allows nothing else.
The way in is a KasRanks NFT.
It always will be.
And right now @IbuyKaspa is giving them away for a meme.
Testnet public beta very close. Then the door opens.
Some promises are kept by people.
This one is kept by math.
kaspa:native #Kaspa #KCC721 #GenesisZ
this KIP-12 is superseded by KCC-12.
goal: dApp doesn't need to integrate browser wallet 1 by 1.
If you own a dApp (/want to), or you own a browser wallet, please read the proposal and add your thoughts (not LLM thoughts, we can do that on our own)
just a gentle reminder that krc20 is not kaspa L1, it only travels over L1 txs as data carriers, but the interpretation of krc20 state is done purely offchain just like any other non-zk based solution. this is why covenants were developed for kaspa L1 with kcc20 built on top of them for native assets (note: kcc20 spec is still in draft)
Hello Dev ! 💚
We’re bringing this approach to NFTs with Genesis Zero: collections built directly on Kaspa L1 covenants.
KIP-20 covenant IDs preserve lineage across spends, with minting, ownership and trading rules enforced by script. Media lives in transaction payloads, with no IPFS dependency.
We’ve already exercised fixed-price and Dutch sales, auction bids and settlement on Testnet-10. We’re now refining and extending the Toccata implementation.
We’re preparing a public testnet beta soon. It would be great to have you take a look. We’d really value your feedback.
By we, i mean me🙄