New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wrong result from get_address_txs? #33
Comments
test server is running The branch has numerous changes (time based imports, integrated address, upgraded angularjs, support of latest dev monero from master, angular cleanups), mostly to frontend. However Any errors you get? |
I added this testnet wallet. On transactions tab all tx's show positive amounts, which is not correct. Example: Another example is I also noted the default testnet wallet also shows positive amounts only. |
I see. It shows incoming txs only (i.e. change returned to you). But the overall wallet balance (i.e., 80.409981421942 XMR) should be ok? If balance is ok, this means that backend correctly fetches all txs to the frontend (thus balance is ok). JavaScript must incorrectly lists txs in the account overview and transaction list. I will look into it. |
yes, balance is correct. It could be a js error. Though, i was suspecting that the wallet balance was calculated by the data from get_address_info and not get_address_txs in the web wallet? I'm not seeing this error on mainnet when using myMonero backend, which makes me think it could be a backend error. |
results in incorrect tx details #33
results in incorrect tx details #33
You were right. It was backend problem. Was using wrong tx public key for spent outputs in get_address_txs. It has been fixed for txs both in blockchain and mempool. Should be ok now.
|
Thanks! Works great now. |
Since I can't get my own server running (#31) I'm using your testnet server (http://139.162.32.245:81) currently. Is it running master or something else? I'm suspecting that get_address_txs is giving me weird results. On #/transactions I'm only seeing incoming tx's. I can dig deeper into it if you don't already know what's causing it.
The text was updated successfully, but these errors were encountered: