feat: add Atto support#227
Open
rotilho wants to merge 1 commit into
Open
Conversation
|
@rotilho is attempting to deploy a commit to the MoonPay Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds Atto chain support to OWS, including chain registry metadata, wallet derivation/import, message signing, transaction signing, work generation, and transaction publishing.
Why
Atto is fast, feeless digital cash built for payments. It uses an account-chain model, where each account maintains its own chain, with its own protocol, address format, transaction encoding, signing rules, and network APIs.
This makes Atto a natural fit for OWS. Atto’s lack of fees and low-latency finality, currently around 150ms confirmation time, is especially powerful for agent payments and machine-driven payment flows where multi-second settlement times or per-transaction network fees directly affect the user experience.
With this PR, Atto can use the same flows as other supported chains: account derivation, wallet material import, message signing, Atto block signing, work attachment where required, and transaction publishing.
Testing
cargo test --workspacepassescargo clippy --workspace -- -D warningsis cleannpm testpasses (if Node bindings changed)owsCLINotes
Node/npm binding updates are intentionally left out of this PR to keep the Atto review focused on the Rust core, signer, library and CLI.