@H_Que_
Account based inIndonesia
About this account
- Account based in
- Indonesia
- Connected via
- Indonesia Android App
Account-level information from X, not a live location or the device used for a specific post.
When there is nothing to do. Do Nothing,- When there is something to do, give it your 100%💯
Joined February 2018
- Tweets1.2K
- Following1K
- Followers233
- Likes48.3K
H_Que retweeted
We've been silently cooking on Kaskad, and after delivering our lending on @Igra_Labs, we're now ready to expand our services to additional chains. Both EVM and POW 👀.
The KSKD token will stay at the center of them all, sharing the same existing supply, utility and tokenomic across all supported networks.
First stop: Robinhood chain. Ongoing work: Kaspa L1 (thanks to all the Kaspa Core taking the time to discuss and guide us).
Igra mainnet will of course remain as we have plans to scale there as well.
We were always meant to be multichain, and we will always keep building on the Kaspa Ecosystem.
Onward!
Hey $KAS !
This week KaChat 4.1 is set to go live on iOS, Android, and..... DESKTOP!
In fact RIGHT NOW you can start playing around with the desktop version. Please keep in mind there will be bugs. But its time to start getting feedback and consistently working on the desktop version to make it the best!
Start trying desktop here - kachat.app/desktop/
As always KaChat does not need your life savings to be able to use it. Its considered a hot wallet. You only need around 50 Kaspa which will be enough to experience all the features the app provides.
H_Que 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-…
H_Que retweeted
We've recently moved @WolfysBar business accounts to @Revolut and we would very much like to use $KAS at our restaurants worldwide instead of stablecoins
33% of each restaurants crypto profits are fed back into the ecosystem so can you imagine the sheer volumes you guys would get if you simply added support for $KAS
Kii will be at the 16th @DiiDesertEnergy Leadership Summit in Istanbul, 29 Sept – 1 Oct.
This is not a crypto event. It is the annual gathering of the companies actually building EU–MENA clean energy systems and markets.
Look at their Clean Energy Pyramid. @pvson
One of the structural layers is Trusted Information: security and optimality through trusted data, AI, blockchain and cyber security.
That is the layer Kaspa was built to carry. Energy markets need an information and settlement substrate that is:
• fast enough for trade
• neutral enough for counterparties who do not trust each other
• cheap enough to attach certificates, attributes and provenance to every electron and molecule
• secured by proof of work, not a validator committee
Last year we introduced Kaspa’s BlockDAG to this network. This year the conversation is trusted trade: registries, certificates, settlement and auditability that can travel across borders without a central operator.
Kaspa as the information carrier for clean energy markets.#Kaspa #Kii
H_Que retweeted
@OriNewman and @IzioDev’s first token mechanism took thousands of lines of raw opcodes. They can now write the same thing in 60 readable lines of Silverscript.
Silverscript v1 is out. Congrats sir, and thanks to everyone who helped get it here.
Finally, Silverscript v1 is out [Link in the reply]. This completes the journey we started eight months ago with Toccata — it's finally possible to write human- (and AI-) readable smart contracts on Kaspa.
This language started simply as "CashScript with loops", but eventually grew into a full-fledged smart contract language capable of expressing complex, stateful contracts. It's always fun to look back at the first token mechanism @IzioDev and I worked on using raw opcodes, which took thousands of lines of code, and see the same thing implemented in just 60 easy-to-read lines of Silverscript.
I'm excited to explore the possibilities of UTXO programmability together with the Kaspa community, and this is only the beginning - Silverscript will evolve, Argent will add higher layers of abstractions, and I'm sure more people will find their own way of extending this new ecosystem.
H_Que retweeted
Finally, Silverscript v1 is out [Link in the reply]. This completes the journey we started eight months ago with Toccata — it's finally possible to write human- (and AI-) readable smart contracts on Kaspa.
This language started simply as "CashScript with loops", but eventually grew into a full-fledged smart contract language capable of expressing complex, stateful contracts. It's always fun to look back at the first token mechanism @IzioDev and I worked on using raw opcodes, which took thousands of lines of code, and see the same thing implemented in just 60 easy-to-read lines of Silverscript.
I'm excited to explore the possibilities of UTXO programmability together with the Kaspa community, and this is only the beginning - Silverscript will evolve, Argent will add higher layers of abstractions, and I'm sure more people will find their own way of extending this new ecosystem.
H_Que retweeted
After endless audits, reviews and refinement cycles, it’s finally here, ladies and gentlemen: silverscript 🩶📜
Finally, Silverscript v1 is out [Link in the reply]. This completes the journey we started eight months ago with Toccata — it's finally possible to write human- (and AI-) readable smart contracts on Kaspa.
This language started simply as "CashScript with loops", but eventually grew into a full-fledged smart contract language capable of expressing complex, stateful contracts. It's always fun to look back at the first token mechanism @IzioDev and I worked on using raw opcodes, which took thousands of lines of code, and see the same thing implemented in just 60 easy-to-read lines of Silverscript.
I'm excited to explore the possibilities of UTXO programmability together with the Kaspa community, and this is only the beginning - Silverscript will evolve, Argent will add higher layers of abstractions, and I'm sure more people will find their own way of extending this new ecosystem.
H_Que retweeted
📊 UPDATE: Onchain spot RWA trading volume hit a record $7.82B in August, per CryptoRank.
I am proud to be one of the 3 people who use $KAS 💪🍻
H_Que retweeted
Crypto markets are seeing massive inflows:
The largest crypto ETF, $IBIT, has attracted +$3.7 billion in inflows so far this quarter, putting it on track for its largest quarterly intake since Q3 2025.
So far in September, $IBIT has posted +$459.8 million in inflows, following +$3.0 billion in August, its largest monthly inflow since October 2025.
As a result, the fund’s assets under management (AUM) are up to $62.6 billion, near their highest level since mid-May.
Since the start of July, $IBIT’s AUM has risen +$19.6 billion, or +46%.
The rotation back into crypto is accelerating.
H_Que retweeted
We are expecting good attendance by leaders and experts from all over the world on desert based clean energy systems, markets and related trusted information, a.o. distributed BlockDAG technology @ZETAlliance @KaspaKii @IRENA @IEA
🌟 #DiiLeadershipSummit26 - 1 month to go!🎟️
Join us to accelerate action & foster bold dialogue around the key enablers of the energy transformation, from energy storage & data security to geopolitical developments & international cooperation.
▶️ diisummit.org
@pvson
H_Que retweeted
Kaspa builders are already pushing x402 further than many people realize.
Real KAS payments on mainnet. MCP tooling. x402 v2. A facilitator. Payment channels. Even work toward standardization.
So the question isn’t “who will build x402 on Kaspa?”
It’s:
What still separates what exists today from something @CloudflareDev could realistically benchmark, integrate and support?
Stablecoin liquidity?
CAIP-2 registration?
Auditing?
Production infrastructure?
SDK integration?
Kaspa’s architecture makes machine-to-machine payments interesting.
But architecture isn’t enough.
The next step is proving the advantage with code, benchmarks and real usage.
Builders already working on this: what is the biggest missing piece?
github.com/elldeeone/kaspa-x…
github.com/kaspahttp402/kasp…
github.com/Kali123411/k402
H_Que retweeted
Money scales in layers they say. My word please stop using layers for your money. Lightning is not Bitcoin. Liquid is not Bitcoin. Fedimints is not Bitcoin.
We are aware of a security incident on @Liquid_BTC. Purported white-hat hackers have withdrawn ~4,000 BTC (~$320 million) from the Liquid Federation wallet. The @Blockstream team is working on contacting them on-chain with a signed message.
What we know so far is that the funds were withdrawn via the SideSwap PAK (Peg-out Authorization Key), but that key was not compromised, nor were any others.
Exchanges have been notified and have already paused (or will pause) LBTC deposits and withdrawals. Other Liquid assets such as USDT, DePix, and RWAs are unaffected by this security incident.
Bridge nodes have been temporarily disabled, so no new transactions can be submitted to the network. Effectively, the Liquid sidechain is paused until this issue is resolved.
Liquid wallets will be impacted, and we're sorry for any inconvenience. Federation members are actively working on resolving this so we can restore normal network activity.
You can monitor the situation via @mempool's liquid.network site below:
mempool.space/address/bc1qdl…
