iotaAI: the AI engine supercharging your IOTA workflow.

We are proud to be validators of the IOTA network and genuinely excited to be part of its rapidly growing ecosystem. For us, this is not just a technical role — it is active participation in building a reliable and user-friendly infrastructure that developers and everyone building on IOTA can rely on.

We are happy to help other community members make working with the network simpler, faster, and more efficient. With this goal in mind, we developed the Grafana dashboard for IOTA validators — a convenient monitoring tool already actively used by teams like Tokenalbs, Allnodes, and others. We don’t just share the solution; we also provide support by assisting with installation and setup, so anyone can easily connect and start using it within their infrastructure.

We see how quickly AI is evolving and believe it can significantly simplify the lives of validators and developers on the IOTA network. That’s why we have started working on iotaAI — from data retrieval to node status analysis and understanding what’s happening in the network.

🤩 AI assistent

Not sure how to set up a node? Have a technical question related to the IOTA blockchain? Just ask iotaAI — it will not only give you a clear, helpful answer but also suggest useful resources right away.

To ensure the assistant provides accurate and relevant answers, we train it using data from key community resources (Docs, Forum, Github, Discord (community & builders))

Example of iotaAI response based on trained data from the official IOTA website

🔍 Prompt: What is IOTA and how is it different from other blockchains?

Response:

IOTA is a decentralized, feeless distributed ledger designed for the digital economy and the Internet of Things. Instead of using a traditional blockchain, it relies on the Tangle — a fast, scalable directed acyclic graph (DAG) where each new transaction confirms two previous ones. This makes IOTA lightweight, efficient, and ideal for microtransactions, smart cities, supply chains, and Web3 applications.

For official updates and community news, follow IOTA on:

🔗 Link: https://www.iota.org/

Documentations

iotaAI is trained based on the official IOTA documentation, including technical guides, architecture descriptions, validator specifications, and tokenomics sections.

This enables the assistant to provide accurate and structured answers, guiding users to relevant materials and sections of the documentation.

🔍 Prompt: How is validator consensus and voting power structured in the IOTA network?

Response:

In the IOTA network, the total voting power is fixed at 10,000, regardless of how much IOTA is staked overall. To reach consensus, a quorum of 6,667 voting power is needed.
Each validator's voting power is proportional to the amount of IOTA staked in their pool, but with one important rule: no individual validator can control more than 1,000 voting power (10%). If a validator’s stake exceeds 10% of the total, their voting power is capped at 1,000, and the excess stake contributes to distributing voting power among the other validators. This mechanism ensures decentralization and prevents any single validator from dominating the network consensus.

Learn more in the official IOTA Consensus documentation.

🔗 Link: https://docs.iota.org/operator/validator-node/validator-tokenomics

🔍 Prompt: What are formal snapshots in the IOTA network, and how do they differ from database snapshots?

Response:

Formal snapshots in IOTA are minimal, protocol-native snapshots that include only the essential state needed to restore a node at the start of an epoch. Unlike RocksDB snapshots, they’re database-agnostic, smaller in size, and faster to restore. Their contents are cryptographically verified against the committee’s epoch commitment during restoration.

They’re ideal for validators and state-sync nodes but not suitable for nodes requiring historical data (e.g., RPC nodes).

📦 Restore from a formal snapshot (mainnet):

iota-tool download-formal-snapshot \
  --latest \
  --genesis "<PATH-TO-GENESIS-BLOB>" \
  --network mainnet \
  --path <PATH-TO-NODE-DB> \
  --num-parallel-downloads 50 \
  --verify normal \
  --no-sign-request \
  --verbose

🔗 Link: https://docs.iota.org/operator/full-node/configs/snapshots

🔍 Prompt: How can I check if my node is running properly based on the last processed checkpoint?

Response:

To ensure your node runs properly, verify that the last processed checkpoint is recent. Ideally, the difference between the current time and the checkpoint timestamp should be under 1 minute — typically around 10 seconds, and up to 30 seconds is acceptable.

🔍 Check via Metrics

ts=$(curl -s localhost:9184/metrics | grep ^last_executed_checkpoint_timestamp_ms | awk '{print $2}')
(( $(date +%s%3N) - ts < 60000 )) && echo "✅ OK" || echo "❌ Too old"

🧪 Check via JSON-RPC

curl -s -X POST localhost:9000 -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"iota_getLatestCheckpointSequenceNumber","params":[]}' | jq .result

Compare with IOTA Explorer > Custom RPC URL.

📦 Check via Dolphin CLI

You can also use the Dolphin CLI tool for high-level node health checks. It uses Prometheus metrics under the hood:

dolphin scan

More info: https://gitlab.com/blockscope-net/dolphin-v2.

ℹ️ Metrics are available at http://localhost:9184/metrics. For dashboards, see the STAKEME Grafana templates or official IOTA dashboards.

🔗 Link: https://docs.iota.org/operator/full-node/monitoring

Discord

Real conversations and solutions come from validators, developers, and the team. Most of the important information is specifically found on Discord. A nice added benefit is that the bot learns in real-time, so it’s not necessary to go into Discord to check the latest news — you can get updates directly from iotaAI.

Examples of queries:

🔍 Prompt: How is staking reward calculated if I unstake some amount before the end of an epoch? For example, if I unstake 1 hour before the epoch ends, do I receive a proportional reward (like 23/24 of the full reward) or do I lose all rewards for that epoch?

Response:

Staking rewards in IOTA are calculated based on the amount staked during the entire epoch. If you unstake part or all of your stake before the epoch ends, your reward will be proportional to the time your tokens were staked during that epoch. For example, unstaking 1 hour before the end of a 24-hour epoch means you should receive roughly 23/24 of the full potential reward, rather than losing it entirely. However, specifics can vary depending on the validator or platform, so it’s recommended to check their staking rules.
More info: https://docs.iota.org/about-iota/tokenomics/staking-unstaking

🔍 Prompt: How safe is it to host an IOTA node on a cloud server provider? Is there a risk that a cloud admin could access my node and steal funds?

Response:

“Hosting an IOTA node on a cloud server is generally safe because nodes don’t store private keys or funds. However, if you keep wallets or private keys on the same server, there is a risk that a cloud admin with access could compromise them. To stay safe, it’s best to keep private keys offline or use hardware wallets, and separate wallet management from your node hosting.”

The STAKEME team is focused on building accessible and user-friendly infrastructure tools for the IOTA community and developers.

Our work on AI and monitoring tools is designed to make interacting with the IOTA network faster, more reliable, and developer-friendly.

We’re grateful to the IOTA Foundation and community for the inspiring collaboration and the opportunity to push web3 infrastructure forward — together.

STAKEME Developments

Updated on