In-Chat and Direct Crypto Transfers (Scenario) in ADAMANT

[metalisk]

ADAMANT Messenger supports seamless crypto transfers both inside chats and directly from the Wallet screen. Users can also track all operations in the Transaction History.

In-Chat Crypto Transfers

Pre-Checks (Sending Screen)

Before sending, the app validates:

• 0A. User balance — check if there are enough ADM to send a transaction with JSON. Otherwise, show an error and allow retry.
• 0B. Internet connection — if unavailable, show an error and allow retry
• 0C. ADM node availability (via health check). If unavailable, show an error and allow retry.
• 0D. Crypto node availability (via health check). If unavailable, show an error and allow retry.

Transaction Flow

1. Generate a crypto transaction and its ID locally
2. Generate both ADM tx and coin tx locally
3. Nonce check:
   • For chains with nonces (ETH): verify local storage. If a transaction with the same nonce exists and hasn’t failed, show an error and stop.
   • For chains without nonces (BTC, DOGE, DASH): check local storage + query blockchain for pending tx. If pending and not failed, show error and stop.
4. Send ADM tx to the ADM node
5. If accepted, add the ADM tx to the chat and stay on the Send screen. Otherwise, show an error and allow retry.
6. Store crypto tx in the local database → it is displayed in Tx history along with node list from API results. Use local timestamp for ordering until blockchain timestamp is available. Status: tx is already Pending.

💡 This applies to non-ADM coin transfers (e.g., ETH).
Even after sending ETH in chat or directly from Wallet (step 7), the app only has local transaction data at the moment of sending — the ETH node hasn’t returned it yet. Still, we must display this tx immediately in the chat or in the transaction list.
In the transaction list (e.g., Account → Wallet → ETH), all txs are sorted by time.
That’s why we rely on the locally stored timestamp until the actual blockchain timestamp becomes available.

7. Send crypto tx to the coin node
8. On success, navigate instantly to Chat (or Tx details).
   • Any positive response from the node = mark tx as Pending (no need to wait for mempool registration or confirmations).
   • If sending fails (timeout, node error): show snackbar, stay on Send screen, and allow retry. A retry generates a new transaction (start from step 0).
   • If the user returns to Chat without retry, the failed tx still appears in Chat and Tx history (since the ADM message was already sent).
9. Tx updates continue in the background

Why step 2 before step 4?
To ensure the crypto transaction is never sent without being recorded in chat. Otherwise, the user might spend crypto without seeing it and resend by mistake.

Direct Crypto Transfers (Wallet Screen)

The scenario is the same as for In-Chat Crypto Transfers, except:

• Skip 0A (ADM balance check)
• Skip 0C (ADM node check)
• Skip 2 (no ADM tx creation)
• Skip 4, 5 (no ADM tx)
• Redirect the user to Tx history instead of Chat.

Transaction History

On the Tx History screen, transactions are a mix of:

• Locally stored txs — kept even after app restart until logout/re-login. Must be cleared on logout/login to prevent showing another account’s history.
• Txs from node API — synced from blockchain

Together, they provide the most accurate, up-to-date overview of user transfers.

Notes

• Wherever possible, use local calculations and checks (tx generation, balance, nonce, duplicates, timestamps). This ensures a smooth and responsive UX — the user gets instant feedback without waiting for network requests.

Demo

Bitcoin (BTC) In-Chat Crypto Transfer demo:

[adamant-al]

See also: Statuses for Messages and Transfers https://github.com/orgs/Adamant-im/discussions/30