Will publish my interview with @hashdag when this post hits 500 likes
It’s edited and ready to go thanks to help from @web3creative_
If it doesn’t hit 500 likes by Sunday, I will just post it then 🫡
@agence_sparkana tout le monde me dit de mettre Tailscale, pour bloquer le port 22, j y comprends rien, j ai une clé ssh et ca marche tres bien, mais il parait qu en cas de faille, des bots pourrait entrer sur mon vps. Un avis la dessus ?
@thomasgrenoble@LysandreBL Ouvre ton entreprise et essaie de ne pas payer d'impôt, sans tricher, tu te fais violer en France.. C'est vraiment un discours hallucinant de dire que les entreprises ne payent pas d'impôt. Il suffit de tricher.. Ca devient impossible aujourd hui, tout est sous contrôle
@AureaLibe Il y a aussi @KaChat_ , une application iOS native de messagerie basée sur la blockchain Kaspa, conçue sans aucun serveur centralisé pour garantir des échanges chiffrés totalement autonomes, incensurables et impossibles à couper ou à contrôler par une autorité tierce.
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.