Oscar

Just do it!

[Michael Sutton @michaelsuttonil]

I decided to publish a v0 of the toccata dev book nonetheless. The writing style is a bit too AI-ish for my taste, but the content, emphasis, and ideas are by yours truly.

Made a big effort to keep it 100% accurate despite the writing speed, but you (or your llm) should read it with a grain of salt and a critical eye.

Any feedback is welcome. Happy Kaspa Toccata day, and may it all go well and smoothly 🤞

https://t.co/hf3IEWcxWF

[Oscar @oanpcl]

@UltronesJugosos @joseantoniokast jajajaja ctm! épico final

[MalditoSudaka @ElPatoAntofa]

Que opina @joseantoniokast de esto Hoy ?

[Oscar @oanpcl]

@Informa3Chile La clase alta necesita subsidio, porque necesitan apoyo "del estado" y de todos los chilenos para costear necesidades básicas?

[Yonatan Sompolinsky @hashdag]

@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

[Francisco Cancino @Fcancinov]

🔴 CENSURA CASO DUQUE:

El jueves pasado publicamos información que confirma que el candidato de Chile Vamos, Aldo Duque, ha defendido a nuevos narcotraficantes, contrabandistas y criminales organizados.

El video fue censurado anoche a solicitud de alguien…

Hoy vamos con todo de nuevo: compartimos AQUÍ el video completo. ¡No nos callarán!

Ayúdennos con su difusión 💣💪

#CensuraEnYoutube
#FNMNoSeCalla
#NarcoDefensor
@AldoDuqueSantos

[Shai (Deshe) Wyborski @DesheShai]

$kas I'm working on a "KIP-15 for dummies". Understanding KIP-15 is crucial to understanding the trust model of smart-contracts in the pre-ZK post-Crescendo era.
Through the writing process, I was looking for a good and friendly reference for Merkle trees and how they work. All explanations I could find are either much too technical, or just completely inaccurate... so I wrote one myself!
I attach it here for those interested in understanding a simple-yet-clever construction that has been a cornerstone of cryptocurrency since before Bitcoin launched:
https://t.co/zAsa20L3Qy

(and as usual, if you find this content educating, entertaining, or otherwise useful, please consider supporting my work)

[Igra Labs @Igra_Labs]

https://t.co/FhKCX1YtJL

[coderofstuff @coderofstuff_]

Over 2hrs later, Crescendo on TN10 still looks legit

[Kaspa @kaspaunchained]

🚀Crescendo Testnet 10 is LIVE! 𝆒
This stage is a HUGE step forward for Kaspa.
Here’s why it matters:

𝆒 Kaspa continues to prove it can scale! Crescendo 10x’s the block speed from 1 → 10 blocks per second!
𝆒 More transactions, faster transactions, smoother experience and ready for further developments with smart contracts, new applications and enterprise market integrations.

This is the final test before launching on mainnet. Running nodes & testing now helps catch bugs, optimize performance, and ensure stability before the big upgrade.

💡 What’s next? Main Hardfork version and then final deployment in ~April/May! 🚀

[Michael Sutton @michaelsuttonil]

~1 hour to testnet 10 crescendo activation

[Michael Sutton @michaelsuttonil]

Late night fully featured Crescendo activation on a small devnet with @coderofstuff_

[Nick @6M_Nick]

@Binance_intern

[Yonatan Sompolinsky @hashdag]

In undergrad studies we were told a true story about a fire that broke out in a conference hotel; the engineer woke up in their room, grabbed many buckets of water, threw them all over the room until the fire was extinguished, and went back to sleep. The physicist woke up, calculated the exact angle, angular momentum, and amount of water to throw at the fire, the last drop elegantly extinguished it, and the physicist went back to sleep proud of themself. The mathematician too woke up, proved to themselves that a solution exists, and went back to sleep.

This tale manifested in kas history, with golang devs taking an engineer's approach, rusty @MichaelSuttonIL taking a physicist's approach, and while I am not a mathematician per se I do tend to be satisfied with proving a solution and going to sleep.

In truth, a distributed systems engineer must embrace the mental model of the physicist, in the sense of comprehending theoretical constraints vs degrees of freedom as a method of drawing the contours of the solution space---merely implementing a working solution is typically not enough, likely unsound. To give a quick example, consider how the full node code should identify or detect when the node is fully synced or require syncing (aka IBD in btc/kas jargon), specifically when a mining node is up to date with the DAG and should start or resume mining. It's very easy to implement some flow that works -- until it doesn't: premature detection may lead to an unsynced miner flooding its peers with out-of-date unmergable blocks, whereas overdue detection leads to synced miners not initiating mining when needed, eg after a network hiccup or a node restart, despite being fully synced. The "physicist" must comprehend these opposing constraints, weigh the respective implications of the edge-threats, pick a sound sweetspot and proceed to the algorithmic design and implementation. This process is much more challenging, rewarding, and robust compared to the prevailing engineers' approach of just building systems that "work" c'est tout.

It was a privilege to watch from the courtside your thoroughness and technological leadership @MichaelSuttonIL. Kudos to you and to the rest of the RK/10bps devs who undertook this heavylifting. More than the product itself, you have ingrained the culture of Kaspa in your image, that of a boutique R&D engine driven by first principles and fundamentals throughout.

Looking forward eagerly, impatiently for the implementation of this KIP and for mainnet HF activation.

Make satoshi great again <3

[Oscar @oanpcl]

@almaplame @TradeOgre Lo lamento Alberto 😞. Yo tuve suerte de poder retirar mis kaspitas desde Tradeogre. A la fecha aún no sé pq pude lograrlo.

[Oscar @oanpcl]

Day #380 ... Still unable to withdraw my $KAS from @TradeOgre 🤡 #TRADEOGRE #Kaspa

[Oscar @oanpcl]

Day #311 without my $KAS from #TRADEOGRE. Could use them to buy $NACHO when #KRC20 works again, but no, i can't 😭. People, be careful with that exchange, please. #SCAM #CRYPTO

[Michael Sutton @michaelsuttonil]

Kaspa Crescendo timeline update:

End of February 2025: Testnet 10 transition activation
End of March 2025: Mainnet version release (activation will be scheduled ~30 days from the release; currently favoring a single, swift transition from 1 to 10 BPS, though this decision will be reevaluated as we move closer to the finish line).

Short-term—January 21, 2025:
* Crescendo hardfork KIP proposing the exact consensus changes and the forking transition strategy
* Medium post detailing the remaining roadmap

[MrBeast @MrBeast]

BEAST GAME EPISODE 3 IS OUT NOW!

To celebrate, I'm giving away $100,000 total to 10 random people who like and retweet this post!

Go watch it here: https://t.co/Yntf9E7FTN

[Kaspa @kaspaunchained]

📢Calling all testers running a TN11 node.
We will soon put up a Testnet-Only Release for the Testnet 11 environment which will hard-fork the TN11 network to include KIP9 and KIP10 consensus changes.

Discord Testnet channel: https://t.co/Fov8OWEZy3

This new testnet release will include all the optimizations and improvements the #Kaspa Dev team has been working on thus far allowing them to determine the minimum recommended node spec for 10bps in mainnet. (#Crescendo)

Stay tuned for the announcement of the testnet-only release in the next few days
The current target for TN11 Hard-fork is December 1, 2024, at 1800 UTC

[Oscar @oanpcl]

@Cryptoprofe_ $KAS obvio! éxito

[Oscar @oanpcl]

@pumpolinsky At 0.15... lol 🤣