Rotilho

u/Rotilho


r/atto•

We’re making a small change to how staking rewards are calculated.

Currently, staking rewards can stop for two reasons:

  1. The voter has not voted in the last 24 hours.
  2. The delegating account has been inactive for 30 days or more.

The 30-day inactivity rule was originally introduced to encourage people to regularly review and maintain their voter choice.

However, there is an unintended side effect: when a delegating account becomes inactive, its stake also stops contributing to the voter operator’s reward, even though the operator is still running and maintaining their node correctly.

After discussing this with Jestag, we agreed that this isn’t particularly fair to voter operator

10

r/atto•

The Atto integration has been reviewed and verified by n8n and is now listed in their integration directory.

You can use Atto directly inside n8n workflows to:

  • Monitor accounts, balances, receivables, and transactions
  • Send instant, feeless payments
  • Trigger workflows from activity on the Atto network
  • Build payment alerts, automated payouts, account monitoring, and more
  • Combine Atto with n8n's huge ecosystem of apps and AI tooling

This makes it much easier to plug Atto into existing automation and agent workflows without having to build the integration layer yourself.

👉 https://n8n.io/integrations/atto/

Would love to see what people build wit

20

r/atto•

Node 1.37 is a fairly substantial performance release.

The biggest change is that several parts of the node no longer poll continuously for work. Election persistence, transaction/vote prioritization, vote persistence, vote timestamp recording, and stale-vote cleanup now use demand-driven workers that wake only when there is something to process.

On one of our production nodes, steady CPU usage dropped from around 0.3 cores to 0.03 cores, roughly a 10× reduction.

We also observed confirmation times improve by nearly 80 ms.

Other changes include:

  • Final vote signatures are cached when elections start, removing signing latency from the final confirmation path.
  • Stale vote cl
10

r/atto•

I built Atto to work as everyday money. Fast, no network transaction fees, something that could feel like handing over cash with the convenience of paying by card.

Once the foundation was ready, we could finally focus on micropayments, but not in the way I’d anticipated.

What I wanted was simple: read one article without subscribing to a newspaper. Use a tool once without buying a month of access. I wrote about the subscription trap because I’m tired of choosing between another recurring bill and ads that follow me around.

The problem? Nobody cares (enough).

People already have a way to pay. They might dislike parts of

40

r/atto•

Atto now has a command-line wallet for macOS, Linux and Windows. You can create or import a wallet, send feeless payments, check balances and history, and keep automatic receiving running in a terminal.

You can also name addresses, so a payment can look like this:

atto send --to-label "Savings" --amount 1

“Savings” isn’t a network-wide username: labels are saved locally in your wallet profile.

For scripting, --json provides structured output. Payments have request IDs that let you check or retry the same payment after an interruption. Keep the original ID—running a send again without it creates a new payment.

Getting started

Requires the latest Node.js 24.x release:

10

r/atto•

You can now check balances, follow payments and send ATTO from an MCP-compatible AI assistant. Atto MCP is available in beta as \@attocash/mcp` .

It connects your assistant to a local Atto wallet. You can create a dedicated wallet for it or share an existing Atto CLI wallet.

What it can do

  • Show balances, pending payments and transaction history.
  • Give addresses personal names, then use those names for payments.
  • Watch for incoming payments while the MCP session is connected.
  • Send feeless ATTO payments within locally approved spending limits.
  • Show spending usage and the remaining allowance.

For example, after labelling a destination and approving spending access:

Access

24

r/atto•

Atto node v1.35 is out, with changes to keep elections and transaction processing moving when representative weights change, database writes fail temporarily, or peers send more work than a node can handle. The main changes:

  • Elections now calculate vote totals using current representative weights rather than weights captured when votes arrived.
  • Failed writes of confirmed election results keep retrying with backoff instead of stopping after a fixed number of attempts. Results stay queued within the running process.
  • Recoverable transaction rejections no longer prevent subsequent votes from being processed when missing dependencies become available.
  • Network requests, WebSocket queues,
20

r/atto•

I previously posted results from ten paired GitHub-hosted runners. Those results varied substantially between hosts, particularly for Nano, while GitHub did not expose enough information to isolate the hardware differences.

I have now repeated the comparison on one fixed OCI host selected to match the current Nano principal representative guidance.

Host

  • Ubuntu 24.04
  • OCI VM.Standard.E5.Flex
  • 4 OCPUs / 8 vCPUs
  • AMD EPYC 9J14
  • 16 GB RAM
  • 400 GB balanced boot volume with durable benchmark storage
  • 4 Gbps networking
  • Java 21.0.12
  • Docker 29.7.2

On x86 OCI shapes, one OCPU represents one physical core with two hardware threads.

500 accounts in parallel

Each range is the lowe

10

r/codex•

Full disclosure: I’m Atto’s solo developer.

A structured Hermes audit found a critical flaw in Atto’s live vote handling. I verified it, stopped the release, and fixed it last month in node v1.33. It is now CVE-2026-73855, rated CVSS 9.3.

Later, gpt-5.6-sol ultra in Codex independently found the exact same flaw without my purpose-built audit workflow. It still missed several less severe findings that the structured audit caught.

The experience changed how I think about context, subagents, and AI security reviews:

https://atto.cash/blog/age-of-continuous-audits

Are native Codex subagents enough for large security reviews now, or do you still use an explicit task and evidence structure?

10

r/atto•

Fix already patched since July!

A critical vote-validation vulnerability affecting Atto node versions older than 1.33 has been fixed.

The flaw could allow a connected peer to claim another representative’s voting weight before the received vote’s signature was validated. It is rated CVSS 9.3. If you operate an Atto node older than v1.33, upgrade. There is no workaround.

Advisory: https://github.com/attocash/node/security/advisories/GHSA-mm7v-33mg-6r9p
Behind-the-scenes audit story: https://atto.cash/blog/age-of-continuous-audits

20

r/atto•

Atto node v1.34 is live, with a major rebuild of the bootstrap path.

In observed runs, a new node caught up in 6–7 hours instead of roughly 15 hours on v1.33. That is more than twice as fast, although exact times will still depend on hardware, disk and database performance, network conditions, and the peers serving history.

The main changes:

- bounded discovery queues instead of unlimited buffering
- adaptive pacing based on measured MySQL insert throughput
- true multi-row persistence batches of up to 1,000 transactions
- exact-batch retries after database failures
- faster gap discovery on large databases
- removal of the old 10 ms delay between historical tr

10