back on weekly Kaspa dev roundup duty.
1 / vProgs
a batch of @Max143672’s work on vProgs landed this week. pending settlements can now resume after a prover restarts, and another fix helps settlement transactions go through when the network gets busy.
https://t.co/nvVCZz1gbV
https://t.co/ilwiqsdujS
2 / DAGKnight
@coderofstuff_’s update lets DAGKnight weigh all the blocks in a conflict together again, and @Max143672 proposed giving the runner-up a shot when the two sides are closely ranked.
https://t.co/DFfqZGJhbD
https://t.co/hmeVr1IUFm
3 / smaller transactions in Argent
Argent now lets devs leave unused contract templates out of a transaction. @freshair18 added that option while building a version of Pong on Kaspa, where even hitting the ball back used to send data for paying the winner.
https://t.co/xHOeXqMW9J
https://t.co/bE1CVJmQwv
4 / .kas names from @knsdomain
KNS is moving .kas names from inscriptions to covenants. existing names on testnet-10 have already moved, and you can register a new one there in a single transaction.
https://t.co/p6ABeXf8sc
5 / Kozmic Bridge
@KasperoLabs published the code for Kozmic Bridge and tested moving real USDC between Ethereum and Kaspa. they plan a few more rounds of testing before opening it to the public.
https://t.co/LJO6tyb6fE
Coming soon: Kozmic Bridge.
USDC between Ethereum and Kaspa L1, both ways, verified by zero-knowledge proofs alone. Kaspa checks a proof of Ethereum’s finality; Ethereum checks a proof of Kaspa’s work after your burn. Nothing in the middle holds a key.
Deposits land in about 25 minutes, exits in about an hour and a half. Small caps, real USDC, a few more rounds of testing before the door opens.
Will interview @michaelsuttonil on Tuesday at 8 PM CET / 2 PM EST
We were supposed to do this livestream more than a month ago, but conferences got in the way
He will talk about his research work at Kaspa, covenants, ZK stuff & more!
a few things you might’ve missed while the devs were busy this week.
1 / KOB
@crono_walker launched a testnet order book built with SilverScript and Argent. lets people place buy and sell orders for tokens, with Kaspa L1 contracts enforcing the trading rules. open to try on testnet-10.
https://t.co/2TQTFhPh8C
2 / home nodes
@OriNewman proposed a Rusty Kaspa update to help nodes behind home routers connect to each other without manually setting up port forwarding. still under review.
https://t.co/w0Q5l4AIXu
3 / prediction markets
@manyfest_ shared work with @maxibitcat on a permissionless prediction market built with Argent. predictions would be tradable tokens, with a voting system to settle outcomes. still in development.
https://t.co/4cfKmMz3Io
4 / HardKAS
@HardKASOfficial is building a practice environment for Kaspa app developers. it lets them send test payments and try out smart contracts on their own computer, using coins with no real value. the idea is to find bugs before real money is involved. still experimental.
https://t.co/xUhvwQxI5x
5 / notes for coding agents
@KasperoLabs published a free guide for AI agents building on Kaspa. covers wallets, payments, SilverScript and mistakes found while building real projects.
https://t.co/DpWK6iwCGk
Here's a library to help your AI agent build on Kaspa safely.
https://t.co/VYczp3NhY0
Best practices, code snippets tested on mainnet, lessons learned and failure modes, from building wallets, covenants, an indexer, token launchers, payment flows and a red team tool. It's written for coding agents to read before they write code, whichever one you use.
What's in it:
- Wallet safety: drainer patterns, signature modes, wrong-network and wrong-account traps
- Sending and signing KAS from code: the fee rule, storage mass, SDK calls that work
- SilverScript covenants: syntax, design principles, worked patterns
- KCC-20 tokens: identity by covenant ID, metadata, supply, lookalikes
- Token launchers: name rules, safe metadata and images
- Supporting Kasware, Kaspire, Kastle, hosted and phone wallets
- Accepting a KAS payment and checking it on chain
- Red-teaming a covenant before it holds money
- An error lookup: the node's message, its meaning and the fix
- A failures log, each entry with the rule it taught
It scales to the project. A tip jar and a hosted wallet need different things, and the first file helps your agent pick how strict to be.
To use it, tell your assistant:
"Read https://t.co/VYczp3NhY0, start with 00-agent-rules.md, then the files for what we're building."
Free and MIT. Corrections and additions welcome as issues or pull requests.
628,030 of 5,000,000 $KAS has been raised with over 800 donations. We are amazed by the strength of the community and hope that we can continue with the same spirit.
Every DeFi ecosystem on major chains has grown largely thanks to stablecoins. This is because DeFi primitives, like lending or trading, all need a token that has a stable value. We do not have this yet on Kaspa, and until then we are forced to rely on bridged stablecoins or those that originate from L2 networks, and these solutions do not inherit the properties of Kaspa that we so strongly vouch for.
KaspaDollar will be a pure token, controlled by nobody and priced by Kaspa’s miners, with no governance token to dump on you and no developer fee to extract from the community. But it can only be created if we come together as an ecosystem.
$KSD will be the first stablecoin on Kaspa, but it will not be the last. When centralized issuers see the benefit of Kaspa and decide to issue on it, they will find an ecosystem with a DeFi market, and KaspaDollar will be the primary point of contact for those efforts. What you fund now is the groundwork for every future stablecoin on Kaspa, decentralized and centralized alike.
if an app handles your money, “trust us” is doing a lot of work.
silverscript and argent help devs write rules for what the app can do with it. covenants let kaspa enforce those rules on L1.
covenants are also what connect inline zk and based apps back to kaspa. they check the proofs and enforce the resulting updates, even when the calculations happen elsewhere.
TLDR- A fully open, decentralized and permissionless prediction market application on Kaspa.
In the last few months I have been working with @maxibitcat mapping and coding his proposal for a permissionless prediction market into an Argent app.
He proposed a voting resolution mechanism that utilizes a lottery to incentivize the losing side of a binary market to vote honestly (see more in his original post).
It felt like a great use case for KCC20 tokens. A prediction is held as a tradable, fungible KCC20 token representing the prediction asset, with extended logic to support voting.
A few things worth sharing:
1. Argent is a fantastic tool that enables coding this complex covenant system with ease. This idea could also be written as a single EVM program, but when mapping it to the state machine it actually is, it feels natural and obvious to implement it as a UTXO covenant application (image attached).
2. It’s exciting to draft an application that is completely decentralized and open. Everyone would be able to create and participate in any market they wish, while also running their own application code
There will be no owner and no beneficiary. The system is completely open, would only benefit the network miners, and would encourage honest participation.
3. The system’s openness and current implementation tie the security of a market to its size. Small-cap markets could be manipulated more easily. Inevitably, people would lose money in this social experiment.
4. I aim to release a mainnet version around the end of this year.
a trading app on kaspa can have lots of people buying and selling against the same pool of funds. each trade changes the pool’s balances.
with based apps, users send instructions through kaspa, which records and orders them. the app processes those instructions off-chain, updating its shared balances and data.
a kaspa covenant checks a proof that the app followed its rules when processing those instructions. one proof can cover many actions together.
this week in Kaspa dev. the devs were busy. i took notes.
1 / covenant indexing
@Max143672's covenant indexing, covered last week, is now merged. @michaelsuttonil also added a new query for inspecting the transactions behind those coins. both are awaiting a node release.
https://t.co/rahZn2aKLs
https://t.co/Rn5YrzLvcW
2 / KaspaDollar
@KaspaDollar released a working whitepaper for its proposed KAS-backed stablecoin, with vaults and a price feed using miners' votes.
https://t.co/Iv43iBciiK
3 / Argent
Argent now lets devs add checks when connecting contracts. for example, making sure a new trading pool is set up for the correct token contract.
https://t.co/VATuL2QuVp
4 / security reporters
@IzioDev shared a community funding round to reward the security reporters whose findings helped harden Rusty Kaspa v2.1.0.
https://t.co/NTUzD4x77k
5 / kaspa-redteam
@KasperoLabs continued work on kaspa-redteam, adding tests based on real transactions and analysis of deployed contracts without the original source.
https://t.co/Oo6Ws1W4EW
a community funding wallet has been opened to reward security reporters who contributed in the software hardening, something that should be encouraged further.
here are all the details: https://t.co/x4PxskANfJ
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.
https://t.co/tbSVdL8HNr
2 / Argent
Argent merged a fix so devs can use multiple contracts together without running into errors caused by clashing variable names.
https://t.co/4rZiEeNQSo
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.
https://t.co/rahZn2biB0
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.
https://t.co/cWndQalkix
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.