v

@Shawn173985 @shimadonia @RionTheG What a pancake

@shimadonia @RionTheG The Kron tech be teckin

i've already did 3X stop it brooooo kron.technology

@e77st @KaspaKaha It's been 1 month since a very significant upgrade, with another on the short term horizon. Let's check back in a year.

@v4n1m4 @KaspaKaha Time has already shown everything on the distribution chart of 96% of the emission, price, number of active users, on-chain metrics, integrations and cash flow of projects 🔻☠️

Stablecoins on Kaspa are live — but only on L2 for now. Current bridged stables across Igra + Kasplex: • Total: $1.47M • USDC: $1.10M (peg -0.03%) • USDT: $370.7k (peg -0.53%) Most of it sits in lending markets. DEX pools are still tiny. Kaspa still has no native stablecoin issuer tracked. The real question: When do we get proper stables on L1? @Kaspa_HypeMan @KaspaKii @Kaspa_KEF KaspaKaha.com $KAS #Kaspa #KaspaDeFi

@cryptosione @KaspaKaha @KronTechnology @Hashlock_ @sherlockdefi Nope, fair thing to wonder, I've wondered the same thing. The answers I've received include that the firms are engaged with KAS blockchain, and are senior engineers. The audit seemed like a pretty certificate to me...as how can something so new be properly audited? We'll see.

@v4n1m4 @KaspaKaha @KronTechnology @Hashlock_ @sherlockdefi Im wondering how do those audit firms that specializes in smart contracts can test and audit kaspa native/silverscript Or am I missing something

“KRON is fishy - they never published the source.” We keep seeing this. So we did the next best thing: we decompiled the deployed covenant straight off Kaspa L1 and read it. Here’s what the on-chain bytecode actually shows. No admin key. No pause, no seize, no upgrade hatch - the only signature check in the whole system is ordinary per-owner token auth. Nobody can freeze or drain it. No hidden mint. Supply is minted once at genesis and the mint path is permanently closed after - we checked it against the actual genesis transaction. 399M to the curve + 21M dev = 420M, matching the advertised max. The dev allocation is exactly 5%, and it’s sitting where it should be on-chain. The “permanently locked” graduation liquidity is genuinely unremovable, and the pool math (constant-product, LP shares, fee routing) holds up - rounding consistently favors the pool, not an extractor. In short: from the bytecode, this does not look like a scam. One honest caveat, stated plainly: a decompile is what the deployed script does - it is not KRON’s source. We can’t byte-verify that the on-chain script was built from any particular source file. So take this as “the deployed covenant behaves correctly,” not a stamp of approval. So here’s our open offer to the KRON team (@KronTechnology): hand us the source and we’ll run a full, proper audit against it and confirm the build - under NDA if you’d prefer to keep it private. That’s how you close the gap for good - not our word on a decompile, but a reproducible audit of the real thing. The door’s open whenever you are. Now the part that’s bigger than KRON. The same thing that let us audit an unpublished covenant - full execution logic living on L1, in the open - is exactly what lets a searcher model it and extract from it. Read access and extraction access are the same access. That’s the whole point about MEV on Kaspa. It isn’t hiding in a dark forest. It’s in plain sight, by design, because the chain is transparent by design. You cannot have fully-inspectable on-chain logic and ordering that’s somehow invisible to searchers. Those are the same property viewed from two sides. Which is why “just make it private/resistant at the app layer” doesn’t work. If the logic is on L1, the ordering opportunity is on L1. The only place you can actually address it is the consensus/DAG layer - the ordering rules themselves - not the contract on top. That’s the real conversation. @michaelsuttonil @hashdag - this is your territory, not the app developers. KaspaKaha.com #KAS #Kaspa #KaspaDefi #MEV

@e77st @KaspaKaha No worries Eugene. Been in the space over a decade here. I can see pretty clearly how far ahead the technical side is from the pack. Chat in a year or a few mate, no point arguing about the future. We can let time tell :)

@v4n1m4 @KaspaKaha I've known her very well since the beginning of 2023 This is a scam of greedy whores, not an ecosystem.

@e77st @KaspaKaha There's over 300 apps Maybe get familiar with the ecosystem

@KaspaKaha If a network lacks an ecosystem—with virtually no applications or developers—then what use does it have for stablecoins? Neither #Tether nor #Circle is going to enter a network populated by robbed, dying-out #miners &naive holders who bought into fairy tales about the trilemma)🙄

@shimadonia They will only be convinced or bother learning after the fact. It's human nature. The bright side is it gives anyone who understands more time to prepare for potential adoption. Exciting.

@v4n1m4 Something this big is sitting right under our noses and no one gives a shit because they're obsessed with percentage drops and pumps every other video is just "how much we dumped.. how much we'll moon" it's pathetic and disappointing as hell. not one single video that cover it

Extremely significant

@kasbtc_krc20 @elldeeone @Twixx2407 @KaspiumOfficial @Classicxbt @IzioDev @manyfest_ @0xKnitser @KaspaKaha @KasWare_Wallet @KronTechnology Nice @kasbtc_krc20 🫡 Pretty sure Shawn @KronTechnology is coming here later to mention about what's open source/to be open sourced, scope of audit, answering anything unaddressed etc. for Luke and anyone viewing. Morning where he is. Looking forward to that.

We would like to confirm that we reviewed the public SDK and integrated Kron into both our token explorer and KCC20 indexer so people can find them, but we did not review the .sil template and compiler as these are still kept private. When this is public we could review the full source but we are also still waiting for a reply when template and compiler are finally public.

As DeFi starts to take shape on Kaspa, it might be a good time to repeat the basics: Just as you should refuse to sign a paper contract you are not allowed to read, you should not pay into smart contracts with hidden rules. DYOR and know what you buy. There is still an active and meaningful effort to define standards for covenant scripts and fungible tokens. These important decisions will ensure tokens are recognized, supported, and composed with other ecosystem projects. Otherwise what would be the value of an asset that can only be recognized and used within a specific app? Let’s continue building great things and do DeFi the right way.

@Shawn173985 @KronTechnology @HocusLocusT If you're in the Kaspa discord community you'd know the answer.

@KronTechnology @HocusLocusT How did you have thousands of unique visitors when you never promoted KRON until it was already launched? 🤔

Transparency: one KRON token launched using our Beta vesting option. We've since found that vesting makes a token's on-chain program large enough that a sell transaction exceeds Kaspa's transaction size limit, so the network rejects it. Vesting is now disabled for new launches. Every other market on KRON buys and sells normally. No funds are at risk: balances sit on-chain and are untouched. The affected token's page carries a full warning you must acknowledge before buying. We're sorry we didn't catch this before release.

@shimadonia We all know it 😎

@shimadonia Literally $icp formerly dfinity main objective was to replace traditional IT structure with a decentralized internet ecosystem. They never did it in a way you could achieve accessibility in a 5 min tutorial. Crazy. They were top 10 mcap just on the idea/prospect as well btw.

@elldeeone @Twixx2407 @KaspiumOfficial @Classicxbt @IzioDev @manyfest_ @kasbtc_krc20 @0xKnitser @KaspaKaha @KasWare_Wallet @KronTechnology Yes, had to make sure every word is spot on for you mate, don't want you to misunderstand lol. Not sure why he hasn't come here to clarify this simple thing either...I'll agree with you on that part. I'd bet there is a lot on his plate, but I pinged him on discord to come here.

@v4n1m4 @Twixx2407 @KaspiumOfficial @Classicxbt @IzioDev @manyfest_ @kasbtc_krc20 @0xKnitser @KaspaKaha @KasWare_Wallet @KronTechnology lol maybe delete and add your comment a few more times mate anyway just a reminder that shawn still hasn't answered those q's or any other direct q's from other ppl in the community so gghf

@elldeeone @Twixx2407 @KaspiumOfficial @Classicxbt @IzioDev @manyfest_ @kasbtc_krc20 @0xKnitser @KaspaKaha @KasWare_Wallet @KronTechnology Yes hence I said when we were talking less than a day ago about it likely being in their proposed audit (see ss), and why I said 'reviewed as much as possible'. You're not dropping heat. Someone communicating in such a dense manner definitely shouldn't be quoting satoshi.

inspecting compiled bytecode ≠ reviewing the .sil, compiler and build process decompilation is reconstruction, not source verification without a reproducible byte-for-byte build, you cannot verify the source matches what was deployed if you don’t believe me or don’t get it, I don’t have time to try to convince you, sorry

@elldeeone @Twixx2407 @KaspiumOfficial @Classicxbt @IzioDev @manyfest_ @kasbtc_krc20 @0xKnitser @KaspaKaha @KasWare_Wallet @KronTechnology Yes hence we were literally talking less than one day ago about my thoughts on it being in their proposed upcoming audit (see ss), and why I said 'reviewed as much as possible'. You're not dropping heat. Someone communicating in such a dense manner shouldn't be quoting satoshi.

@elldeeone @Twixx2407 @KaspiumOfficial @Classicxbt @IzioDev @manyfest_ @kasbtc_krc20 @0xKnitser @KaspaKaha @KasWare_Wallet @KronTechnology Re-read what I said: "(as much as possible with audit pending)" Then look at the @KaspaKaha tweet and Kron's work with @0xKnitser for two other lenses of context (public info with commentary about the covenants and work relating to Kron) Save the unwarranted condescension too.

@v4n1m4 @Twixx2407 @KaspiumOfficial @Classicxbt @IzioDev @manyfest_ @kasbtc_krc20 @0xKnitser @KaspaKaha @KasWare_Wallet @KronTechnology you’ve just conceded my point. you literally said the L1 covenants had been reviewed when they hadn’t. it’s not my problem if you need to be corrected.

@elldeeone @Twixx2407 @KaspiumOfficial @Classicxbt @IzioDev @manyfest_ @kasbtc_krc20 @0xKnitser @KaspaKaha @KasWare_Wallet @KronTechnology Go and look at @KaspaKaha's post, they covered it well.

@elldeeone @Twixx2407 @KaspiumOfficial @Classicxbt @IzioDev @manyfest_ @kasbtc_krc20 @0xKnitser @KaspaKaha @KasWare_Wallet @KronTechnology Chill mate. I explicitly said as much as possible has been reviewed, pending audit, and already said to you sil template + compiler would be in the audit. The point was that everything that IS on-chain and available has been reviewed as much as it can be right now.

@elldeeone @Twixx2407 @KaspiumOfficial @Classicxbt @IzioDev @manyfest_ @kasbtc_krc20 @0xKnitser @KaspaKaha @KasWare_Wallet all of these have done a form of integration using the open source SDK and working closely with the covenant & underlying code/integration with Shawn @KronTechnology The pro audit is the last step.

@v4n1m4 @Twixx2407 @KaspiumOfficial @Classicxbt @IzioDev @manyfest_ reviewed by who?

@GoonBoyCrypto @ScapeSquad The covenant contract was removed from the holders list (since it's locked and not circulating supply) Their holdings didn't change, just the percentage changed proportionately

@ScapeSquad Has this wallet not actually accumulated more $Kron in the last 24hrs though ? Up from 29.6% to 31.1% - that’s an increase of 1.5% of the supply, so it’s not selling it’s actually accumulating more no ?

🚨 x100 $KAS gains in 2 days. Kaspa meme szn hasn't even started! KRON top wallet with ~30% of the supply is starting to sell and withdraw to Kraken. It started 2 days ago with 33K KAS, and just today it reached a peak value of 3.5M KAS. Track movement: kaspa.stream/addresses/kasp…