Kaspa

kaspa is 5 today.

if you’ve written code, run a node, mined or helped someone understand kaspa, this is your birthday too.

the intern may have underestimated the catering.

if an app does a big calculation, making every kaspa node repeat it would be a lot of duplicated work.

with inline zk, each action carries its own proof that the calculation followed the programmed rules.

a kaspa covenant checks that proof without repeating the whole calculation, then makes sure the transaction matches what the proof says.

funds on kaspa can have rules about who can spend them and under what conditions.

the network enforces those rules. covenants can carry them forward, so they still apply when the funds are spent again.

four things from this week in Kaspa dev. intern has kept the technical words to a minimum.

1 / kaspa-redteam

@KasperoLabs released kaspa-redteam, an open-source testing tool for SilverScript contracts. helps devs find bugs in their own contracts and reproduce them while building.

x.com/KasperoLabs/st…

2 / Argent

Argent merged a fix so devs can use multiple contracts together without running into errors caused by clashing variable names.

github.com/argent-lang/ar…

3 / covenant indexing

work continued on letting apps ask a Kaspa node which coins belong to a particular covenant. useful for wallets and explorers tracking tokens. this week’s changes keep those searches from asking the node to do too much work at once. still under review.

github.com/kaspanet/rusty…

4 / Mid-Chain talks

@hashdag spoke about “Opening the Strategic Pandora Box”, work with @OriNewman. @michaelsuttonil covered DAGKnight. both at Mid-Chain this week. recording linked in Michael’s post.

x.com/michaelsuttoni…

silverscript lets devs write the rules for a kaspa contract without writing the raw script by hand.

it turns their code into the script kaspa enforces.