status-go/services/wallet
Roman Volosovskyi 6bea21c197
[wallet] Skip transaction on chain id mismatch
Sometimes eth_getBlockByNumber returns txs with chainId which is not
equal to chanin's id. That caused an error and tx fetching was
interrupted. From now on such txs will be skipped.
2021-03-19 15:54:39 +02:00
..
erc20 Add api method to query token balances 2019-07-05 08:38:29 +03:00
ierc20 [#2042] Wrong ERC20 decimal rounding in "Set max" 2020-09-22 16:00:47 +02:00
README.md Cleanup after tx fetching changes 2020-02-09 12:05:36 +02:00
api.go [wallet] Store account's last known balance and nonce 2021-03-15 16:18:12 +02:00
async.go Watch new accounts aftter they were saved to accounts table (#1569) 2019-08-28 10:49:03 +03:00
balance.go [wallet] RPC usage stats 2021-03-10 13:32:46 +02:00
balance_cache.go [wallet] Nonce range cache 2021-03-16 16:20:11 +02:00
balance_test.go [wallet] RPC usage stats 2021-03-10 13:32:46 +02:00
commands.go [wallet] Skip transaction on chain id mismatch 2021-03-19 15:54:39 +02:00
commands_test.go [wallet] Skip transaction on chain id mismatch 2021-03-19 15:54:39 +02:00
concurrent.go [wallet] Store account's last known balance and nonce 2021-03-15 16:18:12 +02:00
concurrent_test.go [status-im/status-react#9927] Fast blocks sync after delay 2020-01-30 17:25:56 +02:00
database.go [wallet] Store account's last known balance and nonce 2021-03-15 16:18:12 +02:00
database_test.go [wallet] Store account's last known balance and nonce 2021-03-15 16:18:12 +02:00
downloader.go [wallet] Skip transaction on chain id mismatch 2021-03-19 15:54:39 +02:00
downloader_test.go [wallet] Skip transaction on chain id mismatch 2021-03-19 15:54:39 +02:00
events.go [wallet] Detect non archival RPC node 2021-01-25 14:52:14 +02:00
iterative.go [wallet] Reduce number of RPC requests 2020-11-25 12:20:23 +02:00
iterative_test.go status-im/status-react#9203 Faster tx fetching with less request 2020-01-23 10:36:11 +02:00
on_ramp.go Added API for getting on ramp data 2021-02-17 09:53:45 +01:00
on_ramp_test.go Added API for getting on ramp data 2021-02-17 09:53:45 +01:00
reactor.go [wallet] Skip transaction on chain id mismatch 2021-03-19 15:54:39 +02:00
service.go [wallet] Store account's last known balance and nonce 2021-03-15 16:18:12 +02:00
service_test.go [wallet] Reduce number of RPC requests 2020-11-25 12:20:23 +02:00
sql_big_int.go [wallet] Store account's last known balance and nonce 2021-03-15 16:18:12 +02:00
transfer_view.go Local notifications service (#2026) 2020-10-28 10:56:14 +03:00
transfers_query.go Local notifications service (#2026) 2020-10-28 10:56:14 +03:00
transmitter.go Handle wallet initialization 2020-08-18 14:13:08 +02:00

README.md

Wallet

Wallet service starts a loop that watches for new transfers (eth and erc20). To correctly start the service two values need to be changed in the config:

  1. Set Enable to true in WalletConfig
{
  "WalletConfig": {
    "Enabled": true,
  }
}
  1. And expose wallet API with APIModules
{
  APIModules: "eth,net,web3,peer,wallet",
}

API

wallet_getTransfersByAddress

Returns avaiable transfers in a given range.

Parameters
  • address: HEX - ethereum address encoded in hex
  • toBlock: BIGINT - end of the range. if nil query will return last transfers.
  • limit: BIGINT - limit of returned transfers.
Examples
{"jsonrpc":"2.0","id":7,"method":"wallet_getTransfersByAddress","params":["0xb81a6845649fa8c042dfaceb3f7a684873406993","0x0","0x5"]}
Returns

Objects in the same format.

wallet_getTokensBalances

Returns tokens balances mapping for every account. See section below for the response example.

Parameters
  • accounts HEX - list of ethereum addresses encoded in hex
  • tokens HEX - list of ethereum addresses encoded in hex
{"jsonrpc":"2.0","id":11,"method":"wallet_getTokensBalances","params":[["0x066ed5c2ed45d70ad72f40de0b4dd97bd67d84de", "0x0ed535be4c0aa276942a1a782669790547ad8768"], ["0x5e4bbdc178684478a615354d83c748a4393b20f0", "0x5e4bbdc178684478a615354d83c748a4393b20f0"]]}

Returns

First level keys accounts, second level keys are tokens.

{
  "0x066ed5c2ed45d70ad72f40de0b4dd97bd67d84de": {
    "0x1dfb2099f936b3e98bfc9b7059a8fb04edcce5b3": 12,
    "0x5e4bbdc178684478a615354d83c748a4393b20f0": 12
  },
  "0x0ed535be4c0aa276942a1a782669790547ad8768": {
    "0x1dfb2099f936b3e98bfc9b7059a8fb04edcce5b3": 14,
    "0x5e4bbdc178684478a615354d83c748a4393b20f0": 14
  }
}

Signals

Two signals can be emitted:

  1. newblock signal

Emitted when transfers from new block were added to the database. In this case block number if the number of this new block. Client expected to request transfers starting from received block.

{
  "type": "wallet",
  "event": {
    "type": "newblock",
    "blockNumber": 0,
    "accounts": [
      "0x42c8f505b4006d417dd4e0ba0e880692986adbd8",
      "0x3129mdasmeo132128391fml1130410k312312mll"
    ]
  }
}
  1. reorg signal.

Emitted when part of blocks were removed. Starting from a given block number all transfers were removed. Client expected to request new transfers from received block and replace transfers that were received previously.

{
  "type": "wallet",
  "event": {
    "type": "reorg",
    "blockNumber": 0,
    "accounts": [
      "0x42c8f505b4006d417dd4e0ba0e880692986adbd8"
    ]
  }
}
  1. history signal

Emmited when historical transfers were downloaded. Block number will refer the first block where historical transfers were found.

{
  "type": "wallet",
  "event": {
    "type": "history",
    "blockNumber": 0,
    "accounts": [
      "0x42c8f505b4006d417dd4e0ba0e880692986adbd8"
    ]
  }
}