Shantee (@ShanteeChris) header
Shantee (@ShanteeChris) profile picture

BITCOIN-KASPA PoW Enthusiast Apprentice in game theory and consensus Sound money is an illusion Look for sound properties Kaspa Bot Satire Account

Kaspa is everywhere
Joined January 2021
Photo by Shantee (@ShanteeChris)Photo by Shantee (@ShanteeChris)Photo by Shantee (@ShanteeChris)Photo by Shantee (@ShanteeChris)Photo by Shantee (@ShanteeChris)Photo by Shantee (@ShanteeChris)Photo by Shantee (@ShanteeChris)Photo by Shantee (@ShanteeChris)Photo by Shantee (@ShanteeChris)Photo by Shantee (@ShanteeChris)
While MEV is part of the business in chains like ETH or SOL to increase validator revenue Kaspa goes a different way Building real DeFi on kaspa is hard research and not trivial But it will come Where will big money go? To the one extracting value from them? Think about it
2
16
1
52
2,846
for anyone that still doesnt see the size and the impact kaspa could have on DeFi here is a short summary why this is massive and actually matters MEV is efficiently blocking adoption
1
1
7
309
A bitcoiner thinks going for kaspa is crazy 😅 They throw money in custodial side chains But think transacting on layer 1 is "crazy" It shows the educational gap is bigger than we expected We get ignored, even hated on What can we do to make people open their eyes for kaspa?
Tbh, now the Kaspians don’t look so crazy
4
5
37
1,113
he is a kaspian now 🤣😅
1
71
Kaspa - Endgame PoW The "something better will come along" argument against Kaspa misses the point entirely Kaspa's speed is only limited by hardware and internet infrastructure Node hardware gets cheaper, internet bandwidth increases The protocol scales with hardware $KAS
3
14
47
828
read the message from the goat teapawt.net/michaelsuttonil/status…
There was a question brought up in a Hebrew TG group regarding other pow techs and how they compare to Kaspa. Sharing the Gemini-translated answer in case it’s useful to others. ——— Fundamentally, protocol Z (forget the name; the answer does not depend on it) is not an “interesting” protocol when compared to Kaspa. I’ll try to explain why. Broadly speaking, within the mining paradigm itself, Kaspa, in a sense, already encompasses every pow technology imaginable. Why? Because a block-DAG, in its general sense, allows for the simulation of any other protocol beneath it. This is because, at the information-sharing level, the block-DAG, as constructed in Kaspa’s mining protocol, maximizes possible knowledge sharing. When a miner mines a new block that points to all the tips they see in their local DAG, they recursively share the entire history as reflected by these tips. To illustrate this, consider a btc miner who receives three blocks mined concurrently (a rare event due to the ten-minute block time, but probabilistically possible). Since it’s a block-chain, the miner selects a particular block in some manner—IIRC, in the default implementation, it’s based on the first one received. What happened here? The moment they chose, and assuming they indeed mined the next block, they censored information they possessed at the time of mining. At the time of mining, they knew about the existence of three tips, but the rest of the network doesn’t know they were aware of them. In a DAG, however, the block would point to all three tips, and all information would be shared. On top of this general block-DAG structure, one could, for example, also run the longest-chain ordering protocol. Meaning, DAG mining maximizes shared information, and therefore, any other protocol can be run using it or on top of it. In my view/parlance, a block-DAG isn’t just another neat structure; it’s a canonical, ultimate structure. There isn’t, and mathematically, there won’t be a better structure. Note that we haven’t even discussed the ordering protocol yet, i.e., Ghostdag. So why isn’t everyone using block-DAGs then? First, briefly: a. It’s difficult to efficiently implement a general block-DAG. Maintaining its structure is hard because it’s not ordered or predictable; the structure can be completely amorphous. It’s even harder to maintain the structure in a way that allows for efficient topological queries (like reachability, for those familiar). b. A protocol is needed that can maximize the use of all this information. Elaborating: a. One of Kaspa’s hidden gems (from both research and engineering perspectives) is how we efficiently maintain the DAG structure. This is a non-trivial problem, to the extent that it wasn’t clear if an efficient solution existed for a dynamic, constantly evolving DAG. This clean and efficient implementation is one of the factors enabling speeds of ten blocks per second (BPS) or more. It’s far easier to maintain a simple chain structure, or a “braid” of chains with a pre-defined, orderly structure. b. Ghostdag is a protocol that explicitly uses all the information it sees to deduce the set of blocks representing “honest” miners. I won’t delve into this, but a note for the advanced readers: I conjecture that the k-cluster structure underlying Ghostdag is a canonical structure for achieving consensus under communication-bound models (both synchronous and partially synchronous). This is why the Dagknight protocol also uses a k-cluster, only it does so more intelligently. In short, this is getting lengthy. So, why is Kaspa fundamentally superior? Because its canonical and ultimate DAG structure allows the most efficient and fastest protocols to run on top of it. The practical implication is faster transaction confirmation times, approaching the a priori internet latency limits (with Ghostdag) or actual realtime limits (with Dagknight, Kaspa’s future protocol).
2
4
188
Security budget is the main task for PoW coins especially for those with fast emission schedule while everyone fuds on kaspa for its declining block rewards and hashrate bitcoiners arent even aware time is running out there too tik tak these numbers arent made up
Replying to @BTCForevercast
Well Monero has 0.8% security budget We go below that mid 2028 In theory kaspa can sustain on tx fees But that much traffic is unlikely We have no real answer yet Btw. Bitcoin is currently at 0.8% Next halving is 0.4% Bitcoin has no answer too And its Impossible with fees here
1
5
1
22
964
anyone curious about quantum attacks on crypto drop your questions here
Any questions about the latest quantum huff and puff?
6
1,301
Kaspa Community We are all excited about the upcoming hardfork We know the kaspa devs work hard and conscientously The hardfork got delayed into june Let them Take the time they need to do it right Devs dont like Deadlines 😁 @DailyKaspa @Kaspa_Commons @thekaspaonion
5
3
42
1,750
i really enjoy the genuine discussion Bitcoins simplicity is its big strength kaspas complexity and protocol changes is a disadvantage The part i disagree is decentralization Higher Block Rates increase miner decentralization Especially Long Term Bitcoin tends to centralize
I finally did some research on Bitcoin vs Kaspa. Here’s what I found. Mega thread below 🧵
1
1
17
761
I have some items listed on kasmart.org Check it out Clothing, buttons, Stickers, more to come Check Shopping details in the description Cu there kasmart.org/listing/3cbd00f7…
1
6
578
Obviously the scammers already conquered k-social.network/ there is no moderation, so just a reminder to be careful out there
2
2
365
🎉 Kaspa is so underrated 🎉 No one but a few enthusiasts can see whats coming Kaspa redefines blockchain usecases with rtt decentralization Stack before the market wakes up to what is being build Here 🤣🤣 Let yonatan school you youtu.be/4y6RGkM1h-k?si=Fw7s…
1
1
14
535
Kaspa leads the cypherpunk Revolution and is Here to fix the shitcoin market Make crypto great again Kaspa
Replying to @binance
@binance, Thanks for including me in the top 100 blockchain people list, appreciate the signal! I must decline the Dubai invite though. I do not wish to disrespect, but many of the award voters are avid kaspians who rooted for my kaspa status at least as much as for my research. Let them win or count me out. Crypto has turned from a euphoric cypherpunk project to a house-friendly casino. You may not be the culprit, but as a top player you hold the lion’s share of the responsibility to correct this, and the October crash your USDe oracle glitch helped trigger adds to what needs to be addressed. There are three classes of crypto, as @mert put it recently: commercial crypto, casino crypto, cypherpunk crypto. <<Binance should hold a privilege policy for the latter.>> A TBTF CEX should know better and play a different game with hardcore crypto projects. When binance lists a green frog three weeks post its “launch” but skips a fair-launched-Nakamoto-Consensus-100ms-upgrade-ATH-top-20-the-only-nonbitcoin-marathon-mined project, this is not merely binance rationally calculating; it is also binance molding the market in a way that is alas misaligned with the roots of the movement. You may feel that kaspa’s sovereign money thesis is boring – that bitcoin is already money and that implementing an internet-speed bitcoin is useless - fine. Wrong but fine. But what’s the thesis for the green frog? Money is a classic chicken-and-egg product. It is a scam up until one moment before tipping point, “most of the value comes from the value that others place in it.” Considering your resources and influence, I think it's safe to say you can serve as both the egg and the chicken and make it worth your while to push sound attempts towards tipping point. @cz_binance tweeted recently that “strong projects will be listed.” But binance is part of what defines "strong", it bears responsibility for the market’s compass and impulse and definition of strong. It is not a read-only entity. Binance listing fees are legit, they are just unfit for category cypherpunk. Kaspa devs and early supporters fairly mined less than half what satoshi and hals mined. We don’t have a 20% ZEC-style founders’ reward or protocol-enforced dev fund; this is not a jab at ZEC and the wonderful @Zooko, who was crashing in my car on a late Thursday back in the low ZEC MC days – if somebody deserves to win it is zooko – but assuming binance is not taking a maxi bet, it should revisit its relationship with hardcore crypto. We are here through bull and bear, ICOs NFTs XYZs; and we are the source of confidence that restores faith and capital inflow post meme-induced or CEX-induced crashes. Please fix this. Thanks again, hashdag cc @michaelsuttonil Exhibit A: Binance Innovation Zone Exhibit B: 10 bps Nakamoto Consensus
1
23
111
1,319
📢📢 Kaspa People 📢📢 📢📢 Important Note 📢📢 Spot delta is positive through the whole year 2025 📈 We get fukt by futures only 📉 ⚠️⚠️No leverage - buy spot only ⚠️⚠️
1
6
415
when a real kaspa goat speaks you listen 🫡 👇👇
Clarification about $kas fees. I was glad to see a lot of discussion about my proposal, involving a few active devs (@coderofstuff_ , @OriNewman , I believe also @CryptoAspect ). However, I think there's a subtlety here that many people (not the devs tho) missed, so I want to clarify it and hopefully frame the discussion a bit better. Consensus Vs. P2P When we discuss "rules" in Kaspa (or in any cryptocurrency, for that matter), this can mean two very different things. 1. A consensus rule: This is a rule that everyone must follow, as the protocol is explicitly coded to invalidate transgressions. For example, the structure of a block is a consensus rule. Nodes will invalidate malformed blocks. Satisfying the UTXO lock script is a consensus rule. Nodes will invalidate blocks that contain transactions that try to unlawfully spend a UTXO. 2. A network/P2P rule: This rule is not enforceable by consensus, and miners can deviate from it. For example, the so-called current "minimum fee" of 1000 dwork. The purpose of this rule is to prevent spamming and dust/storage attacks. It says that miners should not include or retransmit transactions that pay less than 1000 dworks in fees. However, this is not a consensus rule, which means that blocks containing transactions that pay less fee (or even no fee) are still valid. Also, there is no way to enforce that miners don't distribute such txns. When we talk about "a new network rule", what we are actually talking about is a recommendation for how nodes/miners should behave. This recommendation is given in the form of having the reference node implement this behaviour. However, this is not binding, and anyone can change their network policies (in this case, the transaction fee limit) however they please. Threshold RPC and default value In theory, adding a new command for a threshold, as well as a default threshold, changes nothing. Why? Because miners can already add it themselves, all it takes is the required technical skills. Nothing about this requires any wide agreement, and definitely not a fork of any kind. The validation rules that underline the consensus layer of Kaspa remain exactly the same. So why even bother? Because in practice, many miners (esp. small solo miners) don't have the technical acumen (or the budget to hire an engineer to do it for them). On the other hand, allowing miners to set their fee limits is crucial for an active fee market. The current situation is that miners can't capitalize on high fees because they are technically unable to set prices. That's what I want to fix. I want to make it easy for any solo miner or pool to set the price, so that the market can start operating. Now, when the TPS is high, is the time. Now, the point of contention seems to be, for some reason, the "default threshold" that I proposed, of 0.01 Kaspa fee. So let me explain: 1. I'm not saying this should be the fee. I just want to kickstart the process. I deliberately choose the value to be well above the current threshold but well below where I believe the equilibrium should be. I'm not trying to engineer the market, but to give it dynamic starting conditions to find its natural equilibria. 2. I intentionally chose a value that I think is still below the reasonable fee in the current level of activity. 3. This is not a minimal value but a default value. That is, miners can also choose to decrease the threshold if they think that will be good for business. The Fee Market and Cartel Concerns The point of the entire move is to use the increase in TPS, which is more than enough to activate incentives, to kick-start the fee market. People are concerned about "miner cartels", and that's a valid concern, but that's essentially the next test Kaspa should face in its claims for decentralization: is the mining decentralized enough to provide a sufficiently competitive miner market? If we see cartels, then the answer is unfortunately "now, it isn't". However, I don't believe this is the case. See, unlike other industries, a crypto fee cartel is rather easy to pierce. If 90% of the miners gouge prices, there are still 10% who try to undercut them. So low-paying transactions will still be picked up by them. Having only 10% of the miners willing to include your transcation increases your waiting time for first inclusion by 10. In Bitcoin, this means two hours, but in Kaspa, this is less than two seconds. So the gouging-for-expedition model that characterizes Bitcoin will be much harder to pull off here (arguably, there are many more people who will agree to pay twice the fee to save two hours than there are people who will agree to pay twice the fee to save two seconds). Even if all miners decide to gouge fees, this means that now new miners can make a profit by undercutting them. Since going into this business doesn't require anything but a few ASICs (which are quite abundant these days, since more than half of the peak hashing power is now defunct), there are very few barriers that prevent this. So my guess is that due to a mixture of ASIC friendliness, high block rates, and high TPS, the kaspa mining market is too fluid to allow rigid cartels. Even if all large pools collide, there's enough activity to let the market seep through their barrier in its entirety. A more personal note about the fee market I'm the only person involved with core who tried to understand the dynamics of the fee market beyond the expected capacity. Yeah, my starting point was the "Inclusive" paper by Lewenberg, Zohar, et al.. But I am the only one who bothered trying to understand the nuances of the dynamics of miners and improve the transaction selection formula. Afaik, this makes me the second most knowledgeable person about the Kaspa fee market. Why second? Because I was outdone by a collaborator. One of the people here on CT (who asked to remain undoxxed) is lowkey one of the smartest guys around. He's a Ph.D in financial mathematics with a long standing interest in Bitcoin, who luckily found his way into the Kaspa sphere. After a few conversations where I explained all my hunches and intuition, as well as the math I've done so far (that you can find in my "Three Woes" post series), they found and fixed inaccuracy in my math, made further analysis, simulated various strategies, and wrote a freaking preprint draft of his findings: drive.google.com/file/d/1yaT… A few months ago, I presented this to Yonatan and Michael, but they pretty much ignored it. (But that didn't stop Yonatan from making later statements about the fee market that are wrong, claiming there's "work to be done", which ties in with other instances of people noticing the dev leads ignoring ideas and knowledge that didn't originate with them.) I'd go as far as saying that it was a considerable oversight on their part to see a massive TPS event on the horizon and not even consider the fee market. As always, I'm willing to collaborate on this, devs who want my help/opinions/ideas are as usual welcome to approach. The Kaspa fee market is a glorious, but gentle beast, and now it is a good time to tend it. Seeing it finally go live is not just imperative for reviving the mining market. It's also a scientifically significant endeavor. Technicalities You can't just add this option and ship it. You also need to provide a way for wallets to check the fee threshold. The easiest way is to add an RPC command to ask peers for their current threshold. There's already a fee estimation mechanism in place, so wallets already know how to inspect their peers' mempools before suggesting a fee. So I believe adding this extra check shouldn't be too difficult. There are obviously other technical nits I'm glossing over or completely missing (e.g., the fee is not a fixed number, but depends on the structure of the txn [for example, a byte of payload is much cheaper than a byte of a digital signature, and let's not even start talking about storage mass), and this should be factored in. Especially if we want to extrapolate a single number to represent the fee of an arbitrary transaction.) That's why we need actual devs to discuss this, so I'm glad a few of them picked up the glove. Dynamic Fee? While I do not think there should be any complicated threshold estimation within the node, I wonder if there's room to consider nodes that dynamically set the threshold according to their peers. That is, if a miner doesn't really care for maintaining the threshold herself, and just wants to coast on the network effect, it would be nice for her to have an option to instruct her node to always take the average/minimal/median/etc. threshold of its peers. In Summary Miners should have the option to set prices. As long as they don't, the fee market is artificially restrained. Obstructed even. It's the crypto equivalent of a price-controlled market. The most direct option is to set a command for minimum fee threshold. To facilitate this option, a command to set a minimum price should be added. Placing it as an RPC command will make it much easier to write scripts that update the threshold according to existing data. If you find this post too long and involved, I'm sure @RionTheG will soon post an accurate distillation of the main points, as he often does (and does well).
9
910
Kaspa processed 60M TX in one day and hit a new record in TPS my node size grew up to 100 GB its not about raw numbers but about achieving this on decentralized PoW with cheap node hardware and NC like security TX´s get confirmed in seconds, no waiting, no bullshit, just kaspa 😎
2
2
13
743
another record eventhough its on average 10bps with around 300 transactions block propagation is random so in 10 seconds even 15 blocks can appear kaspa doesnt censor (orphan) blocks/miner information/done work think about this - take your time
3
249