Your most precious assets should be taught that nothing is impossible--not even the moon.
Stay Based. Stay Pepe. Stay Based base:0x52b492a33e447cdb854c7fc19f1e57e8bfa1777d 🧢🐸
base:0x52b492a33E447Cdb854c7FC19F1e57E8BfA1777D
https://t.co/uoK6HAsWsi updated pushed - dynamic smart mass txn batching when sending mass amount of $KAS to multiple hundreds of wallets - working on krc20 tokens with L1 kaspa: addys - All KCC20 tokens are loading in -
DAGKNIGHT is a proposed replacement for GHOSTDAG, Kaspa’s current consensus protocol.
Blocks take time to reach other miners. GHOSTDAG accounts for that with a preset delay assumption, which influences confirmation times even when the network is running smoothly.
DAGKNIGHT orders blocks without needing that delay bound fixed in advance. Its consensus can adapt as network conditions change.
Still in development.
1/12 Introducing dotk 🥳, a name service built different - unique, trustless, decentralized - enforced by covenants. Names are a binding of name (supertypo.k) to an address (kaspa:...). dotk names are cheap, and I have a whole page dedicated to the *why* it exists. Highlights 👇
@supertypo_kas i got to say that https://t.co/saweaaMKoM shows impressive covenant design, with an inherently partitioned and scalable state space. big like.
@kascovio links are live on every token page.
Every KRON token page now links straight to that token on https://t.co/zuwumOxf65, the independent Kaspa covenant explorer.
One click gets you the layer under the chart: decoded KCC-20 state, balances and events, with every decode checked against the token's on-chain commitment. Not our numbers — the bytes.
It's on every token, on-curve and graduated alike. Look for the ◉ next to verify on-chain.
The Kaspa explorer links aren't going anywhere. kascov reads the covenant layer, https://t.co/Et6Otzn9CQ has the raw transactions — now you have both, one click apart.
kascov is built independently by @0xKnitser . Not affiliated with KRON.
GEMINI × KASPA SILVER
Join us live with @KaspaSilver for a conversation about Kaspa, the technology behind the project, and the community around it.
Tomorrow @ 9am ET
Be there or be square🟧
Everyone is debating how KRC-20 tokens should migrate to covenant native KCC-20.
We stopped debating and ran one on Kaspa testnet-10.
One snapshot, sealed into the token's identity at birth. Every balance claimable exactly once. Zero admin keys after the handoff. Not a bridge, no operator, no committee. Kaspa consensus enforces every claim itself.
Five real transactions, all public: token genesis, controller genesis, reserve handoff, a Merkle claim, and the claimant spending what they claimed.
See it live and click every receipt yourself: https://t.co/2CtAHvQbsT
Honest print: the run used one synthetic holder, KCC-20 is still a draft standard, and this is testnet. The mechanism is proven. The rest is verification work, and it is listed on the page.
kaspa:native
#Kaspa #KRC20 #BlockDAG #KCC20
Today we’re taking a look at KRON, a project building a native DEX and launchpad on Kaspa L1.
KRON uses Covenants to enforce rules on-chain, allowing users to launch and trade tokens directly on Kaspa.
No bridge. No EVM. No Layer 2.
Just another example of what developers are building around the Kaspa ecosystem.
This is only the beginning…
#Kaspa #KAS #KRON #KaspaEcosystem #BlockDAG
@KronTechnology
The KRON covenant audit has begun. @Hashlock_ has the repo.
Four covenants, every entrypoint, no sampling and a reproducible build check so the audited source provably matches the deployed bytes.
#kaspa#kcc20
Quick note for the community: KRON does not currently have any official PR representatives or spokespeople beyond this account. If you see anyone, including accounts branded with "KRON" in the name posting status updates, running giveaways, or claiming authority to speak on KRON's behalf, that is not authorized by us.
Please never send your wallet address, keys, or anything else to a third party "giveaway" claiming affiliation with KRON. If we ever run something official, it'll be posted here first.
#kaspa
#kron
kron-sdk 0.18.0 is live on npm.
The SDK now builds trades for tokens on KRON's newest covenant schema — recipient-bound trades with pinned payout outputs, straight out of the audit hardening rounds. Per-token ABI resolution, byte-parity-verified against production. Existing tokens unaffected.
npm i @kronsdk/kron-sdk@latest
https://t.co/jSy211psVr
$kaspa