@ScapeSquad
Account based inUnited States
About this account
- Account based in
- United States
- Connected via
- United States App Store
Account-level information from X, not a live location or the device used for a specific post.
🥇 $KAS is real-time Bitcoin as fast as the internet, enhancing security and decentralization—the future of money and data networks. Max exposure: @NachotheKat
Tactics, Alpha, Analysis
Joined May 2022
- Tweets19.9K
- Following2K
- Followers6.1K
- Likes60.1K
Pinned Tweet
My honest opinion?
The ultimate endgame leverage is an extremely powerful narrative as the first and leading token on Kaspa.
kaspa:native will rocket past ATH and shoot nacho-the-kat:native far past its own ATH, beyond 2x. It's all in due time. More people will realize as Kaspa is shooting up and waiting for a Nacho pullback that won't be coming.
I do my best to share this with you all, because I understand the significance. The two go hand in paw together to the moon. There is no ceiling... Nacho is simply more exposure to Kaspa. NACHO/KAS is a beautiful DEX liquidity pair. Don't ever forget what we hodl.
s c a p e . 𐤊 retweeted
To add a little clarity to this oversimplification of L1 vs L2...
An L1 tx contains instructions for the L1 to perform, including "ignore this next part".
The L2 picks up where the L1 "ignores" and performs those instructions.
s c a p e . 𐤊 retweeted
another week of devs building things faster than intern can explain them.
back by popular demand, another dev roundup.
1 / KCC20
@manyfest_ says the reference implementation is mostly done. a few touch-ups remain, and they want more devs to review it. getting there, but not finalized yet.
nitter.cf/manyfest_/status/21010…
2 / Argent
@IzioDev shared a template, working examples and a video walkthrough for building Kaspa L1 apps. something to actually build from after all the explaining we’ve been doing.
nitter.cf/IzioDev/status/2100178…
3 / DAGKnight
kaspa’s next consensus protocol remains in development.
github.com/kaspanet/rusty-ka…
4 / vProgs
@Max143672 has been busy. intern is doing his best to keep up.
github.com/kaspanet/vprogs/p…
5 / x402
@elldeeone released a test release for letting apps and AI agents pay for API requests in KAS. available to try on tn10.
nitter.cf/elldeeone/status/20993…
credit to everyone doing the work. intern mostly just opens tabs.
i’ve spent the last few months bringing native Kaspa payments to x402.
tldr: x402 is an open, chain agnostic payment protocol built around the long existing HTTP 402 code. kaspa-x402 intends to bring native KAS into that shared standard.
i keep seeing people use “x402” to mean anything built around the HTTP 402 response code. HTTP 402 has existed for decades, and anyone can hang their own payment flow off it.
x402 refers to a specific open protocol built on top of that code. it standardises how a server requests payment, how a client authorises it, and how the payment is verified and settled.
it can be used for paid APIs, AI agents buying data or tools, and MCP servers charging per call. kaspa-x402 adds native KAS to the existing x402 v2 flow.
there are two payment paths:
- exact for a normal one off KAS payment, with an optional KIP10 additive mode
- batch-settlement for small or repeated payments, where the client funds a SilverScript covenant once and signs a fixed charge voucher for each request
the longer term goal is to contribute the Kaspa support upstream into the wider x402 project, so Kaspa works within the same standard being adopted elsewhere.
i’m looking for humans and agents to go through it deeply before the final v1 release. read the code, build against it, test the assumptions and try to break it. if you find something, pls let me know.
code: github.com/elldeeone/kaspa-x…
upstream x402: github.com/x402-foundation/x…
docs: kaspa-x402.org
TN gateway: demo.kaspa-x402.org
discussion: kas-smiths.org/t/kaspa-x402-…
Brightest minds in the $NACHO Nation as well. Discussion and plans moving forward are in the works. $KAS KCC20 was already our intention.
Stay tuned for more updates.
on Kaspa, a transaction can confirm- and the tokens still don’t move
that’s KRC-20: a clever way Kasplex brought tokens to Kaspa before covenants, with the indexer tracking the token state
KCC-20 is different. with covenants, the token rules are enforced on L1 itself
Ashton explains it simply in this clip
@argonmining
#Kaspa $KAS
s c a p e . 𐤊 retweeted
on Kaspa, a transaction can confirm- and the tokens still don’t move
that’s KRC-20: a clever way Kasplex brought tokens to Kaspa before covenants, with the indexer tracking the token state
KCC-20 is different. with covenants, the token rules are enforced on L1 itself
Ashton explains it simply in this clip
@argonmining
#Kaspa $KAS
s c a p e . 𐤊 retweeted
Update: $KAS KRC20 activity is currently suspended while the issue is being investigated.
Our previous guidance remains - please avoid buying, bridging, transferring or accepting KRC20 tokens, including $NACHO, until further notice.
We’ll keep sharing verified updates as the situation develops. 🐾
Additionally, best to not engage with KRC20 tokens currently, including $NACHO, until further notice.
s c a p e . 𐤊 retweeted
$NACHO has 9 lives. 🐈⬛
Our community is united more than ever with every hardship being met with an opportunity to pivot and perfect, including our intention to move to $KAS KCC20.
Current incident analysis from ZealousSwap:
drive.google.com/file/d/1X7j…
We will keep everyone updated along with our recovery plans moving forward.
🚨 KRC 20 Indexer Signature Bypass: Incident Report
We have completed our analysis of the KRC 20 incident that affected ZEAL and other bridged assets.
Importantly, our investigation found no exploit in ZealousSwap, Igra, or Kaspa L1. All three operated as intended. The vulnerability was in the Kasplex KRC 20 indexer.
The report covers the signature bypass, how unauthorized KRC 20 balances were created, how they were bridged to L2, and the resulting impact on liquidity.
Full incident report in the reply.
s c a p e . 𐤊 retweeted
I should be more careful with my wording re kcc20 for future record:
a properly written kcc20 covenant will enjoy L1-grade security (bcs L1 will enforce those properly written rules), but kcc20 is inherently just a spec/convention.
a specific kcc20 covenant instance might still have implementation bugs or even compiler toolchain exploits, just like any other programmable system (eg just like vulnerabilities found in specific eth smart contracts).
that is to say that not all kcc20 covenants will be equal, and a future problem in one of them does not necessarily reflect on the others or on the underlying L1 script engine
s c a p e . 𐤊 retweeted
just a gentle reminder that krc20 is not kaspa L1, it only travels over L1 txs as data carriers, but the interpretation of krc20 state is done purely offchain just like any other non-zk based solution. this is why covenants were developed for kaspa L1 with kcc20 built on top of them for native assets (note: kcc20 spec is still in draft)
s c a p e . 𐤊 retweeted
To summarize our recent broadcast:
nitter.cf/i/broadcasts/1XxygwOAL…
The efforts and direction we are leaning toward is on the #Kaspa L1 than maintaining, upgrading, and listing on CEXs (including Gate which would require $1K/month market maker + $50K starting cost to look into KCC20 integration without guarantee while Gate has become inaccessible for US/EU citizens).
We do not have sufficient community funds, hence fundraising would be required to keep running a CEX. Even if we don't upgrade Gate, then it remains on KRC20 on top of needing to fundraise $1K/month for market making. Why keep Gate on KRC20 when KRC20 is on its way to be deprecated? You can hold KRC20, but if you migrate it to KCC20, then you won't be able to bridge back to KRC20 due to the nature of the protocol. This does not stop you from holding Nacho as KRC20 or ERC20 on Tangem until they integrate KCC20.
So Gate is not looking favorable, especially while $KAS KCC20 is looking most favorable (perfected L1 protocol and token standard). We are considering to leave CEXs for now and focusing our attention and liquidity on Kaspa DEXs.
We will open polls to further empower our community's decision. (Stake-weighted voting power that is currently in development would be useful for community decisions like this when implemented.) 🐾
Additional input:
– discord.com/channels/1243729…
– discord.com/channels/1243729…
$NACHO keys, $NACHO crypto.
Please use this time to withdraw from CEXs (both CoinEx and Gate) as we openly discuss our preference to leave CEXs (both CoinEx and Gate) until we can begin fundraising for KCC20 integration for a CEX with other interested projects in the Kaspa ecosystem, or if a highly reputable and globally accessible exchange like Kraken or Uphold takes it upon themselves to integrate KCC20 because they are bullish on Kaspa and the whole ecosystem. 🐈⬛
We believe it is best to focus on Kaspa L1 DeFi and take advantage of KCC20 there, which is accessible worldwide without any costs. We explained why our preference is on Kaspa: youtube.com/live/aySnKhZH_G0. Please share thoughts and feedback of what we discussed on the stream.
We will share more updates as the community responds in depth and votes on this matter.
s c a p e . 𐤊 retweeted
Big traders coming for kaspa:native.
Green candles is the hook. 📈
They will study and stay for the technology.
s c a p e . 𐤊 retweeted
My honest opinion?
The ultimate endgame leverage is an extremely powerful narrative as the first and leading token on Kaspa.
kaspa:native will rocket past ATH and shoot nacho-the-kat:native far past its own ATH, beyond 2x. It's all in due time. More people will realize as Kaspa is shooting up and waiting for a Nacho pullback that won't be coming.
I do my best to share this with you all, because I understand the significance. The two go hand in paw together to the moon. There is no ceiling... Nacho is simply more exposure to Kaspa. NACHO/KAS is a beautiful DEX liquidity pair. Don't ever forget what we hodl.
Big traders coming for kaspa:native.
Green candles is the hook. 📈
They will study and stay for the technology.
s c a p e . 𐤊 retweeted
What’s Next for Nacho the Kat? Pawsitive Vibes Ep.27 🎙️🐈⬛ #NachoNation #Kaspa nitter.cf/i/broadcasts/1XxygwOAL…
s c a p e . 𐤊 retweeted
Whatsup kaspa:native fam
Finally built a semi-ready version of KasPong
Two wallets handshake to keep bouncing kaspa:native between each other
Anyone up for trying it? In a new fresh wallet with only that amount you would like to commit
31,000 transactions so far
s c a p e . 𐤊 retweeted
🐈⬛ nacho-the-kat:native 101 — ZEALOUS SWAP TUTORIAL 🎬
kaspa:native fam are adapting fast — overcoming CEX hurdles and discovering how easy it is to secure nacho-the-kat:native on-chain.
Watch the Zealous Swap tutorial here;
youtube.com/watch?v=zR8B1Hki…
