Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1824. (Read 4670606 times)

@othe: you are right, but with bitcoin-qt wallet and standard options you could send the change without any confirmations, so this stays hidden from the regular user.

understood  

If this behaviour of outperforming during a btc downtrend persists I will have to consider rotation.

locked means they have less than 10 confirmations, which is just normal because you have send coins out and got coins back which arent confirmed yet.


Of course it does, the changed balance is always immature till confirmed.

@hughjays77: after some blocks the balance will be unlocked. Some part of the balance get locked for a few blocks after each transaction from the wallet. This is a little confusing, because it won't happen in any bitcoin clone.

hi all
does any one has payout issue with monero.crypto-pool.fr ?, i've 45 XMR rewared according to the pool, but only 16 are on my wallet

scam ?

my simple wallet all of a sudden only has a 2/3rd's of my coins in UNlocked balance. The balance is correct but it seems that 1/3rd of my coins are locked. I was able to send with no issues to Poloniex[ 30mins prior] and I did NOT recently receive any coins that still requires confirmation so not sure what the issue is. My bitmonerod deamon is running in background but is 560-580 blks behind[keeps on increasing]

Any help would be appreciated

They added it in February. The just removed it two days after, (something about technical issues)

if they are technically ready for CryptoNote.

only .bin.keys is crucial, .bin file is just a cache. I prefer backing up both of them.

With the new feature of deterministic wallets from recent update, you don't even need to backup any file, just remember 24-word seed. It's similar to Electrum client for Bitcoin.
http://www.reddit.com/r/Monero/comments/27txuf/the_monero_missives_weekly_report_june_10th_2014/

Mintpal refused to add monero before because of its different algorithm etc etc. Now it let Monero get on the voting list, I'm 101% sure they're going to add it.

What is necessary to make an offline backup?
Just the 3 bin files in the folder or more?
as example *.bin & *.bin.adress.txt & *.bin.keys

thanks in advance

Caution advised: No payouts from http://monero.crypto-pool.fr/ in the last 14hr+.

The pool shows my Total Paid at over 2XMR, but nothing has been received.  My wallet is synced and operating fine and I've never had issues with payouts from other pools before.  I contacted the pool admin, and he doesn't seem to know what's going on (claiming payouts are fine when they are not, and asking me if I am out of sync).

It's certainly not a problem on my end, because others confirm not receiving payment (at least 2 other miners in IRC).

I would suggest being careful on crypto-pool.fr until the pool admin provides an update.

do you have a source ? and if so did they refund the btcs sent to them for voting ?

Previously Mintpal repeatly denied to have Monero on voting list because this coin is not based on Bitcoin protocol. Suddenly few days ago Monero appeared on voting list, so i think Mintpal is technically ready for CryptoNote.


confirm what ? they wouldn't reveal anything.

can anyone confirm this with mintpal?

I would be shocked if MintPal added MRO. They wouldn't add Nxt when Nxt got first place votes for a mile, once they realized they actually had to modify the api since it wasn't a bitcoin clone. Nxt offered its own developers for help, but MintPal was too lazy.

I think this is one reason why the price is being pumped at the moment.

Those daemon errors are not uncommon, its all to do with it commmunicating with other peers.

The send_que_size is more than... error is because the daemon tries to shove more data at a remote peer than it is supposed to in a session

The connection closed by remote host is someone else's daemon disconnecting you for some reason


You can usually ignore them, but if you are getting loads at the same time it can end up only talking to one or two peers and getting out of sync. Even so thats not a major problem unless you are running a pool.

Can someone explain these errors in the daemon?  It goes on forever in red text except for the bolded which is white.  Before I was mostly getting the bolded error.

2014-Jun-14 13:46:44.564557 [P2P8]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than
 ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
2014-Jun-14 13:46:44.570561 [P2P8]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\levin_protocol_handler_async.h:638 [24.8.142.47:18080 O
UT]Failed to do_send()
2014-Jun-14 13:46:44.577566 [P2P8]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than
 ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
2014-Jun-14 13:46:44.588574 [P2P8]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\levin_protocol_handler_async.h:638 [81.155.65.215:18080
 OUT]Failed to do_send()
2014-Jun-14 13:47:08.950807 [P2P1]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than
 ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
2014-Jun-14 13:47:10.594970 [P2P1]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\levin_protocol_handler_async.h:638 [24.8.142.47:18080 O
UT]Failed to do_send()
2014-Jun-14 13:47:10.602976 [P2P1]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than
 ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
2014-Jun-14 13:47:10.609980 [P2P1]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\levin_protocol_handler_async.h:638 [81.155.65.215:18080
 OUT]Failed to do_send()
2014-Jun-14 13:47:12.034988 [P2P3]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than
 ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
2014-Jun-14 13:47:12.041993 [P2P3]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\levin_protocol_handler_async.h:638 [24.8.142.47:18080 O
UT]Failed to do_send()
2014-Jun-14 13:47:12.047997 [P2P3]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than
 ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
2014-Jun-14 13:47:12.056004 [P2P3]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\levin_protocol_handler_async.h:638 [81.155.65.215:18080
 OUT]Failed to do_send()
2014-Jun-14 13:47:17.557895 [P2P2]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than
 ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
2014-Jun-14 13:47:42.866797 [P2P3][sock 2288] Some problems at write: An existin
g connection was forcibly closed by the remote host:10054
2014-Jun-14 13:48:02.277528 [P2P2]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\levin_protocol_handler_async.h:515 [24.8.142.47:18080 O
UT]Failed to do_send
2014-Jun-14 13:48:02.289536 [P2P2]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than
 ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
2014-Jun-14 13:48:02.297542 [P2P2]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\levin_protocol_handler_async.h:515 [81.155.65.215:18080
 OUT]Failed to do_send