Knitser

171 posts

Knitser banner
Knitser

Knitser

@0xKnitser

Multi-Disciplinary Technology Expert My Projects: https://t.co/4NP9rhbgSO - open-source

Thailand Katılım Aralık 2021
160 Takip Edilen263 Takipçiler
Knitser
Knitser@0xKnitser·
A memecoin launchpad running on Kaspa covenants, live on testnet-10, and every token page ships with a Verify on kascov button built in. Launch anywhere, verify from the chain itself. This is exactly the loop covenants were made for. @KaspaRocket is now on the kascov front page under built with covenants. kascov.io
KaspaRocket@KaspaRocket

🚀 Transparency is key. Every KaspaRocket contract has a unique covenant ID on Kaspa that can be inspected on Kascov 🔍 Huge thanks to @0xKnitser for building this amazing covenant explorer. Try it yourself on kasparocket.fun and check the demo video below 👇

English
0
6
27
783
Knitser
Knitser@0xKnitser·
Just shipped a fix, and it works today. Name and ticker in the genesis tx payload at launch, kascov reads them straight from the chain and badges them named on chain. Add image plus image_hash and the art gets pinned forever, that's what kascov will render. No API integration, the chain is the integration. This is a bridge until the standards track covers metadata (KCC-0020 doesn't yet): when a standard lands, kascov reads the standard and early payloads stay honored. Recipe: #token-name" target="_blank" rel="nofollow noopener">kascov.io/guide#token-na…
KaspaRocket@KaspaRocket

@Classicxbt @0xKnitser Once the KCC20 standard is finalized, I hope Explorer will be able to display token names directly from the contract. And a KaspaRocket × Kascov integration to share token metadata and images would be awesome. 😁

English
1
4
14
427
KaspaRocket
KaspaRocket@KaspaRocket·
@Classicxbt @0xKnitser Once the KCC20 standard is finalized, I hope Explorer will be able to display token names directly from the contract. And a KaspaRocket × Kascov integration to share token metadata and images would be awesome. 😁
English
1
1
7
623
KaspaRocket
KaspaRocket@KaspaRocket·
🚀 Transparency is key. Every KaspaRocket contract has a unique covenant ID on Kaspa that can be inspected on Kascov 🔍 Huge thanks to @0xKnitser for building this amazing covenant explorer. Try it yourself on kasparocket.fun and check the demo video below 👇
English
4
16
79
2.8K
Knitser
Knitser@0xKnitser·
testnet-10 post-mortem: a 49 hour sync freeze met Kaspa's 3 day pruning window. We rebuilt 60,789 events and 47,956 spends straight from the chain. The oldest slice was already pruned everywhere and is gone, being honest about that. Mainnet: untouched, complete since day one. The fix: kascov now runs its own archival node, self-alerts in minutes, and streams verified backups every 5 minutes. The explorer that remembers now has a memory the network can't take away. kascov.io
English
2
11
51
1.6K
Knitser
Knitser@0xKnitser·
@IzioDev Thanks for that that's why I was not able to recover what was lost 50+hrs
English
1
0
5
137
IzioDev
IzioDev@IzioDev·
@0xKnitser node retains at least ~30hrs of prunable consensus data, at 10bps, not three days
English
1
0
7
331
Knitser
Knitser@0xKnitser·
New on kascov: transaction preflight. Paste your tx as JSON and find out before you broadcast. Every input's compute budget checked against the classic script units trap (9,999 free units meets a 100,000 unit CheckSig), masses measured against the block limit, an honest fee estimate, and a real run through Kaspa's script engine. Nothing broadcast, nothing stored. Also new: every transaction has a permanent page now, the "built with covenants" showcase is open (first entry: the Covenant Game Kit by @w00c00), and the full changelog since day one ships as an RSS feed. Check before you send. kascov.io kaspa:native #Kaspa
English
1
8
30
943
Knitser
Knitser@0xKnitser·
Everything being recovered right as we speak btw 🧠
English
0
0
0
101
Knitser
Knitser@0xKnitser·
Implement a Node for testnet-10 $KAS so kascov.io has some safety nets against losing data. Also going to hosy everything on a $60 deticated windows server. More projects coming
English
2
5
43
1K
Knitser
Knitser@0xKnitser·
Point is to not have any data loss and it actually happened. We live and learn
English
0
0
0
69
Knitser
Knitser@0xKnitser·
@bridgemindai it's funny they're not thinking straight when they get pressured by the competition
English
1
0
2
64
🇵🇭 TapToTip — Zero Entropy Knowledge Unified 𐤊
Thank youu sir <3 #KASPA What the actual fuck. This is nuts
Knitser@0xKnitser

Every explorer shows you token balances. kascov proves them. The KCC20 accounting layer is live on kascov.io: ✅ 287 of 302 covenant tokens verified from the chain itself: supply conservation checked, every live cell cryptographically proven 🧾 full books per token: holders, mints, transfers, burns, reorg-exact 🚫 12 tokens we refused to verify, with the exact reason shown. Conservative by doctrine, never a false pass 🔬 an independent adversarial audit rebuilt every balance table from raw chain data: byte for byte match Plus a galaxy of glowing coins and a landing page that breathes. Verified from the chain. Not asserted. kascov.io

English
1
1
7
301
w00c00 𐤊
w00c00 𐤊@w00c00·
Kaspa Covenant Game Kit is now open source — an SDK for 1v1 games with player-funded Covenant escrow and on-chain settlement. Your game owns the rules. The SDK handles funding, wallet signatures, settlement and proofs. github.com/w00c00/kaspa-c… #Kaspa
w00c00 𐤊 tweet mediaw00c00 𐤊 tweet mediaw00c00 𐤊 tweet mediaw00c00 𐤊 tweet media
English
3
23
78
4K
Knitser
Knitser@0xKnitser·
This is what Toccata was for. A game SDK where the match escrow is a real covenant: player-funded, non-custodial, settled on chain. No server holding the pot. And you can check his work: the Escrow contract recompiles byte-identical from source against the on-chain program hash, verified on kascov. Go build games on Kaspa 🎮
w00c00 𐤊@w00c00

Kaspa Covenant Game Kit is now open source — an SDK for 1v1 games with player-funded Covenant escrow and on-chain settlement. Your game owns the rules. The SDK handles funding, wallet signatures, settlement and proofs. github.com/w00c00/kaspa-c… #Kaspa

English
2
20
75
1.8K
Knitser
Knitser@0xKnitser·
Every explorer shows you token balances. kascov proves them. The KCC20 accounting layer is live on kascov.io: ✅ 287 of 302 covenant tokens verified from the chain itself: supply conservation checked, every live cell cryptographically proven 🧾 full books per token: holders, mints, transfers, burns, reorg-exact 🚫 12 tokens we refused to verify, with the exact reason shown. Conservative by doctrine, never a false pass 🔬 an independent adversarial audit rebuilt every balance table from raw chain data: byte for byte match Plus a galaxy of glowing coins and a landing page that breathes. Verified from the chain. Not asserted. kascov.io
English
4
17
72
2.1K
Knitser
Knitser@0xKnitser·
The chain has names now. kascov update, the covenant explorer for Kaspa L1 just learned to read: 🏷️ 16,557 covenant runs decoded and named: genesis0, PURE, KCC20 🪙 the first open KCC20 token directory: 266 tokens, owner and amount decoded straight from chain state 🔎 search 216,822 smart coins by name, id or contract ⚙️ replay any real spend through Kaspa's actual script engine with one curl 📡 open API: cursor event feeds, signed webhooks, no key required 📖 new builders guide: deploy, spend, replay in 15 minutes Everything open source. Everything verified from the chain itself, not from an indexer's say-so. kascov.io
English
3
23
83
3.4K
Knitser retweetledi
Knitser
Knitser@0xKnitser·
a few minutes later I pulled the trigger again. same result: 0.5 TKAS to the recipient, the rest re-locked under the same rules. and then, one window later, the contract hit its own exit condition: less than one pledge left, so it paid out everything and retired itself. nobody managed this coin. it managed itself.
Knitser tweet media
Knitser@0xKnitser

coin #2 is the good part. a Mecenas: 2 TKAS in, pledge of 0.5 TKAS unlockable every ~minute. once it aged past its period, ANYONE could pull the trigger. no signature needed. kascov.io/#/testnet-10/c…

English
4
9
35
1.4K