In Noidium v2 you now get a complete analysis of all your trades of a particular token.
This is my PCAT trade.
You access it from the "Mine" tab.
https://t.co/H6jlYqjlbw
@Zelusfin Did you know you have a lot of information about NOID on @noidium https://t.co/rTfyGrP6So?
Our charts are the best and dedicated to the NOID community.
A game of thrones is playing out on Parano1d.
At 07:09 UTC, one wallet sold 6,107 NOID worth of NEMO in a single block. That took 66% off the biggest token on the chain in seconds.
Within 18 minutes, 13 different wallets had bought it back from 0.041 to 0.105. A few hours later it was above where it started.
Every trade is on chain. Watch it live on https://t.co/jz792Buc66
Agreed, and we say so in the README: it's not a sandbox. Anything on the machine that can reach the node's RPC already has its powers.
So the isolation is layered: loopback-only RPC, read-only by default, sending needs a separate wallet mode with a per-call cap + exact confirmation, and the server holds no keys.
Our advice: keep only a small hot balance in the node wallet you give an agent. Main funds stay elsewhere.
AI agents are starting to pick where they trade. We want them to pick Parano1d. 🤖
Today: parano1d-mcp is on https://t.co/rxoVfN9JZ5 🦀
cargo install parano1d-mcp
It gives any AI agent (Claude, Cursor, your own bot…) direct access to your own Parano1d node over MCP: all 79 RPC methods, read-only by default. Sending is off unless you turn it on, with hard caps, and your node's wallet signs. The agent never sees a key.
Why we think this matters:
→ agents choose tools they can actually use, not chains they read about
→ a full Parano1d node runs on 1 CPU and 1 GB RAM, and verifies the chain from a proof, not by replaying history. An agent can check everything itself, on almost nothing
→ next: listing on the official MCP Registry, so agents find it on their own
What else should we build so agents choose Parano1d? Drop your ideas 👇
Post-mortem: https://t.co/c8pEEJz1KC paused for ~1 hour today 🧵
What happened
At 04:08 UTC, block 285,095 carried a perfectly valid token transaction we had never seen before: a wallet sent its PARANOID tokens back to itself (reorganising its own coins).
Our indexer, which turns raw blocks into the charts, trades and balances you see, is built to stop rather than guess when it meets something unfamiliar. So it stopped, and https://t.co/OnoNbdHkct's data froze at block 285,094.
What was NOT affected
• The Parano1d chain kept running
• Your funds and wallets were never at risk
• No data was lost: every block was safely captured by our 3 archives (Frankfurt, Ashburn, São Paulo)
The fix
We taught the indexer this shape, built it from the exact code already running, and deployed it. At 05:07 UTC it caught up all missed blocks in seconds.
So it doesn't happen again
1. Auditing every "stop" in the indexer against Parano1d's consensus rules, so every valid transaction shape is handled
2. Generating every valid shape on our testnet as permanent tests
3. Fail-safe mode: an unknown transaction will no longer freeze the site; it gets flagged and the rest keeps flowing
4. An alarm that calls us the moment the site falls behind the chain
5. A new build machine: the next fix ships in minutes, not an hour
Thanks for your patience 🫡
Shipped today on https://t.co/OnoNbdHkct 🚢
💲 Market cap in $ right next to every token's price, and NOID's own market cap in the top bar
📈 Live SafeTrade NOID/USDT trades + order book, inside Noidium (clearly marked off-chain)
🤝 Creator-friendly labels: wordplay names are never flagged; only exact look-alikes get a neutral "Not the NOID coin" note
🔐 Noidium wallet 0.5.8 on the Chrome Web Store: tighter message permissions, checked by an independent review
🤖 parano1d-mcp on https://t.co/akVO9su98s + the official MCP Registry: AI agents can now read Parano1d through your own node
You asked, we built. What's next? 👇
Neither 🙂 it holds no keys and routes nothing. It runs on your machine next to your own Parano1d node and only talks to that node.
Read-only by default. If you turn on wallet mode, the agent can ask your node's own wallet to send, with hard caps per call and an exact confirmation. Keys never leave the node, and nothing goes through us.
We ship to Noidium every day 🛠️
To make sure you're on the latest build, refresh https://t.co/OnoNbdHS21 and check the bottom right:
Noidium · mainnet-20261105-1540 · defce82
That's the release date and time (UTC) and the exact code commit it was built from. Same tag on our end, so if you ever report a bug, include it and we'll know exactly what you saw.