Cryptello

[Cryptello @DeCryptello]

@bundeskanzler Ihr seid so ein schmierenkomediantischer Clownsverein! Am besten auswandern und woanders sein bestes geben! Das Land ist am Arsch…

[Cryptello @DeCryptello]

@dogeai_gov @DeItaone But consumers at home often bear the cost. Tariffs make imported goods more expensive, which leads to Higher prices for everyday goods, increased costs for domestic companies that rely on imported components, and retaliatory tariffs that hurt domestic exporters.

[Cryptello @DeCryptello]

@goldi Mir ist selten so viel Dünnschiss unter die Augen gekommen. Ich weiß nicht was man dazu noch sagen soll. Dass X ansich eine rechts propagierende Plattform ist, habe ich schon vor Jahren gemerkt. Die Algos liefern ständig rechten Müll. Bleib hier, um Teil des Gegengewichts zu sein

[Cryptello @DeCryptello]

@MarkelGerald Das israelische Regime hat begeht seit Monaten Kriegsverbrechen!

[Cryptello @DeCryptello]

@MissCryptoGER Wenn man nicht überwiegend in Altcoins investiert ist 😂

[Cryptello @DeCryptello]

@elonmusk Fuck u all racists… you make war, take what isn’t yours and then dump on people who fight for their rights… world is going crazy… colonialism is still present 💔

[Cryptello @DeCryptello]

@HorstHauser1 @maikpi70 X wird immer besser. Davor wollen uns Regulierungen schützen. Zuvor habe ich einen ähnlichen Beitrag gesehen, mit einem anderen Überwachungsvideo. Was für eine Masche ey.

[Cryptello @DeCryptello]

@alphadojo_net Wieso jetzt nicht eine Swing Position mit kleinem Hebel aufbauen?

[HEXscout @hexscout]

Dear @elonmusk , may I draw your attention to this massive crime by the SEC, which in this case 👉 (https://t.co/uYfwLVeKvO) is actively fighting Free Speech—something you and @realDonaldTrump have thankfully been strongly advocating for. Investors have suffered billions in market cap losses, in an especially malicious way, as the former instigator, the Deep State puppet Gensler, even misused X to maximize the damage to these crypto assets with the highest possible exposure.

[Cryptello @DeCryptello]

@hoss_crypto Wenn sie wirklich Staatsreserven in Bitcoin aufbauen wollen, dann wäre es klug, ab jetzt nicht mehr so viel darüber zu sprechen 💡

[Binance @binance]

The blockchain trilemma explained 👇

[Cryptello @DeCryptello]

@binance $KAS

[Cryptello @DeCryptello]

@CryptoCallejon @alphadojo_net Hat er das nötig?

[MetaMask 🦊 @MetaMask]

Happy Friday, Degens 🦊

Here's what you've been swapping this past week:

$PEPE (@pepecoineth)
$SLAP (@CatSlapToken)
$SHIB (@Shibtoken)
$DSYNC (@DestraNetwork)
$HEX (@HEXcrypto)

[HEXscout @hexscout]

@MetaMask @pepecoineth @CatSlapToken @Shibtoken @DestraNetwork @HEXcrypto What is the financial revolution HEX? Learn to understand it in just 10 minutes: https://t.co/jhlpHPF8R2

[Richard Heart @RichardHeartWin]

Retweet if you want me to go live.

[Shai (Deshe) Wyborski @DesheShai]

Hi $kas. I wanted to write a recap of the KRC20 launch and its consequences now that almost 24 hours have passed.

Before that, I want to stress that I only found out about the bug in KasWare yesterday at about 11PM Israel time. I was very saddened to found out that some community members lost funds due to a completely avoidable 3rd party bug, tarnishing what otherwise would have been an unequivocal day of celebration for our community. Since hearing of the bug (and despite having to leave for a flight in three hours) I've spent most my efforts trying to understand what happened and what can be done, I'll get back to this below.

I wanted to share my interpretation of the last 24 hours layer by layer.

Consensus layer: the Kaspa L1 was given a legendary stress test, possibly the largest in PoW history. In just 8 hours the network processed more organic transactions that ETH can handle in a week. All throughout we monitored nodes and found that the Rusty Kaspa client can handle these huge loads on cheap hardware without breaking a sweat. For the Rusty crew and anyone focused on the L1, this was an abject success.

Peer to peer layer: similarly, the network handled the loads very well. At no point was it hard to find peers and even at the height of pressure, syncing nodes worked perfectly. Even with a mempool of 50k transcations in queue (the highest I tested) nodes were able to sync from scratch in less than an hour.

Mempool: the mempool is the real star of the show. The modular refactoring of the mempool withstood queues in the six digits without flinching. I remind you again that we have nodes running on century old laptops and on Raspberry Pis. We've already done bigger stress loads on TN11 so we weren't terribly surprised, but seeing the Rusty nodes working like clockwork under an excessive strain caused by more than 50 coins deployed on the same day provided very strong affirmations to just how much of a wonder Rusty-Kaspa is. I was also fortunate enough to wake up in time to see the point where the rate of transaction issuence went below the network capacity, enjoying the beautiful sight of a mempool clearing down from six digits to zero in less than five minutes.
Moreover, the RBF and fee estimation features seem to work extremely well. Fee estimation on DAGs is trickier than one might think, I will hopefully write a post about it soon.

The bottom line is that even of the light of the extremely chaotic usage oscillations, not a single node had to be restarted.
The conclusion is that the entire L1 proved god-tier performance and resilience.

Ecosystem: This is where things unfortunately go a bit sour.
After a few hours it became apparent that one of the 3rd party wallets, @KasWare_Wallet, had incorrectly implemented their RBF policy. I am not sure on the details, but it seems that their logic for some reason mixed the minting and the change UTXOs, causing the change to go to the miner. So in some situations, a person with a single UTXO of X Kaspa who wanted to pay a fee of Y instead found that they actually paid X-Y. This could be terribly painful if, say, X is in the tens of thousands while Y is, like, three.
Due to the KasWare wallet being closed source, and their devs incompliance in properly informing their community, some of the devs had to issue a statement (given voice by @CryptoAspect) guiding users to stop using KasWare. I also made a parallel announcement from my X account. But at this point the damage has been done.

There are lessons for everyone here. I learned in hindsight that I should have insisted that Kasplex also provide their own open-source wallet (which they will, following yesterday's events). Kasplex's motivation for not developing a wallet was to leave room for more community development, which sounded very reasonable to me at the time.

I could maybe also have been more active with warning users to exercise caution. Experienced users know to never trust large sums of money to a 3rd party dev with no reputation, especially when their code is closed. I could have stressed that, and advised people to only move funds to minting wallets in small quantities at a time. The Kaspa community is very educated and mature, so I keep forgetting that many community members are new to crypto, and don't realize how unfortunately common such mishaps are in the crypto industry.

I am not familiar with the KasWare team and never had any contact with them, but I hope they learned harsh lessons as well.
In particular, it is clear that they did not properly test their wallets in high loads (which is easy to do on Testnet, the Rusty-crew do it all the time as part of their testing methodology).
That's why I also urged users to stop using their wallets for now, despite updates from KasWare that allegedly solve the issues. This is just too delicate to be handled by on-the-fly patches, and the only reasonable thing for them is to shut it down and go back to the drawing board.

I am currently trying to obtain data analysis showing the extent of users/funds affected by the bug, and checking what can be done to help users who lost funds.

More on the ecosystem: the exchanges. Some exchanges were responsible enough to work with us to implement RBF, other exchanges didn't. The latter found out that they are unable to process withdrawals because they don't have logic to raise fees when necessary. That's stupid, but I think at this point users can see which exchanges try to respond to updates in the network and which just ignore it at the expense of their users, and make future choices accordingly.

For me, the launch as a whole was very bittersweet. Everything was almost perfect, the only thing that went wrong (besides CEXes being CEXes) is one bug in one 3rd party wallet. But the consequences of this bug fell on the Kaspa community, which saddens me very much.

(And a small digression: some pointed me to a post claiming that "kHH is broken". I will try to find a post explaining all in great detail but the bottom line is: kHH is not broken, the "issue" raised in the post is inconsequential, we have known about it and publicly disucssed it as early as January 2022. The post is based on the work of a researcher that is mentioned by name, we contacted them and they agree with us that the subtlety pointed therein is not "a break" and has no consequences on the security of our network, and his work has been misrepresented. I will grab the instructive opportunity in the future, because explaining the fud away affords a very nice discussion about the internals of kHH, but that'll have to wait for when I am less busy.)

[Cryptello @DeCryptello]

@Dernimmersatte Wo bin ich hier gelandet? Oh mein Gott „X“…

Hab selten so einen Bullshit gehören und die ganzen Leute die das glauben 🤦🏻‍♂️ oh sorry 🤦🏼‍♂️

Das Video ist mit KI gemacht…

[T-ᗷIᖇᗪ @TheReaLTBird26]

Until finance and commerce are conducted universally and frictionlessly with #crypto nothing in this world will change. If this change doesn't happen, then the appetite for trash fiat will not diminish.

Until you change the way money works,
you change nothing.

$HEX $PLS $PLSX #PulseChain

[Richard Heart @RichardHeartWin]

Richard heart teaches you things no one else can, or will.

You do not custody coins, the blockchain does.
You do not send coins. You publish updates to a public database. The coins are right where they always were.
You do not have a cryptocurrency wallet, you have a keychain.
Every addresses was created and published by individuals through their own labor.
Every update was created and published by individuals through their own labor.
There aren't really any coins, just numbers people have a penchant for. Like characters in literature.
If the value was in your wallet, the value would double when you copied your wallet. It doesn't.
If the value was in the blockchain, the value would double when the blockchain was copied. It doesn't.
The value is a shared fiction, subjective and volatile, subject to whim and fancy, yet worth $ billions.
You don't use the blockchain, you run it, it's software.
In the blockchain, you're not a user, you're a publisher.
Blockchain software is publishing software.
Speech is speech.
Code is speech.
The blockchain is both speech and publishing software, and as such, should be doubly protected; Like you would protect books and the pen.