Kaltoum_S

[M6 Info @m6info]

📸 Connaissez vous les "Instagram Husbands" ? Ce sont ces maris chargés de photographier leur femme pour les besoins des réseaux sociaux. Une activité source de stress et de frustration pour 87% d'entre eux.

🎥 @deGaudemar 🎙️ @candice_atg

[Kaltoum_S @Shadi_Bada]

RT @Ashcryptoreal: Hey guys! To Celebrate hitting 2 million followers on X, we will be giving away $5,000 Bitcoin or ETH to 10 people in ne…

[Kaltoum_S @Shadi_Bada]

@idreau_ https://t.co/Nr4f7d1Mqr - Pression de pneu & fond de plat !

[The_F1_Whisperer @The_F1Whisperer]

#F1 #HungarianGP FERRARI, LECLERC : modes moteurs, pressions pneus & usure du sous-bassement : les FAITS (1/19)

1) Tour 9 : BOZZI demande à LEC de changer un réglage.
"Mode FS1, mode FS1"
1 minute + tard, LEC se plaint (entendu à la TV) : "il se passe quoi avec les coupures ?!"

[CANAL+ F1® @CanalplusF1]

2 PLACES POUR LE GRAND PRIX DE MONACO À GAGNER 🤩🇲🇨

🌟 Pour participer :
- RT ce post
- Abonnez-vous à @canalplusf1

BONUS : Doublez vos chances sur tous nos réseaux 🤞

Tirage au sort le 21/05 🍀

Règlement en bio.

[Kaltoum_S @Shadi_Bada]

@BDCryptoGuru done

[Kaltoum_S @Shadi_Bada]

@John_wiiic @KaspaCurrency https://t.co/vYGTqgN19h

[Kaltoum_S @Shadi_Bada]

@BRED_BP Une idée de quand reprendront les virement instantanées ?

[Massimo @Rainmaker1973]

How to digitalize a camera film

[𐤊 Lilly 𐤊Kaspa 𐤊 @Lilly_crypto_]

Lets make some noise in pressuring Binance to list Kaspa. Let's all show how great we are as a community!
Like, Repost and comment to get the word out!
#Kaspa #Binance #Kas @binance @cz_binance #KRC20

[Pumpolinsky @pumpolinsky]

Lets make some noise in pressuring Coinbase to list Kaspa. Let's all show how great we are as a community! Like, Repost and comment to get the word out!
#Kaspa #coinbase
@brian_armstrong

[💎 𐤊 @apptwalitty]

Lets make some noise in pressuring Binance to list Kaspa. Let's all show how great we are as a community!
Like, Repost and comment to get the word out!
#Kaspa #Binance
@binance @cz_binance

[Baldwin @Baldwintiktok]

Ce que je ferai EXACTEMENT pour monter à 5'000€/mois si je partais de zéro aujourd’hui

// THREAD 🧵 //

[Monsieur-TK @MiningTk]

Que le projet de la communauté se dénonce 🤣🤣

[Restitutor Orientis 🇱🇮 @restitutorII]

🇹🇷
Iztuzu en Turquie.

[Kasper the Ghost of Kaspa @KasperCoin]

Hey Kasper Fam! 👻✨

Where do YOU want to see $KASPER listed after launch? Share your thoughts below and let’s dream big together! 🚀🌟

Repost and comment your favorite exchange! Let’s make some noise! 🌌

$KASPER the Ghost of $KASPA on #KRC20

#KasperCoin #CryptoCommunity #Crypto #Kaspa

[Ashton @argonmining]

Good morning to all of the $NACHO and KRC20 minters of yesterday. I know you are frustrated, upset, and tired after a seriously long day of attempting to participate in a brand new ecosystem. For many of us, we now must go back to work and our weekday normalities without any sense of resolution to this KRC20 issue.

I’d like to offer you a Post-Mortem Analysis of the NACHO Launch and hopefully provide more insight into what happened and what is to come. Please keep in mind that below is based on the knowledge available to me and my interpretation of it, and I’m not perfect.

Overview:
In line with the spirit of fair launch, NACHO Community decided to hold a Live Launch Event in Discord. NACHO was launched with over 600 community members in attendance at 10:30am EDT on June 30, and minting of the token was immediately available to anyone. I left the Discord stage shortly after deployment to focus on minting for myself and answering questions async in the Discord and Telegram.

Less than 30 minutes after the deployment I realized that something with the KasWare Wallet and/or the Kasplex protocol was very wrong. I returned to the Discord Event that had now grown to over 700 attendees and spent the next 9 hours answering community questions, walking members through changing to a private RPC Node, setting up their own Rusty KAS Node on localhost and connecting to KasWare, and a litany of other situational, psychological, and curiosity questions, many of which I simply didn’t have an easy answer to. I went as far as exposing my own private residential node for Public Use - if you minted any with the OnArgon node, you're welcome 😉

Being so involved in the Discord Live Event for so long yesterday, I did not give enough attention to the chats in Discord, the Telegram community, or our followers on X asking questions. I apologize if you felt unheard and unhelped. While it is certainly not an excuse, we just were not prepared for the support demands the community needed on a day like yesterday. I can assure you that won’t happen ever again in the NACHO Community.

About 10 hours after launch, I was able to step away from 1:1 Community Support and moved to important conversations with the developers and teams involved in the KRC20 Ecosystem. Specifically, the KasWare and Kasplex teams. Kasplex humbly asked us to request the community to stop minting for 1-2 hours so they could push an update to their indexer. We passed that request on to the NACHO community and much of the KRC20 activity subsided on the Kaspa network. Kasplex then proceeded to take down the KRC20 Indexer entirely, which forced an unofficial pause on all KRC20 activities, including checking balances, and we remain in this holding pattern this morning while they work to deploy an improved version of the indexer and KasWare works their wallet.

KRC20-Relevant Issues:
- Transaction already in the Memory Pool: Yesterday, Kaspa established a “Fee Market” for the first time ever. Transactions were being prioritized based on the quantity of gas fee included. If your transaction has no priority gas fee, or a very small one, it was kicked down the mempool list for hours while copious amounts of other transactions with 1+ KAS gas fees were stacked on top of your txn. Unfortunately, “Replace-by-fee” RBF, does not exist on the Kaspa DAG as of now, so those low fee txns were simply stuck until priority processing of the txns organically included your low fee transaction. Implementing RBF could be a potential solution to this issue but is not the most pressing one. With proper development and KIP9 adherence, the mempool issue would likely have been moot. Kasplex discusses here: https://t.co/5inMAgLgaM

- Request Limit Exceeded: When minting in KasWare, users regularly saw this error and had to change Nodes and/or restart their browser to clear the error and continue minting. We are still exploring the exact cause of this error, but what is clear is that the KasWare team rushed an improper fix. During Closed Beta Testing, many projects experienced this error and were assured by the KasWare team that it would be resolved in the mainnet release. My initial knowledge of the error leads me to believe that the KasWare wallet was sending far to many Requests to the node to be sustainable and/or the Automatic Node Load Balancing was non-existent, meaning every request from every KasWare user could have been sent to the same node. We need more time to confirm this is accurate.

- Connecting, Failed to Fetch, & Unable to read UTXO’s: When viewing balances in the Kasware wallet, many users were stuck in an endless “Connecting to network” error. In viewing KRC20 balances or pulling a Ticker in for minting, many users received the Failed to Fetch errors, and upon mint attempts many users received an error about being unable to read/construct UTXO’s. This issue is very likely caused by the lack of proper node load balancing in the wallet, leading to overloaded Nodes that could not handle additional requests. Kasplex addresses this here: https://t.co/8QK2J2LJW4

It seems the most critical issue was the lack of complete optimization for the KIP9 requirements on Kaspa. This caused significant UTXO bloat that led to an even more congested network and an environment where Rust blocks could only hold about 50 txns instead of 200+.

Moving Forward:
Many of these issues are very straightforward to fix and the ecosystem teams are actively working on implementing the solutions, and doing so with interaction and guidance from the core Kaspa dev community. I look forward to discussing and experiencing those improvements in the coming days.

On a more positive note, I really enjoyed helping test a new protocol (KRC20) on the best layer 1 in the world (Kaspa) and making history as the first fairly launched project deployed in the ecosystem ($NACHO).

Nacho's 10M mints and Fair Launch Tokenomics were first on KRC20 and were designed with something like this in mind. We did not run and hide from bleeding edge technology. We led the way as innovators are supposed to do. We forged the path and we will continue to do so. Regardless of the disappointments, bumps, bruises, and challenges that pop up along the way. Those simply makes us stronger as a community, a project, and an ecosystem.

I look forward to minting $NACHO with you all again very soon, and I’ll keep you updated as best I can in the meantime.

[Makertronic YT - Mining , Tech & IA @makertronicYT]

👀

[Kaltoum_S @Shadi_Bada]

@OffTrack_FR Toujours la, Tu veux pas aller commenter a la place d'Eurosport ? Jpp

[Kaltoum_S @Shadi_Bada]

@larry_paust @makertronicYT Trouvé : https://t.co/ikrmUtVCrR

[Kaltoum_S @Shadi_Bada]

@larry_paust @makertronicYT On l'attends avec impatience :)