
jellyfish f
115 posts



To me the bottleneck on this "legit defi usage" is the aggregate bizdev talent in kas ecosystem. I guess we'll be able to assess how we score on that once Tocatta launches with the necessary primitives and features. (And since we can't know for sure, and while others are making hopefully successful efforts to attract existing defi activity from other chains, I am attempting a parallel trajectory to bootstrap coordination markets on kaspa. Hopefully at least one of these efforts succeeds.)


THE @HansMokeNiemann STREAM FRIDAY. 5PM EST. LIVE.






I wrote a PoC token contract in Silverscript, currently called DOG20 (better name ideas are welcome). It supports token ownership by 3 kinds of entities: 1. Public keys — like any regular Kaspa address. 2. P2SH addresses — which means ownership by a stateless contract, e.g. multisig. 3. Covenant IDs — which means ownership by a stateful contract. The third option is the interesting one, and it's a demonstration of a broader concept (that might be familiar to whoever watched the webinar by @IzioDev and @michaelsuttonil), called inter-covenant-communication (ICC). In this context, it means you can put arbitrary stateful rules around token control. For example: - “after the first 10 spends, wait a year before spending again” - zk-rollups can manage their L1 tokens using a stateful bridge. DOG20 also supports minters that are allowed to mint indefinitely — but that does not mean the supply must be unbounded. Let's say you want to publish a token and allow to issue only 100 new tokens each month. DOG20 doesn't support it natively, but you can achieve that by making the only minting entity a covenant. That covenant will store in its state `nextIssuance`, and will allow spends of 100 tokens only if `time > nextIssuance`, and will set `nextIssuance = nextIssuance + 30 days` each time it's used. I hope to explain about it a bit more in the future, but in the meantime, feel free to look at the examples linked in the next comment.










