-
foxett
Hello. I need help. For some reason I receive one transaction out of several using the Wallet RPC get_transfers method
-
m-relay
<jeffro256:monero.social> Can you provide more information, please? What does `wallet2::get_transfers` return versus the RPC endpoint that you're missing? What kind of transactions are they? What kind of wallet? Which calls exactly did you make before this? Do you have logs? You really haven't explained what expected behavior you're looking for or what you've tried already which makes it hard for people to help you.
-
foxett
i'm sorry.
pastebin.com/iSKpCh2W link for request and response from postman. I receive one (first) transaction although monero gui shows correctly from the same node - 2 transactions
-
m-relay
<jeffro256:monero.social> Was the second transaction still in the pool?
-
m-relay
<jeffro256:monero.social> `get_transfers` only returns confirmed transactions
-
foxett
The second transactions The second transaction already has 523 confirmations. Tell me how I can show you the logs of the second transaction from the monero gui?
-
foxett
The second transaction already has 523 confirmations. Tell me how I can show you the logs of the second transaction from the monero gui?
-
foxett
The second transaction id: 4b5971a135f92ab939dc36715fec869fa90292befc6dd34dcdef294028e91650
-
m-relay
<ofrnxmr:xmr.mx> Are all transfers going to the same account?
-
m-relay
<jeffro256:monero.social> Yes, the `account_index` parameter you send in the request must match the subaddress account index of the received transfer that you're expecting in the responde
-
foxett
yes. One wallet, one account, several addresses
-
foxett
I tried with it and tried without it at all. The result is the same. At the same time, Wallet GUI displays everything correctly. Both transactions were sent to the same address.
-
m-relay
<jeffro256:monero.social> Is it returned with the `incoming_transfers` RPC endpoint?
-
foxett
-
foxett
First transaction only
-
m-relay
<ofrnxmr:xmr.mx> Using the exact params that you sent, returned multiple transactions for me
-
m-relay
<rajafan:xmr.se> what is the average commission for xmr withdrawal?
-
m-relay
<ofrnxmr:xmr.mx> plowsof
-
foxett
When requesting a balance through the RPC, I also see a balance that takes into account only the first transaction
-
m-relay
<jeffro256:monero.social> Commission from whom ?
-
m-relay
<ofrnxmr:xmr.mx> Yes, connected to my own node and my own wallet
-
m-relay
<ofrnxmr:xmr.mx> Bro keeps posting nonsense in here
-
foxett
What could be wrong with me?
-
m-relay
<ofrnxmr:xmr.mx> the wallet file that your using might not be synced?
-
m-relay
<ofrnxmr:xmr.mx> You're*
-
m-relay
<jeffro256:monero.social> Is it different wallet cache files ?
-
m-relay
<rajafan:xmr.se> for withdrawal via automatic system
-
m-relay
<jeffro256:monero.social> What automatic system blud
-
foxett
{
-
foxett
"id": "0",
-
foxett
"jsonrpc": "2.0",
-
foxett
"result": {
-
foxett
"height": 3400501
-
foxett
}
-
foxett
}
-
foxett
It seems to be less than a block with a transaction
-
plowsof
Rajafan form a coherent question in another channel as this is likely not dev related
-
m-relay
<jeffro256:monero.social> Yeah that height is ~1000 blocks behind
-
foxett
I did get_height correctly to get the current sync block of the wallet?
-
m-relay
<ofrnxmr:xmr.mx> The same nameless one he's been asking about posting on getmonero for 6 months
-
m-relay
<ofrnxmr:xmr.mx> Foxett, yes, but your wallet isnt synced
-
m-relay
<ofrnxmr:xmr.mx> Same one he posted screenshots here about
-
foxett
Thank you very much guys. Can you tell me if I can run synchronization by request or do I need to contact DevOps to run it on the server?
-
m-relay
<ofrnxmr:xmr.mx> Tldr: its unrelated to monero-dev , monero-site, etc.
-
m-relay
<ofrnxmr:xmr.mx> You just need to connect the wallet to a daemon and let it sync
-
m-relay
<jeffro256:monero.social> Foxett, you can call the "refresh" command on the RPC wallet as long as it has an assigned daemon
-
m-relay
<jeffro256:monero.social> If it doesn't have an assigned daemon , you can assign one by URL using the "set_daemon" command
-
foxett
Thank you guys. Sorry for my English. I am writing through a translator.
-
m-relay
<jeffro256:monero.social> That's okay! I'm glad ofrn could figure it out lol
-
m-relay
<jeffro256:monero.social> It's always a syncing issue isn't it
-
foxett
after refresh when I request get height I get different values every time but sometimes they become bigger sometimes smaller but they repeat all the time. What could it be? That is, it does not catch up with the node
-
m-relay
<ofrnxmr:xmr.mx> are you using v0.18.4.0?
-
foxett
"version": "0.18.3.4-release",
-
m-relay
<ofrnxmr:xmr.mx> Update to 18.4.0
-
foxett
Thank you. I asked DevOps to do it already.
-
m-relay
<ofrnxmr:xmr.mx> the get_height should only be increasing. Is the wallet being closed periodically? There is a bug that will lose the wallet state if closed
-
m-relay
<ofrnxmr:xmr.mx> Lets continue in #monero-support
-
foxett
I understand that it should increase after node blocks, but it runs in circles between some values. Maybe RPC Wallet needs to be restarted? There are no errors. Try closing and opening the wallet?