Accounts and activity.
Use protocol types and a remote node client to query accounts and follow transactions. Add monitors when you need to track a changing set of addresses.
BuildAtto Commons
Your application.
Atto inside.
From exact amounts to a complete wallet flow. Commons gives you the protocol types, clients and workers to build Atto into your own software. Choose the modules you need.
- TypeScript
- JavaScript
- Java
- Kotlin
TypeScript and JavaScript through npm; Java and Kotlin on the JVM. Platform support, including Kotlin/Wasm, varies by module. Use matching module releases and check their requirements.
Package on npm ↗Your application
Pick the pieces you needcommons-coreExact types. Protocol primitives.
Amounts, keys, addresses, blocks, serialization and validation. Start here when your application needs to speak Atto.Read this module →Start with a read.
Build from there.
A network monitor and a wallet have different responsibilities. You do not need a signer or a wallet just to read an account.
Your wallet workflow.
Add wallet helpers for accounts, sends and automatic receiving. Pair them with a worker. JVM applications can use remote signing when keys belong behind a signing service.
Choose where work runs.
Prepare proof-of-work on the CPU, in a compatible browser, on a JVM with OpenCL, or through a remote service.
From payment intent.
To a transaction.
Your application chooses the recipient, amount and spending rules. Commons handles the protocol steps that turn an authorized payment into a transaction.
Your app authorizes 0.0001 ATTO a recipient
- 01
Build
Create a send block from the account state, recipient and exact amount.
- 02
Sign + work
Sign the block and attach valid proof-of-work, freshly generated or cached.
- 03
Validate
Check the assembled transaction, including its signature and proof-of-work.
- 04
Publish
Submit the validated transaction through the remote node client.
Publication, network confirmation and the recipient’s receive transaction are separate steps. Node monitors let your application follow what happens next.
Try the exact-amount example →The protocol tools.
Your application rules.
Commons supplies the building blocks. Your application still owns authorization, key storage, spending limits and the lifetime of its network connections.
Keep the data intact.
Pass raw JSON strings into the appropriate Commons parser. Decoding large integers with a normal JSON parser first can lose precision.
Parsing is not cryptographic verification. Call the appropriate validation method when the application needs to verify a transaction.
Choose your level of control.
Use Commons for a custom integration. For a ready-made wallet interface, the CLI, MCP server and N8N nodes provide more of the application workflow.
Importing a Commons package does not add the CLI or MCP approval policy to your application.
JavaScript packages use the @attocash/ scope; Gradle dependencies use cash.atto. Prefer individual modules over the deprecated @attocash/commons-js aggregate. Check each module’s supported targets and release notes before upgrading.
Another way to build.
Choose the interface that fits the work. Each connects to the same feeless Atto network.
Build with Atto Commons.
Open the guide for setup, requirements, and implementation details.