0
Under review

XMR paid out 21 hours ago, but nothing received in my wallet yet

Kiba45135 6 years ago updated 6 years ago 16

According to my payments page (https://coinfoundry.org/pool/xmr/account/49JV3T88YaoH2maZAbuf55S6i2niebLEXEAxpgQHKpG5d3cEjyW8rQyRR8gwvA6xnQ5evnJK3fi3z3edX3r7N8Vc3uHtSxr) payment was sent 21 hours ago but nothing has appeared in my wallet. In the past I've not noticed it taking so long. A few questions.. A.) Is this expected? ; if so, when could I expect to see it reach my wallet? Details below. Thanks!


Sent Amount Transaction 21 hours ago 0.10286 f3066db773542f4adf79c7de17c448678a10a3244574<truncated> https://chainradar.com/xmr/transaction/f3066db773542f4adf79c7de17c448678a10a32445747f70dd44d27010307746


// From FAQ: 
"When will I get paid?
You won't see any balance in your account until a block has been found by the pool and after the block has reached a mature status. This may take a couple hours, depending on the coin. As soon as a block can be considered 'mature' by the pool, your shares will be used to calculate your contribution towards finding the block."


## Similar KB post:

https://feedback.coinfoundry.org/communities/1/topics/445-xmr-payout-2012017

I am having same issue. Payments before fork came in a matter of hours, still nothing since the fork.

Under review

The problem is that once the coins have left the pool wallet they are (and should be) beyond our control. Are you guys sure you using a legit wallet that's fully synced?

I am using the wallet from GetMonero.org... I am noticing it is having issues connecting to the daemon.... I am reading an article on their site right now how to correct the issues... Seems like its the wallet gui app causing the issues.

Same for me. Looks like the issue is because I didn't update the wallet and daemon >before< the fork. oooppss.


Started a new block chain download for same wallet address. Could be a while before I see if that fixes it.


Del

+1

Fresh block chain download worked. I manually saved the block chain and then restarted the daemon a few times as it seemed to slow down. Got there eventually and all good now.

Aye, the same thing worked for me too. Took a while to DL the 52+GB on my internet connection.

Yeah, I upgraded the wallet after the fact and it is having trouble syncing with the old blockchain.... gunna resync the chain ans see if that helps

// Started with: 
monero-gui-v0.11.1.0 for Win x64 of official Monero client w/ wallet (from https://getmonero.org/downloads/
fully synch'd and daemon running


// This morning (4/22/18) upgraded to: 
0.12.0.0 Lithium Luna for Win x64 of official Monero client w/ wallet (from https://getmonero.org/downloads/
fully synch'd and daemon running


No change. No deposit.

Prior to the fork everything was fine with transactions (coinfoundry and otherwise), but this is the first one I've had since. Later this morning I'll do some reading and see what else I can do on the client side.


Thanks for your help.

I'm going to relaunch daemon with more logging on and see what's in the logs. I'm on Win7 x64. I see "Error: Couldn't connect to daemon: 127.0.0.1:18081" when showing daemon status, however the GUI shows okay, connected, and sync'd and netstat shows local sockets connected (shown below).

_________________________________


## Processes:
--> monero-wallet-gui.exe, 48304, 0.08, 17.91 kB/s, 177.89 MB, 7:54:44 AM 4/22/2018, , <username>, G:\<path>\monero-gui-win-x64-v0.12.0.0\monero-gui-v0.12.0.0\monero-wallet-gui.exe, ASLR

--> monerod.exe, 48500, 1.46, 254.99 kB/s, 173.31 MB, 8:48:34 AM 4/22/2018, , <username>, G:\<path>\monero-gui-win-x64-v0.12.0.0\monero-gui-v0.12.0.0\monerod.exe, ASLR


## Here's when I initiate a shutdown of daemon and restart it:

Error: Couldn't connect to daemon: 127.0.0.1:18081
Error: Couldn't connect to daemon: 127.0.0.1:18081

Height: 1557321/1557321 (100.0%) on mainnet, not mining, net hash 551.88 MH/s, v7, up to date, 0(out)+0(in) connections, uptime 0d 0h 0m 1s
Height: 1557321/1557321 (100.0%) on mainnet, not mining, net hash 551.88 MH/s, v7, up to date, 8(out)+0(in) connections, uptime 0d 0h 8m 42s
Height: 1557321/1557321 (100.0%) on mainnet, not mining, net hash 551.88 MH/s, v7, up to date, 8(out)+0(in) connections, uptime 0d 0h 8m 51s

Stop signal sent

## Netstat showing some established connections and 3 time waits 
G:\Windows\system32>netstat -ano | find "18081"
  TCP    127.0.0.1:18081        0.0.0.0:0              LISTENING       48500
  TCP    127.0.0.1:18081        127.0.0.1:48328        ESTABLISHED     48500
  TCP    127.0.0.1:48328        127.0.0.1:18081        ESTABLISHED     48304
  TCP    127.0.0.1:48358        127.0.0.1:18081        TIME_WAIT       0
  TCP    127.0.0.1:48359        127.0.0.1:18081        TIME_WAIT       0
  TCP    127.0.0.1:48360        127.0.0.1:18081        TIME_WAIT       0
  
## Below is a screenshot of what the Monero client shows for status:



+1

I started the daemon manually and then ran the GUI wallet as the GUI could never start the daemon. PITA.

Launched monerod.exe and monero-wallet-cli.exe and everything looks fine. I don't see any client-side issues. 


How can I verify a payment was actually sent to my wallet?


## Below shows CLI wallet load, displays status, inbound transfers and balance.

-------------------------------------------------------------------------------------------------------

G:\<path>\monero-gui-win-x64-v0.12.0.0\monero-gui-v0.12.0.0>monero-wallet-cl
i.exe
This is the command line monero wallet. It needs to connect to a monero
daemon to work correctly.

Monero 'Lithium Luna' (v0.12.0.0-master-release)
Logging to G:\<path>\monero-gui-win-x64-v0.12.0.0\monero-gui-v0.12.0.0\moner
o-wallet-cli.log
Specify wallet file name (e.g., MyWallet). If the wallet doesn't exist, it will be created
.
Wallet file name (or Ctrl-C to quit): G:\<path>\Wallet-HM
Wallet and key files found, loading...
Wallet password:
Opened wallet: 49JV3T88YaoH2maZAbuf55S6i2niebLEXEAxpgQHKpG5d3cEjyW8rQyRR8gwvA6xnQ5evnJK3fi
3z3edX3r7N8Vc3uHtSxr
**********************************************************************
Use the "help" command to see the list of available commands.
Use "help <command>" to see a command's documentation.
**********************************************************************
Starting refresh...
Refresh done, blocks received: 0
Untagged accounts:
          Account               Balance      Unlocked balance                 Label
 *       0 49JV3T        0.000823818322        0.000823818322       Primary account
----------------------------------------------------------------------------------
          Total        0.000823818322        0.000823818322
Currently selected account: [0] Primary account
Tag: (No tag assigned)
Balance: 0.000823818322, unlocked balance: 0.000823818322
Background refresh thread started
[wallet 49JV3T]:

[wallet 49JV3T]: status
Refreshed 1557321/1557321, synced, daemon RPC v1.19

[wallet 49JV3T]: show_transfers in
 1514707     in       2018-02-21       0.006634460000 9ed483e524f815bd1e884a754f7dc3aba32e
91a12d808a9fa73756f57ebd97ed 0000000000000000 0 -
 1527466     in       2018-03-11       0.124556657699 e9e684df06468281da089447b91ba74a3576
e9af1fe76e031294a74bc6b74f6b 0000000000000000 0 -
 1534780     in       2018-03-21       0.110083920623 72938609784d163a15692437a797c172ea89
f31788ce74baddfbde3c2e7a6ab7 0000000000000000 0 -
 1538419     in       2018-03-26       0.128000000000 13a42cc21303a5985168d6d1034753c3afa4
383efeb842ab2d10e954b64e6f38 0000000000000000 0 -



Your payment was part of a batch transfer that included the payments too all eglible miners in a single transaction. Either all payments get sent or none.

+1

Thanks Oliver.


I cleared my G:\ProgramData\bitmonero folder and it's rebuilding it now; imagine this will work based on what delone70 said.

Yeah, same here.... I will post if deleting the block chain works once its done syncing.  

Cool, me too. I've still got a ways to go before I'm synchronized..

+1

That worked! Thanks delone70 and everyone for the help.