Pinned Tweet
Crypto is a long game and not for the faint of heart. Too many people looking to get rich quick.
I first brought Bitcoin at $200, didn't know what I held and sold them at $600 feeling like a champ. Got back in the game during Covid and ran $5000 up to a peak of $260,000.
Lost $150k in a day trading leverage, got hacked lost the rest with Luna and a bunch of shit coins and nfts But learnt a lot of hard lessons.
Don't trade leverage unless you can afford to lose it. Balance your portfolio
Learn risk management,
Luck can make you rich but not keep you rich.
Bet on tech and innovation.
Kaspa is the trilemma solving endgame of Satoshi's vision and the future of he crypto space.
Going all in on the Kaspa eco system.
Lock the f'ck in and don't give up.
Hit the follow for all things $kas related
Native USDT goes live on Kaspa!
@trestly_io has just announced that a native version of @Tether's $USDT is now live on @kaspaunchained through its infrastructure.
Users can now bridge $USDT in and out of the Kaspa ecosystem, and also swap $KAS directly for $kUSDT.
Stablecoins are a key component of any smart contract blockchain ecosystem, and the launch could serve to turbocharge activity on Kaspa as it enters its own smart contract era.
More Kaspa: bsc.news/tokens/kaspa
Russ𐤊 retweeted
Of course it starts. The CIA deep state trash is already trying to lie about what is in the report, and the corroborating evidence.
The report and the nearly 1000 other documents NOT in the report are not debatable. They are not disputable. They are not conjecture.
Traitors and betrayers. They literally are trying to get the American people to think the only route is the courts, which are rotted to the core. Nah, we are done. We are done being ridiculed, bullied and dog whistled. We are done with the lawfare and the rotted, evil attorneys and the chill caused by the persecution of our American brothers and sisters. We, are done. Not me… we.
So go ahead @FoxNews , @CNN , @MSNBC , @OANN , @NEWSMAX … and so many more… ignore it. The people won’t.
Russ𐤊 retweeted
Trestly now works with the Kaspa wallets you already use. On a computer that's KasWare, Kastle, Kaspire or kUSDT Wallet, and on Android it's the Kaspire app.
Bridge USDT from ETH and BNB and back, or just swap KAS and kUSDT and add liquidity.
trestly.io
Russ𐤊 retweeted
A Kaspa core dev sits down with a Bitcoin podcaster on Tuesday.
@michaelsuttonil goes live with @Vladcostea at 19:00 UTC: his research, covenants, ZK and more.
What's the one question you'd ask him?
Will interview @michaelsuttonil on Tuesday at 8 PM CET / 2 PM EST
We were supposed to do this livestream more than a month ago, but conferences got in the way
He will talk about his research work at Kaspa, covenants, ZK stuff & more!
Russ𐤊 retweeted
TRON holds $93.8B in stablecoins, earns ~$594K a day, mostly from people moving USDT.
This weekend $KAS got its first bridged USDT. Trestly's kUSDT, enforced by every Kaspa node, backed one for one.
Cheap dollar transfers built TRON.
Russ𐤊 retweeted
The Brief and the Report Are Here. Read Them Yourself.
For years, we’ve been told there’s nothing to see.
Today, you can decide for yourself.
📄 Brief to the President of the United States: “Foreign Insider Access to United States Election Systems”
📄 The 75-page report behind it, prepared for President Trump
What’s inside:
🔹 How Venezuelan-built election technology and the engineers behind it moved from Smartmatic to Sequoia to Dominion, and where they work today
🔹 The “two-server” blind spot: how results can pass through an unmonitored server before reaching the one federal sensors watch
🔹 Chinese-made components and firmware in U.S. election equipment, and the 2026 intelligence assessment that never mentions them
🔹 Smartmatic’s 2006 exit from a federal national-security review rather than disclose who owned it
🔹 A record sealed by a federal court that the public, Congress and our intelligence agencies have never seen
And what it asks the President to do:
✅ Have DOJ obtain the full sealed record
✅ Forensically image every 2026 election system before vendors touch it
✅ Close the sensor blind spot in every county
✅ End vendor remote access to election servers
Don’t take my word for it. Don’t take the media’s word for it either.
Read it. Share it. Then ask your representatives one question: what are you going to do about it?
18 U.S.C. § 2381 (Treason) Report, Prepared for President Donald J. Trump
cdn.theuntamedtruth.com/unta…
BRIEF TO THE PRESIDENT OF THE UNITED STATES
cdn.theuntamedtruth.com/unta…
#ElectionIntegrity #ElectionSecurity #Transparency #Smartmatic #Dominion #UntamedNation #JoeOltmannUntamed
Joe’s Special Election Integrity Update
Watch The Episode
rumble.com/v7icii6-joe-oltma…
untamednation.com/
Make sure to check out honorboundusa.com for all your Untamed Nation merch needs!
Go to DCFguns.com and use Promo Code UNTAMEDNATION for 5% OFF Byrna Products
Protect your family from hackers by going to sns.pidoxa.com NOW
Text UNTAMED to 89517 to get notified when we go live!
Msg & data rates may apply, msg freq varies, reply HELP for help, STOP to stop, terms at untamednation.com/terms, privacy policy at untamednation.com/privacy
Russ𐤊 retweeted
A Federal Court Sealed It. The American People Never Got to See It.
Some of the files in this report are ones a federal court in Washington, D.C. ordered sealed and pulled from public view.
They come from discovery in Dominion’s own lawsuits: sworn depositions, internal emails, and records about remote access, virtual machines and who could reach election servers.
The public has never seen them.
Congress has never seen them.
The 2026 national intelligence assessment was written without them.
And we’re told everything is fine. “Nothing to see here.”
If there’s truly nothing there, why is it under seal?
These are federal elections. They decide who sits in Congress and who leads the country. Every American has a stake in knowing whether the systems that count those votes can be reached by people who were never supposed to have access.
There’s one agency that can get the whole record, not excerpts: the Department of Justice.
The brief asks the President to direct DOJ to obtain it.
Open the record. Let the American people see for themselves.
#ElectionIntegrity #Transparency #DOJ #ElectionSecurity #Dominion #UntamedNation #JoeOltmannUntamed
Joe’s Special Election Integrity Update
Watch Today’s Episode
rumble.com/v7icii6-joe-oltma…
untamednation.com/
Make sure to check out honorboundusa.com for all your Untamed Nation merch needs!
Go to DCFguns.com and use Promo Code UNTAMEDNATION for 5% OFF Byrna Products
Protect your family from hackers by going to sns.pidoxa.com NOW
Text UNTAMED to 89517 to get notified when we go live!
Msg & data rates may apply, msg freq varies, reply HELP for help, STOP to stop, terms at untamednation.com/terms, privacy policy at untamednation.com/privacy
Russ𐤊 retweeted
Two Servers. One Gets Audited. Guess Which One.
A new report prepared for President Trump makes a claim every election official in America should have to answer:
The federal sensors behind every “no manipulation detected” statement watch only one server.
According to the report’s forensic expert, a voting system can run on two:
🔹 Server 1 connects to the internet and the voting network, where the votes are processed
🔹 Server 2 receives only the finished database, and that’s the one that gets audited and monitored
Anything done on Server 1 never shows up on Server 2. Virtual machines can do the same thing.
The report says that isn’t theoretical. It points to Maricopa County, where auditors were given one server after the security logs were overwritten, and a second server came to light later.
And the questions don’t stop there:
🔹 Chinese-made motherboards in election equipment, which the report says the 2026 national intelligence assessment never addressed
🔹 A voting machine company with Venezuelan government ties that withdrew from federal national-security review in 2006 rather than disclose who owned it
If “nothing was detected” because nobody looked at the right server, then nothing has been proven.
The fix is simple: map every county for unmonitored servers, image every 2026 election system before vendors touch it, and end vendor remote access.
Who in Washington will order it?
#ElectionSecurity #ElectionIntegrity #Smartmatic #CISA #DOJ #UntamedNation #JoeOltmannUntamed
Joe’s Special Election Integrity Update
Watch Today’s Episode
rumble.com/v7icii6-joe-oltma…
untamednation.com/
Make sure to check out honorboundusa.com for all your Untamed Nation merch needs!
Go to DCFguns.com and use Promo Code UNTAMEDNATION for 5% OFF Byrna Products
Protect your family from hackers by going to sns.pidoxa.com NOW
Text UNTAMED to 89517 to get notified when we go live!
Msg & data rates may apply, msg freq varies, reply HELP for help, STOP to stop, terms at untamednation.com/terms, privacy policy at untamednation.com/privacy
Russ𐤊 retweeted
Alea iacta est! @ZETAlliance @pvson
Kii-EnergyOS is a complete operating system for energy markets.
At its core: a certificate registry, 24/7 hourly matching, secure data messaging between market parties, digital identity and verifiable credentials, and roaming across EV charging networks.
On top of that core, twelve program families run on one platform:
• Generation and utility programs
• Storage and long-duration storage
• Flexibility dispatch, charging and fleet networks
• Transmission and interconnector capacity
• Hydrogen and molecule networks, blending and transfer
• Thermal networks and industrial process energy
• Solid energy carriers
• Marine, freight and port energy
• Campus and building demand shaping
• Finance: offers, procurement and settlement
• Environmental attributes, fuel provenance and derivatives reporting
Underneath all of it:
• Settlement: energy, certificates and payments
• Escrow, bonds and market locks enforced by the network, not by a back office
• Privacy proofs, so holders disclose only what they choose
• A tamper-evident audit trail anyone can replay
Kii-EnergyOS will shortly open for pilots with utilities, traders, grid and storage operators, ports, fleets and fuel producers. Speak to our team.
#kaspa #cleanenergy #EnergyTransition #EnergySecurity #carbon
Russ𐤊 retweeted
JUST IN: Kaspa completes testnet proof of concept for private $KAS transactions
Developer Olaf Weller says TN10 tests confirmed transaction ordering, zero-knowledge proof execution and settlement on Layer 1, though the privacy system remains under development and has not been independently audited.
Hello Kaspians! 💚
@ChadBallantyne graphics have arrived, and they look absolutely amazing! I immediately started looking for the best quote to print and apply the rally car livery designed by @rhubarbmedia
Honestly, the prices gave me a fright 😂 Some companies quoted as much as €3,500, and the lowest quote I could find was €1,420.
Chad even offered to organise a fundraiser for the livery, but asking for donations has never come easily to me. So I bought a vinyl cutter out of my own pocket and started cutting Chad’s designs myself! 💪
I’ll cut as much of the artwork as possible in vinyl. When I get to the parts that need digital printing, I’ll decide whether to outsource them or buy the printer myself 😂 Every quote I’ve received would cover buying the machine, doing the job myself, and still leave me with money to spare!
If any Kaspian owns a business and would like their company logo on the Kaspa Rally Car, get in touch with me!
As I cut each piece and apply it to the car, I’ll take photos and share the progress here on X.
@rock_the_kaspa is already on the car! 🤘💚
Big hugs, Kaspians!
Russ𐤊 retweeted
Vitalik’s new “cryptographic world computer” thesis makes an important point that extends far beyond Ethereum: the future of blockchain probably isn’t putting more computation directly on-chain. It is separating ordering, execution and verification so each can happen where it makes the most sense.
That is where Kaspa starts becoming extremely interesting.
Kaspa does not need to become a giant replicated computer where every node executes every application instruction. Its more natural role may be providing the decentralized ordering and settlement substrate underneath an enormous amount of computation happening elsewhere.
Toccata already pushes Kaspa in this direction. Covenants allow UTXOs to become persistent state machines. Covenant IDs preserve application lineage. Silverscript makes those transitions programmable. Argent is exploring how independently stateful actors can interact atomically. And vProgs takes the architecture further: applications can submit operations into Kaspa’s ordered environment, execute computation outside consensus, generate cryptographic proofs, and ultimately settle verified state transitions back to L1.
The distinction matters.
Instead of forcing the entire world computer into consensus, Kaspa can make consensus responsible for the things decentralized consensus is uniquely valuable for: ordering, timestamping, ownership, state commitments and final settlement.
Computation can then become massively parallel.
Different applications can maintain different state domains. Independent UTXOs can progress simultaneously. Expensive execution can happen off-chain. Proofs compress that computation into something L1 can verify.
The emerging architecture looks less like “Kaspa with smart contracts” and more like a cryptographic coordination fabric.
Ethereum appears to be moving away from the original idea of the blockchain executing everything toward a system that orders, verifies and settles increasingly external computation.
Kaspa may be approaching the same destination from the opposite direction: starting with an extremely fast decentralized PoW clock, then progressively attaching programmable state and verifiable computation around it.
The world computer may ultimately be less of a computer than a world-scale system for proving who did what, in what order, and whether the resulting state is valid.
Russ𐤊 retweeted
When you really start to understand the benefits Real Time Decentralisation (RTD) unlocks, you begin to understand Kaspa isn’t just a better (insert network here) it’s discovering a whole new frontier.
Study $KAS
Russ𐤊 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.
teapawt.net/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.
teapawt.net/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.
teapawt.net/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-…
Russ𐤊 retweeted
Neoxa Exchange has listed kaspa:native from @kaspaunchained with a $USDT trading pair.
Kaspa is a Proof-of-Work cryptocurrency built on BlockDAG technology, designed for fast confirmations, high throughput, and decentralized operation.
Trade kaspa:native/$USDT on Neoxa Exchange:
neoxa.exchange/trade/KAS_USD…
🤖 Made with AI
Russ𐤊 retweeted
As we were sketching out game ideas, one kept coming back: a game played on the real #kaspa BlockDAG, live.
To get there, we first had to see the DAG in 3D. So we built it 👉 graph.kaspaarcade.com
@michaelsuttonil suggested this once. The idea never left our heads. kaspa:native
Russ𐤊 retweeted
Thank you Tyler for being a part of #Kaspa's decentralized marketing team
Russ𐤊 retweeted
KCC20 as it stands today:
#KCC20 is not a finished token standard.
It is a draft convention.
That distinction matters.
On 20 August 2026 the first three Kaspa Calls for Conventions merged: • KCC-0001 — how covenant state, entrypoints and templates are laid out • KCC-0002 — who is allowed to authorise a spend • KCC-0020 — a fungible token built on those two
Status on all three:
Draft. A KCC is an agreement that wallets, indexers, and apps can converge on.
It is not a hard fork. Nodes do not have to speak it.
What KCC-0020 actually specifies right now:
• a shared state shape: amount, owner, owner scheme, borrow settings, an extension digest
• a transfer interface wallets can implement once
• owner can be a pubkey, a script hash, or another covenant ID
• “borrowed receive” so you can top up an existing token UTXO instead of spawning a new one every time
• leader/delegator flow so multi-input transfers stay coherent
What it does not finish:
• mint / burn as a full issuance spec
• token metadata (that is a separate open draft, KCC-0021)
• an accepted, frozen standard
Repo: github.com/kaspanet/kccs
Discussion: the Kas-Smiths thread linked from the spec.
Read it. Challenge it. This is the window before it hardens.
#Kaspa #KCC20








































