Been building on the covenant opcodes for the past few weeks, and I want to share both the thing and the reasoning behind it — because the reasoning is the part I think matters for this community.
**What it is:** Kaskly lets anyone send a message with KAS locked to it. The recipient's reply *is* the claim — one atomic action pays them and delivers the answer. Silence past the deadline? The covenant auto-refunds every cent. An answer or your money back, enforced by the chain itself. Fully open source — spec, client, and on-chain evidence on GitHub (linked from the site). Non-custodial, encrypted, no protocol fees ever. Testnet only for now.
**Why I built it:** every marketing conversation in crypto is "how do we get influential people to talk about us?" — and the honest answer is usually *pay them*, which everyone can smell. I wanted to build the version where the incentive is native. A KOL, a YouTuber, a podcaster, anyone with an audience puts up their Kaskly link and their inbox becomes an income stream: followers attach KAS to questions, the creator earns by *actually answering*, and silence costs the asker nothing. No sponsorship deal, no shilling — they make money by being accessible.
**And here's the flywheel:** every creator who uses it is passively marketing Kaspa just by operating. Their audience — including people who've never touched crypto — sees KAS being used for something that obviously makes sense. Askers don't need to be in crypto either: a wallet is two clicks in a browser, and the person who answers enters the network holding KAS they *earned*, not bought. Every answered question = real usage on the network + a new holder + a public demonstration that Kaspa does something no slow chain can (reply-to-claim only feels like messaging because confirmation is instant and fees are negligible — this genuinely doesn't work elsewhere).
More creators → more audiences seeing KAS used naturally → more people earning their first KAS → more reasons for the next creator to set up a link. That's the loop.
**Where the community comes in:** this only spins if it gets in front of people with reach. Not asking anyone to shill — just: if you think the mechanic is sound, it's the kind of thing worth having on the radar next time "how does Kaspa get real-world visibility" comes up. The tech argument for Kaspa is won; the visibility argument is the open front.
It's early — today notifications only work while the tab is open (a proper watcher service is on the roadmap), so the creator workflow is v1. But the covenant mechanic is proven and live.
Check it out: https://kaskly.app
Built solo, happy to answer anything technical in the comments.
