Kripto Veteran

[Kripto Veteran @KriptoVeteran]

@RedPandaMining Maybe gıveaway for us :)

[Kripto Veteran @KriptoVeteran]

@travladd @grok Good on ya! $KAS

[elperor @elperorr]

⚡The platform CoinMarketCap owned by #Binance just added the "Buy KAS" button on the Kaspa page.

This button is usually added to coins spot listed on Binance.

Many big X accounts were noticed posting about $KAS lately.

The price surged 16% last 7 days.

Is it happening ? 👀

[Oisin.D @oisinlee]

Kaspa L2 with SmartContract is under testing 😏

#Kaspa #Kasplex

[MMOStars @MMOStars]

$KAS is officially added to CoinMarketCap "Top Made in America" assets category: https://t.co/xIRnMKwlb6

[Michael Sutton @michaelsuttonil]

This visual gives the feeling of water bursting from an obstructed source, paving its way into new territory...

[Michael Sutton @michaelsuttonil]

wow, what a day

[il Donaldo Trumpo @PapiTrumpo]

STOP IT!!!🤣🤣🤣

[supertypo @supertypo_kas]

The "10bps readiness release" - v1.1 of simply-kaspa-indexer is out! 🥳
Highlights include selective indexing, better performance, more compact storage. And a brand new api w/metrics&health.
https://t.co/xWjHRmzGZq

[Tyler Bea @skibumtrading]

Looks like @binance just updated the date that they will send $KAS mining rewards to users’ funding wallets.

They are now expected by March 6th.

[Michael Sutton @michaelsuttonil]

Almost done with the realization of this KIP in bits and lines of code. So many details and so much responsibility, but we’re almost there

[Kaspa @kaspaunchained]

PSA: @coinbasetraders lists $KAS Futures.
Thanks @coinbase

[coinco @coinco041]

KAS promotional mining on @binance ended on January 27th, 2025 and they said rewards will be distributed within 14 working days into the user's wallet.

So, @Binance will distribute $KAS into "Funding Wallets" by Feb 10th.

So technically binance should list $KAS by the end of the second week of Feb or early third week.

What do you think #kasfam ?

#kaspa #Binance #kasplex

[Mona @krypto_frau]

Sold my chair 🪑 to buy the $KAS dip

[kns.kas @knsdomain]

KNS Mainnet is set to launch on January 27th!

This marks a significant milestone for KNS and the entire Kaspa ecosystem, allowing users to register their .kas domains and text inscriptions.

To prepare for launch, we’ve also updated our docs below.

🌐: https://t.co/Xas4TtuV9B

With our docs release, we also welcome builders/ communities to integrate our inscription products for inscribing domain and text inscriptions.

Let’s make history together! KNS appreciates your continued support.

kns.kas

@KaspaCurrency $KAS #Kaspa #KNS

[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

[elperor @elperorr]

⚡The exact spec and design of the upcoming 10 bps Crescendo upgrade on Kaspa is out for public review and discussion.

$KAS #Kaspa #10bps

[Michael Sutton @michaelsuttonil]

So I'm done with the most heavy research post I had to write. Let's start crescendoizinggg 🎼💃
Are you in for the ride @coderofstuff_ ? we got some stuff to code 😀

[Kripto Veteran @KriptoVeteran]

@binance $KAS !!!