harmony-one / explorer-v2-frontend

19 stars 23 forks source link

transactions show up on the receiver's wallet address, but not on the sender's wallet address #112

Closed lijiang2087 closed 2 years ago

lijiang2087 commented 2 years ago

these transactions show up on the receiver's wallet address, but not on the sender's wallet address:

these 2 txns shows on receiver's wallet: https://explorer.harmony.one/address/0x6532974d5fb193de27d4d9479789ea68053bb715

but not on the sender's wallet: https://explorer.harmony.one/address/one1a5fznwvnr3fed9676g42u7q30crtmmkk5qspe9

ArtemKolodko commented 2 years ago

Explorer client uses Node RPC API to get address history. I checked RPC response and figured out that one of two transactions doesn't returned from request to _hmyv2getTransactionsHistory

Curl request to reproduce:


curl --location --request POST 'https://api.s0.t.hmny.io/' \
--header 'Content-Type: application/json' \
--data-raw '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "hmyv2_getTransactionsHistory",
    "params": [{
        "address": "one1a5fznwvnr3fed9676g42u7q30crtmmkk5qspe9",
        "pageIndex": 0,
        "pageSize": 1000,
        "fullTx": true,
        "txType": "ALL",
        "order": "DESC"
    }]
}' \
> one1a5fznwvnr3fed9676g42u7q30crtmmkk5qspe9_history.txt

Response doesn't contain tx 0x814ece883ca7ed1fe1911fbfd444ba34d4454d08fef7e1b9b3e7e0ccf15cd639

Issue may be related to nodes maintenance. The solution could be to refactor the explorer service and client to implement endpoint with full address history (after additional performance tests).