coderofstuff

@0xKnitser @IzioDev Weird, doesn’t seem like I can initiate it. There’s no message button

@coderofstuff_ @IzioDev Would love to use it, dm me

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

@0xKnitser @IzioDev @0xKnitser i have a tn10 datadir holding data from 7/13/2026 to present if you need it

@0xKnitser @IzioDev If you could get data for the last 72hrs are you able to recover?

@elldeeone When companies set up token usage quotas for people, this is the guy they have in mind as the standard

blew through 5b+ tokens in the last 48 hours.. hit the week limit.. have been running a task now for over an hour with zero tokens tho which is nice 😂 love how oai don't nuke the task the moment your tokens run out

@simogattok @BTCBreadMan @BitcoinIsaiah @KasGobbler btc doesn’t have utxo commitments which is why this same process as done in kas won’t work there.

@BTCBreadMan @BitcoinIsaiah @KasGobbler This is a fallacy that you guys need to correct, just to not seem dumb in scientific conversations. And btw you can ask your AI how it works in simple terms. x.com/coderofstuff_/…

When I post about $KAS I get a bunch of engagement from folks with arguments that would be compelling if I didn’t already understand what happens to shitcoins. When I post about BIP-110 I get less engagement, and even less compelling arguments. It’s frankly embarrassing.

There’s an internal devnet that’s been running since Feb also. Work is ongoing to: - implement incremental UMC (context: paper version is not efficient enough for mainnet, so an incremental version is necessary for production usage) - onboard devs from core to get more people up to speed on dk

@KASPAglobal @coderofstuff_ don't you wanna share anything, just in case

DAGKnight doesn't have a testnet. It doesn't have an activation date. It doesn't run any part of Kaspa mainnet today. What actually exists: a research-stage design for parameterless, adaptive block ordering, and a prototype branch with real commits, tie-breaking logic, conflict-zone handling, majority-coverage work. Research and a prototype are genuine progress. Mainnet still runs GHOSTDAG. Worth watching. Not worth repeating as if it's already live. $KAS

@IzioDev @keves_ko @Kaspa_Girl @hashdag @michaelsuttonil @OriNewman @Max143672 Definitely could use some izio et. al help on some dk bits, so I need to start doing some brain dump to bring you guys up to speed

@keves_ko @Kaspa_Girl @hashdag @michaelsuttonil @OriNewman @Max143672 perpetual dev on-boarding, improve devxp, some side features (multisig x pskt being one) and i heard that @coderofstuff_ may appreciate more attention to what he has been cooking (maybe just a rumor, let's ask him)

Congrats @hashdag , @michaelsuttonil, @IzioDev and Community to achieve the perfect milestone. May the KASPA and its Community keeps growing !

Toccata is Live! 🎉

@KasMaporg @michaelsuttonil @IzioDev @asaefstroem Very nice :) it’s great to see people who actually wrote the code be there to help spread the word about it

@michaelsuttonil @IzioDev @asaefstroem You can watch Izio live here in a few minutes. I wont tag him, to not put extra pressure on him.😏 x.com/KasMaporg/stat… ps. The workshops (July 1st and 2nd) will also be livestreamed, by both Imperial and our own team that will be on the ground.

#Kaspa $KAS at Imperial College London, with the table full of merch, 2 great looking banners, and 2 great guys!

@HeavyHashMedia @KaspaSilver I assume you’ve read the motivation for the change here #near-term-view-standard-min-fee-as-anti-spam" target="_blank" rel="nofollow noopener">gist.github.com/michaelsutton/…

I’m half joking. But Kaspa at bitcoins market cap puts the base fee at around 15-20 cents. At the market cap of gold, it’s around $2. And if we ever want to replace fiat, the base fee will be around $20-50. That stops Kaspa being peer to peer money and incentivises custodianship (debasement) Kaspa’s probabilistic txn selection model means that the fee market exists to determine speed of inclusion rather than whether you are included. I’d happily pay a very low fee for a coffee and have it take 6 seconds rather than 0.1. Anyone saying “yeah but it’s not a problem now and we can change it later”- Markets are forward looking, and we’ll never get to the market cap levels where it’s a problem if it prohibits the use cases which people are buying Kaspa for… Incredibly silly in my view not to let the natural fee market sort out block usage.

Btw this gives another use case and reason you should run your own node. I will not make the code work with public nodes. You gotta change it yourself or go local. :)

@IzioDev @codegirl007 Bugs in point in polygon math have led to some of most interesting glitches in speedrunning for early games. Degenerate triangles in Final Fantasy 7 comes to mind.

@codegirl007 This put me back 8 years ago, when I was developing a library for a game to check if a point is in a polygon. I found out about winding number algorithm, was super excited to implement, and then spent the next days finding out why it wasn't working properly ^^ Best moments

I just spend a long time debugging code thinking it was something super complex. But no, it was just a typo in a method I wrote to calculate distance. I'm a dummy.

Golang -> Rust transition is not just a rewrite in different language but a rewrite from first principles. We’re able to implement new, complex consensus changes because the foundation is optimized and allows for it. The old codebase just didn’t have that setup and a bunch of these HF work would’ve taken longer to implement or been impossible to do so.

@Kaspa_Commons Payloads came in via Crescendo, laying foundation for a lot of these

@cryptogenerian @ibuypow @lAmeR_1337 kasvault uses kaspa’s Public Node Network whose member nodes are updated to toccata node versions. Afaik ledger wallet uses api.kaspa.org whose backing nodes are also updated (@lAmeR_1337 correct me if I’m wrong)

@coderofstuff_ @ibuypow @lAmeR_1337 So if ledger fails to update their node my Ledger cannot transact on the proper network. Are the people at Ledger for sure aware and will be compliant with the fork? Or should I send my Kaspa to a KNG created address?

Has Ledger upgraded to the Kaspa Tocatta hard fork? At this point it would not surprise me if this falls between the cracks. Someone please let me know. I need to move my coins if not.

@ibuypow @cryptogenerian @lAmeR_1337 Yes. Or someone implement covenant support in the hardware (p2sh signing in general really)

@coderofstuff_ @cryptogenerian @lAmeR_1337 So the only way to use covenants after HF for the time being is with hot wallets that have implemented covenants?

Old nodes will be forked off from the new nodes and an “old network” will continue to exist until those old nodes shut off. Each side may continue producing blocks for as long as miners are on that side. They won’t just stop working, however they won’t be able to mine blocks over the updated nodes’ blocks. Each side of the fork will see the blocks of the other side as invalid.

@coderofstuff_ @ibuypow @lAmeR_1337 That’s really all I need. I assume old nodes will cease working at the hard fork block height?

@ibuypow @cryptogenerian @lAmeR_1337 Neither kasvault nor ledger wallet can support creating covenants at this time as that requires implementing the capability to sign p2sh related txs on the hardware wallet which current isn’t supported and isn’t on a roadmap. Send and receive should continue to work fine

@coderofstuff_ @cryptogenerian @lAmeR_1337 So if we use KasVault to create a covenant on our wallet, we won't be able to use Ledger Wallet to move our funds until they are compatible with covenants?

Say you have a p2pk address (aka. Your typical kas address that you sign with schnorr or ecdsa). Your address determines the locking script (how you may spend a utxo), and for regular addresses in kas (the ones that start with kaspa:q…) that locking script is sort of “sign the utxo with the private key of this address” form. So, if any utxo ends up in that address, you can ALWAYS spend it if you know the private key of that address. Covenant ids in utxos only matter if the locking script cares about them specifically (aka. through a p2sh address). Those addresses typically start with a kaspa:p… (but note that not all addresses that start with kaspa:p… suddenly cares about covenant ids). Fyi, this is an faq of recent exchanges we’ve dealt with for toccata. cc. @IzioDev

With Toccata, you will be able to add spending rules to $KAS coins. But what if someone sends you such a coin that you can’t use? Or its only working once for your wallet? @hashdag @michaelsuttonil @mikeneder @OriNewman

@AlterOR1GiN @mike_papadayo お疲れ様

@mike_papadayo 本当にありがとうございます☺️ そう言っていただけると、今後も動画を作っていくモチベーションも上がります☺️ それに、Tomuさんの頻繁な情報発信というのは素晴らしいものだと思っているので、能力がないとか、決してそんなことはないと思います😃 実際、私自身とても助けられています😄

正直、最初は難しすぎて理解できませんでした🤣 でもToccataの目的や追加された機能を知ると、Kaspaが目指している方向性がかなり見えてきます。 興味のある方はぜひチェックしてみてください👍 #Kaspa $KAS 🚀 👇 引用元YouTube いいね👍 チャンネル登録　よろしくお願いします☺️