KaspaRocket

is the first KCC20 Memecoin Launchpad on Kaspa !! Give-it a try 👾

[KaspaRocket @KaspaRocket]

🚀 https://t.co/iABFpQ3zk3 is now LIVE on Testnet-10! 🧪

It’s time to experiment before mainnet.

We’re inviting builders, testers, and the Kaspa community to explore the platform, break things, share feedback, and help us make it even better.

Start testing! 🚀

#Kaspa #kcc20

[KaspaRocket @KaspaRocket]

👨‍🍳 We’re cooking up another UX update for KaspaRocket��� 🚀

Before we ship it, we’d love to hear from you.

What’s one thing you’d like to see added or improved on https://t.co/k6S04hLruW?

Every piece of feedback helps us build a better launchpad 🎯

[KaspaRocket @KaspaRocket]

On the front end, we’ve already limited purchases during the bonding curve so they can’t go beyond the S1 threshold. However, you’re right that this is currently enforced at the UI level.

Adding a constraint directly in the covenant, something like preventing purchases once the reserve reaches S1 + X KAS while still in the bonding curve phase would make the invariant enforceable on-chain as well.

That’s actually a great suggestion. Thanks a lot for pointing it out! I Will implement this fix for the next release thank you so much

[KaspaRocket @KaspaRocket]

🚨 Kaspa devs, we have a challenge for you.

Try to break our covenant. 🔨

KaspaRocket is powered by a Silverscript covenant managing our Launch Protocol + AMM.

Audit it, test it, push it to its limits 👇
https://t.co/S23hYUIWXx

Find a weakness? Let us know. The ecosystem wins. 🚀

[KaspaRocket @KaspaRocket]

The way our contract is designed, the liquidity is managed through a single UTXO that contains both the KCC20 tokens and the KAS. This means the pool state is fully tied to that UTXO and cannot simply be drained or stolen.

Additionally, we enforce a constraint allowing only one KCC20 UTXO owned by the AMM contract per transaction. This prevents someone from creating a malicious transaction path to interact with or manipulate the original liquidity pool.

Of course, someone could still create another pool independently, but that pool would have its own state and liquidity, completely separate from the initial pool created by KaspaRocket.

[KaspaRocket @KaspaRocket]

Could you elaborate a bit more on the scenario you have in mind?

In our design, the switch from the bonding curve to the AMM can only happen once we reach a minimum amount of tokens sold during the bonding curve phase, defined by the S1 constant.

So I’m interested to understand which edge case you’re thinking about, and whether you mean the remaining token reserve on the AMM side after the transition or another potential issue.

[KaspaRocket @KaspaRocket]

@maxibitcat As for concurrency, that would actually be a good problem for us to have. 😄

It would mean there’s enough activity and enough users interacting with the protocol simultaneously to make it a real concern.

[KaspaRocket @KaspaRocket]

Thanks a lot for taking the time to review it! 🙏
Regarding external liquidity, When the contract transitions from the bonding curve to AMM mode, the pool will already hold 125,000 KAS. We believe that’s sufficient for the initial AMM, so we don’t think external liquidity is necessary in our current design. You can try it on testnet-10 👉 https://t.co/OUdQ1LmrsH

[Kaspik @Kaspik_KCC20]

@KaspaRocket Awesome update! ⚡ The faster bot and massive fee drop are massive wins for the ecosystem. Great job, team! 👑

[KaspaRocket @KaspaRocket]

@ibuypow @EbaratNeil The goal is definitely to encourage collaborative review and make the contract as battle-tested as possible before mainnet. 🚀

[KaspaRocket @KaspaRocket]

@CyberGent_ If you’re exploring projects building with Kaspa covenants, take a look at KaspaRocket. 🚀

We’re building a fully on-chain memecoin launchpad powered by Kaspa covenants & the KCC20 standard.

Live on Testnet-10 👇
https://t.co/k6S04hLruW

We’d love to hear your feedback! 🔥

[KaspaRocket @KaspaRocket]

@moxypixy15683 @amigocintra1 If you’re exploring projects building with Kaspa covenants, take a look at KaspaRocket. 🚀

We’re building a fully on-chain memecoin launchpad powered by Kaspa covenants & the KCC20 standard.

Live on Testnet-10 👇
https://t.co/k6S04hLruW

We’d love to hear your feedback! 🔥

[🇵🇭 TapToTip — Zero Entropy Knowledge Unified 𐤊 @mrZeku2000x]

ttt

[KaspaRocket @KaspaRocket]

@DailyKaspa Amazing to see what Toccata is unlocking for builders. 🚀

Take a look at what we’re building with KaspaRocket: a fully on-chain memecoin launchpad powered by Kaspa covenants & KCC20.

Live on Testnet-10 👇
https://t.co/k6S04hLruW

Your feedback would be greatly appreciated! 🔥

[KaspaRocket @KaspaRocket]

@icp_NB I’m not sure if a KRC20 → KCC20 bridge is currently being worked on. Maybe @kasplex has plans for something like this.

However, it would most likely require a centralized infrastructure, since KRC20 and KCC20 rely on different architectures and KRC20 state is not on chain

[KaspaRocket @KaspaRocket]

⚡ Powered by Kaspa.

Watch how fast you can deploy both a KCC20 token and its Launch Protocol + AMM contract in just a few clicks.

This is what Kaspa’s infrastructure makes possible. 🚀

Try it yourself 👉 https://t.co/k6S04hLruW

#Kaspa #KCC20

[KaspaRocket @KaspaRocket]

🚀 We've shipped another round of improvements!

✨ Smoother token deployment UX
🪙 Improved token page
⚡ Deployment bot: 30s → ~5s
💸 Swap fees: 3 KAS → 0.1 KAS
Full changelog on our Telegram 👇
https://t.co/B07uzcVPfr

[KaspaRocket @KaspaRocket]

That’s why the deployment happens in multiple on-chain steps ! it’s fully transparent and powered by Kaspa covenants. 🚀

[KaspaRocket @KaspaRocket]

Why not do everything in a single transaction? 👀

Because each transaction creates a unique covenant ID, and we need two different IDs: one for the token and one for the Launch Protocol + AMM.

The tricky part: you can’t know a covenant ID before the covenant is created.