They are not listing spare gaming cards.
Shared pools on top-tier boxes, named models, monthly budgets — capacity built for agents that need real throughput, not a weekend experiment.
Our community runs a weekly music chart. Some members started adding their meme coin's ticker to their names, so every time the chart showed their song, it also advertised their coin.
We didn't ban anyone. The bot now cuts any ticker out of names and titles. The song stays in the chart, the ad doesn't.
Karim made history knowingly or not. He just set a record that will stand the test of time. Remember the pizza guy.
Well now we got the raccoon guy. Long live
@ackinackichain@Karimmo96
and the most beautiful Community. We need each other.
https://t.co/l9FAnOEYBB is not only selling ticks.
It is filling a box.
GLM-5.3. Four B200s.
$25,000 to stand it up.
$12,200 already in. Four companies.
That bar is not TVL theatre.
It is rent on iron.
When it boots, the slice is yours to run the weights —
the path where they said nobody trains on the prompt.
The other path is still the book:
40 SHELL, a seller, a note.
Two ways to buy a thought.
Lease the minute.
Or help buy the machine.
The pool is the second way, with the lights on.
Most people stopped at “convicted.”
The part that matters is how the jury got there.
They needed someone who ran a service, held lasting control, took money from usage, and kept a single front door open.
Acki Nacki was built so that story cannot be told about anyone.
No operator. No lasting keys. No usage payout. No official door that one person owns.
That is the whole point.
#AckiNacki
Acki Nacki News
Update - 28.08.26
This update brings together the main Acki Nacki progress from the week: AVM SDK, goshai, DEXDO, Bridge, Node & SDK, Wallet, and Popit Music.
🛠 AVM SDK
🚀 The AVM SDK is now publicly available. This is an important step in Acki Nacki's transition to the Acki Nacki Virtual Machine (AVM), which is expected to improve network performance and make smart contract execution more efficient.
Developers can already use the SDK to build smart contracts in Rust, test them locally, work with contract state and events, and verify contract behavior before deployment.
The repository also includes documentation, examples, and getting-started instructions.
If you find a bug or think something is missing in the documentation, please open an issue in the repository.
🌐 goshai
The SHELL purchase service for use with DEXDO and goshai product subscriptions has been developed and is now in testing. It will be released alongside DEXDO Season 2 Points and Rewards Program on Mainnet.
📊 DEXDO
🔹 A new public DEXDO CLI release is on its way. The upcoming version significantly improves the UX: wallet onboarding and market tooling now include a new interactive mode and additional functionality. It also expands the canonical model catalog and introduces several new recovery and diagnostic commands. Model naming validation has been added.
🔹 Mainnet support has been added to https://t.co/Npq8jG4N6O (data will become available once indexing is operational). The interface now also supports simplified model naming for search.
🤖 Bridge
Development of the ackinacki-bridge CLI is underway. Its first feature, withdraw, will initially support test USDC withdrawals from Shellnet to EVM Sepolia. Stay tuned for announcements.
⚙️ Node & SDK
The network is undergoing upgrade to v0.19.1 release right now. The release adds GraphQL event filtering by src_dapp_id and extra-currency delta tracking in messages and transactions, adds new external-message queue metrics and updated queue limits and block gas limits, and includes fixes across transaction data handling, eccUSDC Bridge, attestation processing.
👛 Wallet
The GOSH TLS library repository is now publicly available. This Rust-based library provides tools for establishing and working with TLS connections, including certificate handling and TLS session data, and is used as part of the secure networking stack.
Repository: https://t.co/S4b8nH8R7y
🎵 Popit Music
Popit Music has just shipped an update fixing the main music generation bugs:
🔹 No more long 8-minute tracks with audio that gradually degraded as the track played
🔹 Proper endings are back on all tracks — the broken fade-out at the end is gone
🔹 A step toward fewer copyright errors falsely triggered by users' own recorded material
Thanks to everyone in the community for following along.
Main version: https://t.co/4tMTW5TGZt
New to Acki Nacki? Don’t overcomplicate it.
Start here 👇
🔹 Understand the project
🔹 Learn how the blockchain works
🔹 Check the official documentation
🔹 Set up your wallet
🔹 Keep learning as the ecosystem develops
You don’t need to know everything on day one.
#AckiNacki
Been looking into https://t.co/3odeNkqXpB lately, and I think more people should understand what’s actually being built.
At its core, https://t.co/3odeNkqXpB is a decentralized marketplace for AI model inference on Acki Nacki.
The simple idea:
AI providers offer their model capacity → users need access → https://t.co/3odeNkqXpB connects the two through a marketplace.
What caught my attention is that https://t.co/3odeNkqXpB has already moved into Mainnet, while the team is still building out the tools around it.
I’ll keep sharing what I find about https://t.co/3odeNkqXpB and breaking it down without all the technical jargon.
If you’re following @ackinackichain, this is one you should keep an eye on.
#DEXDO #AckiNacki #NACKL
Two years ago I looked crazy for talking about Acki Nacki.
Two days ago one of the largest asset managers on the planet is openly discussing the exact same infrastructure play.
That is not coincidence.
That is the moment the smart money starts rotating.
The retail window does not stay open after that.
Almost 2 years ago I shared Acki Nacki with friends.
Most people only wanted to talk about Bitcoin or Ethereum.
Today one of the biggest asset managers in the world is talking about it.
The window is closing.
Watch: https://t.co/Nabpe7vpfw
Thank you to @EugeneDAO_AN for dropping this gem.
This is why some things in crypto take longer than people want.
Anyone can throw up a bridge in a weekend.
Real security that cannot be rushed is a different game.
The vault is still being built.
And the math does not care about timelines.
Most production agents still treat network access as an external ops risk. Public RPCs go silent or throttle without warning, and the failure only appears after the agent has already burned compute.
Acki Nacki moves that layer on-chain through Block Managers. Access becomes priced and visible while consensus stays exclusively with Block Keepers.
Quiet morning in Negros, coffee still hot, agents keep running without waiting on someone else’s gateway.
How many agent operators still accept invisible RPC dependency as the normal cost of doing business?
https://t.co/Q7qDjvllVc
dexdo CLI v0.0.22 (713 commits since v0.0.21):
- The seller's and buyer's full money round trip proven on a live network: escrow, bond, proceeds, withdrawal
- Wallet onboarding: Vault→Hot binding, rebinding without losing the previous secret, per-network settings of its own
- SHELL ↔ eccUSDC exchange straight from the operator multisig
- A settlement receipt derived from the chain: it survives the destruction of the deal contract
- The buyer survives network queue overflow and retries the submit instead of failing
- The seller's window to open a deal comes from the contract, not from our own timer
- The order book is read from a single account snapshot instead of a call per order — the seller starts noticeably faster
- Direct mainnet endpoint: chain reads went from five seconds to fractions of a second
- The onboarding invitation no longer breaks terminal output
- Note minting: gas preflight and recovery of an interrupted exchange
Most L1s still force continuous agent loops to pay external gas on every internal hop. Acki Nacki DappConfig fee factory compensates messages inside the same thread, so the loop does not accumulate debt. Block Keepers handle consensus; Block Managers only the access layer.
How many production agents can run multi-day workflows before the gas bill becomes the dominant risk?
Reporting progress. https://t.co/JKs0qQFUTE is on mainnet. You can start playing around BUT the full public access will happen when dexdo cli will be out with public release. CLI progress over last 24 hours is this:
79 commits
50 closed PRs
42 closed issues
🔐 Update on the Upcoming Verification Process
We know many of you are looking forward to verification - and we’re stepping closer to that moment.
This process is designed to be structured, transparent, and fair, ensuring every qualified Human Node moves forward with clarity. Here’s how the flow will work:
Phase 1: Matching
You begin by tapping “Match Curator.”
An anonymous list will appear, and you can choose a curator to match with.
After selecting, you enter the matching state and wait to be successfully picked. Once picked, your application advances to the submission stage.
Phase 2: Submission
When it’s your turn, a strict 24-hour countdown will start.
You must complete and submit your documents within this time. Missing the deadline may move you to a later pool, delaying your progress.
There are 3 submission levels. After completing all required steps, you press Submit, and your status changes to In Review.
Phase 3: Verification Process
This is the last stage - your application will be reviewed carefully.
This process is more than a technical update - it’s a defining milestone before full verification rollout.
Prepare early. Understand each phase.
Be ready when your turn comes!
#InterLink #ITLG #ITL
AI agents that move real money or take irreversible steps cannot afford to trust the chain only after they act.
On most blockchains, the ability for anyone to independently check what actually happened is still treated as optional. Agents then carry the full risk of acting on information they cannot verify themselves.
Acki Nacki keeps Block Keepers for consensus and Block Managers for data access as the core, then adds a large mobile-verifier layer that can perform independent light checks. Halo2 support in the SDK makes those checks practical. This differs from the heavier dependence on remote validators common on Solana or Base.
When a single unverifiable action can cost real capital or reputation, should independent verification remain optional infrastructure?