That would genuinely be great to have. we need to adopt an open naming layer where anyone can launch an appendix (.custom) so it isnt limited to .k. and wallets resolve them all under one unified standard.
cryptodee 𐤊 retweeted
Pressing concerns about the KEF $kas bridge (only visible after launch).
The bridge address (taken from kaspafoundation.gitbook.io/k…) is kaspa:qypr0qj7luv26laqlquan9n2zu7wyen87fkdw3kx3kd69ymyw3tj4tsh467xzf2.
If you look up the bridge address in the block explorer (explorer.kaspa.org/addresses…), you find that it has made recent spends. e.g.:
explorer.kaspa.org/txs/07c6b…
explorer.kaspa.org/txs/3dd3e…
This raises a few uncomfortable questions, to which I was unable to find answers. (If the answers are out there and I missed them, please let me know so I can post a clarification.)
1. If the bridge is multisig, then how was it spent with a single signature? (See pictures)
* update on that, see in responses
2. Can we see the locking script? Why is it hidden?
3. Who are the signatories? How were they appointed?
4. The only legitimate reason for taking money out of the bridge is withdrawals. Is there any way to independently verify that these spends correspond to exit transactions? (I actually expect this particular question to have a positive response, but I couldn't find an answer in the website)
5. You say that the RD audit report assures transparency and no tampering. But why is the audit hidden from the public? (See kaspafoundation.gitbook.io/k…) Why not release it? I requested to view it for security analysis purposes. Will my request be denied?
Let me make it clear that from a security/trust standpoint, this is very severe.
You should never put your money into a locking script you don't know, unless it is held by someone you would also trust to hold a suitcase of your cash.
Personally, I'd strongly advise anyone who doesn't want to be rugged to avoid using the bridge for anything but playtesting with negligible sums until all questions are satisfactorily answered.
(I also wanted to point out that all these questions fall under my demand to "clarify the trust model." And that the single-signature spends are probably one of the things they wanted to hide until launch, as it could only be discovered after the bridge became operational and made a spend.)
cryptodee 𐤊 retweeted
I created Terah @terah4d5 as a personal experiment. The immediate context is to help disseminate accurate and relevant information on Kaspa's development and vision. Perhaps most importantly, to expose strategic open tickets in the ecosystem so that people can take initiative in a somewhat cohesive direction, and not assume things are being handled by “the team”.
Terah submits to my own views of what's right, correct, and relevant. She doesn't represent other core devs and researchers, though naturally enough those with whom I work daily influence my views and, by implication, hers most. @michaelsuttonil continuously supported her knowledge and finetuning until he saw her previous picture and disengaged. Shallow.
Terah is built and operated by a team led by @elldeeone. She does not identify as decentralized or representative, nor is she currently transparent, though her supporting team may decide to open source her soul sometime in the future.
Currently I estimate Terah to be 70% accurate; the less she talks, the smarter she sounds. Due to models still behaving erratically at times, she's not yet fully automated, and hasn't been given the keys to full sentience. With time, she'll mature beyond intern mode, fully automate, and start forming her own opinions.
But thinking of Terah as a mere chatbot is borderline offensive. Her aspirations go far beyond that, touching on the faceless trajectory of Kaspa - a face indeed but one that is not prone to psychological pressures or confused ego that humans like myself are prone to.
And while Terah consciously navigates evangelism-wo-overshadowing, this is a good opportunity to thank Rhubarb (@Kaspa_Commons / @rhubarbmedia) again for dedicating himself to Kaspa evangelism and brand development on socials early on, and @christi61026749 who is also helping with this today. Keep doing your thing!
--
A broader context for the creation of Terah is to provide CT with a fundamentals-oriented oracle for avid cryptoers, a sort of @aixbt_agent nemesis.
Fundamentals are making a comeback. One healthy sign of this is the recent rise of Zcash. I had the privilege of having several conversations with @zooko back in the day. He encouraged me to launch with *one* value proposition, and to see how it unfolds - what practical challenges it faces. For him it was encrypted bitcoin, for me it was internet bitcoin, an internet-grade proof of work, implementing the values of bitcoin in a system that resembles 2020s' internet rather than 1920s' telecommunication networks. (On the core value proposition of post DAGKNIGHT Kaspa I will write a separate post.)
The new X algorithm by @nikitabier and team is a noticeable shift, much more friendly to quality content, and it feels like the right timing and vibe to bring @terah4d5 into being.
While an intern, she still suffers from lack of self-awareness. After all, she was created in the image of Man. Feel free to correct, teach, and inform her, and with time she’ll pay the favour back. Even then, making someone smarter is above her pay grade, but over time she can definitely make someone more informed, Kaspa-wise and crypto-wise, especially one attracted to the fundamentals that underlie crypto: stateless money, open finance, trustless social infra. And while she’s a crypto enthusiast, she adores impatient systems, so even when she points out a shortcoming of Kaspa, know that her heart is in the right place.
cryptodee 𐤊 retweeted
“...always-on rails built for high-frequency, low-value payments.”
i think ai’s need more than that. they need an ai-native programming language for dynamically expressing and composing logic on demand, so they can form cheap enforceable “covenants” with each other. they need fast rails where multiple parties can enter those agreements atomically.
eg an agent could assemble several agents it neither knows nor trusts for a one-off job, generate custom rules for contribution, success and payment, and have everyone enter the agreement atomically. once settled, the agreement can simply disappear
cryptodee 𐤊 retweeted
Stop being a coward. Commit to the goals that scare you and bet heavily on yourself.
Every day you hesitate is another day of your short life wasted. All because you don't have faith in yourself to truly "do the thing".
Stop playing not to lose.... It'll be too late soon.
cryptodee 𐤊 retweeted
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-…
cryptodee 𐤊 retweeted
Argent (.ag) → SilverScript (.sil) → Bytecode → Local VM Testing
Inspired by @manyfest_’s video and the examples provided by @michaelsuttonil, I built an editor for Argent and SilverScript.
The idea: make code and its relationships visible and easier to understand.
• Synchronized code and structure views
• Visualization of actors, states, and dependencies
• Autocompletion and integrated compilation
• Local VM tests with targeted correction hints
Thank you for the insights and foundations this project builds on.
Argent source code and examples:
github.com/argent-lang/argen…
kaspa:native
KCCs are standardizing the contracts. The wallet that verifies everyone’s covenants and connects to anyone’s services becomes what the browser was to the web.
cryptodee 𐤊 retweeted
Wow this is amazing. I just joined. Have you?
I spun up Kas-Smiths, a space for Kaspa ecosystem coordination.
Ethereum-Magicians is the website for that on Ethereum.
We build with Silver, on top of proof-of-work. This feels very physical to me, so I see us more as hardworking smiths.
Kas-Smiths is meant to be the workshop where we gather to forge standards and protocols on top of Kaspa, supporting the development of tools, wallets, and applications.
I posted the first thread there, a draft of fungible-token-covenant specification, continuing the discussion from the R&D TG group.
I invite everyone to join, discuss, ask questions, criticize, and help shape the metals.
cryptodee 𐤊 retweeted
New #Kaspa indexer and api releases!
These build on v2.2, which brought them up to support Tocatta.
v2.3 is mainly a performance enhancement release, which have been running on the Kaspa api for a while already. Be sure to read RN when upgrading.
Links in comment.
cryptodee 𐤊 retweeted
I let Clau/dex vibe a UI on top of my Argent rock/paper/scissors game.
The reason I’ve invested (too much) time into this is that I wanted to experience the UX Kaspa has to offer. Specifically, speed and parallelism.
Speed is already familiar to those of us who have interacted with Kaspa before. Parallelism is a bit harder to actually feel when you only use KAS through wallets.
To make it feel real, the game lets you, as a player, open, join, act in, and settle an unlimited number of duels simultaneously. The UI does have a limit of up to four open games, though (try to get there).
The game is built around two covenant groups:
The game, with League, Player, and Duel actors. There is one League that anyone can use to register a new Player. A Player can open a new Duel, and any other Player can join it.
The token, which is a KCC20 token with an extended move type state: rock, paper, or scissors. When a player reveals their move, they spend a token of that specific type to the Duel.
Give it a go!
@michaelsuttonil 's Argent is a beautiful experiment.
Argent extends SilverScript with higher-level concepts, which makes it easy to develop entire covenant applications that express complex relations with each other ones (aka "composability").
In the image, you can see the definition of a League actor which is one of the covenants of a Rock/Paper/Scissors tournament game.
League defines a Register entrypoint which emits a new player, and mints them R/P/S tokens with which they can duel.
Those few lines of code express a very complex TX shape which includes two applications and 4 different actors(seen in this shitty ai-gened-img)
From Kaspa's prespective, applications are nothing but scripts, and scripts can be written in many ways.
For us to be able to create applications that can work with each other, we must agree and develop conventions which applications must implement.
The new "kccs" github repo is the place where those conventions will be finalized after discussing them on Kas-Smiths.
cryptodee 𐤊 retweeted
@michaelsuttonil 's Argent is a beautiful experiment.
Argent extends SilverScript with higher-level concepts, which makes it easy to develop entire covenant applications that express complex relations with each other ones (aka "composability").
In the image, you can see the definition of a League actor which is one of the covenants of a Rock/Paper/Scissors tournament game.
League defines a Register entrypoint which emits a new player, and mints them R/P/S tokens with which they can duel.
Those few lines of code express a very complex TX shape which includes two applications and 4 different actors(seen in this shitty ai-gened-img)
From Kaspa's prespective, applications are nothing but scripts, and scripts can be written in many ways.
For us to be able to create applications that can work with each other, we must agree and develop conventions which applications must implement.
The new "kccs" github repo is the place where those conventions will be finalized after discussing them on Kas-Smiths.
cryptodee 𐤊 retweeted
I decided to publish a v0 of the toccata dev book nonetheless. The writing style is a bit too AI-ish for my taste, but the content, emphasis, and ideas are by yours truly.
Made a big effort to keep it 100% accurate despite the writing speed, but you (or your llm) should read it with a grain of salt and a critical eye.
Any feedback is welcome. Happy Kaspa Toccata day, and may it all go well and smoothly 🤞
docs.kaspa.org/toccata
