[XMR] Monero - A secure, private, untraceable cryptocurrency

[parker928]

Hey guys im new to the community, is the anon working or is it in development like darkcoin.

It was always working. It never stopped. In fact, you can control the level of anonymity by varying the "mixin count".

[1714882578]

1714882578

[1714882578]

1714882578

[LeroyJenkens]

^The exchanges have some problems, because they were using the old code with smaller fees and their transactions will be included only by the miners also using the old code. Those changes are 16 days old and most of the miners changed their code on 30th of May and just a few miners (and one of the pools?!) are using this old code. The miners using the old code are mining blocks with little to no reward (~0.3 XMR for a mined block?!). This problem started about 30th of May for the exchanges and I wrote them back then to update, but they are little slow with such small issues. Their transactions somehow got mined till now, but it's getting more and more unlikely and their transactions are stuck in the mempool (will be mined or will get eventually returned back to their wallets sooner or later). The exchanges are finally working on the problem and the devs are helping them in #monero-dev. This will be fixed sooner or later and we should receive our XMR.

About the exchanges "didn't notice the change in the tx fee from May 29th":

05/30/2014 Me: "Yes, finally it did. Did you upgraded bitmonerod to the final version? There is a higher tax in the new daemon and it seems your transactions are not propagated and accepted from the network. Thank you."
05/30/2014 Bittrex support: "We have no upgraded yet... I'll make sure to add that to the list."

I bet poloniex is in the same boat, and that is the problem with my withdrawal:

Yesterday I've withdrawn some XMR from Poloniex. The transaction was listed as "COMPLETE" quickly. However today, when checking my wallet (and after refresh), the funds are not there. And indeed the tx id that poloniex shows for this tx is unknown on http://monerochain.info.

I just opened a ticket, but I wonder if somebody else encountered this?

They escalated my ticket, but still didn't solve it.

I had the same problem. I filed the ticket yesterday. It was escalated but still no payment.

[David Latapie]

Notice that cpuminer-multi in homebrew tap is LucasJones's miner, I can't compile wolf's miner for some reason

Thanks I will update accordingly. Please notify me when you can get Wolf' miner.

[Patel]

I think it would be helpful if on the binaries download, there was version number, so people can see if they are still on the latest binary.

[Crypto_Man1212]

Hey guys im new to the community, is the anon working or is it in development like darkcoin.

It was always working. It never stopped. In fact, you can control the level of anonymity by varying the "mixin count".

Thanks for the info,just downloaded the wallet, gonna check it out.Any new developments in the upcoming weeks?

[David Latapie]

This advice was addressed to small miners with 100-200 H/s.

So, I qualify as a very small miner

[David Latapie]

[12:37:55] <darlidada> Hi MintPal-Jay : if Monero is first on voting list on monday are you gonna be able to add it? because its not a bitcoin clone, its total new technology so maybe its gonna be hard, are u aware of it and of the work that needs to be done to implement it? I ask because at the moment investors are betting a lot of bitcoins to make it first on monday! It would be a shame if things doesnt work out
[13:19:46] <@MintPal-Jay> darlidada: We haven't coded it yet, but might do sooner than later given its climb, tomorrow would be a bit too soon

I can't hardly believe they are that incompetent. Overpromise, underdeliver...

Congratulations, darlidada.

[Its About Sharing]

I've been searching and can't find a solution here. Anyone have any idea as to why upon synching I get the below errors?
In particular, why is there "ric" after the /Users/ directory? I'm on a Mac and that is not my user name, so the /Users/ric directory does not exist.
(I've removed the wallet.bin file and restarted everything, new seed and all generated, but this didn't seem to help.)
I started by double clicking on bitmonerod and then once synched, simplewallet, which were downloaded from Github. (I was unable to install via the command line instructions.)

Thanks
IAS

Code:

2014-Jun-15 14:54:28.481185 [P2P8][sock 22] Some problems at write: Broken pipe:32
2014-Jun-15 14:55:35.798590 [P2P3][87.246.145.171:18080 OUT] SYNCHRONIZED OK
2014-Jun-15 14:55:37.316479 [P2P4][134.249.161.21:18080 OUT] SYNCHRONIZED OK
2014-Jun-15 14:55:37.389800 [P2P3][113.190.13.120:18080 OUT] SYNCHRONIZED OK
2014-Jun-15 14:55:37.459267 [P2P3][86.25.118.21:18080 OUT] SYNCHRONIZED OK
2014-Jun-15 14:55:40.417736 [P2P4][101.164.234.118:18080 OUT] SYNCHRONIZED OK
2014-Jun-15 14:55:43.603074 [P2P6][184.190.220.14:18080 OUT] SYNCHRONIZED OK
2014-Jun-15 14:56:01.198940 [P2P0][199.188.178.180:18080 OUT] SYNCHRONIZED OK
2014-Jun-15 14:57:51.320218 [P2P6][sock 15] Some problems at write: Broken pipe:32
2014-Jun-15 14:58:49.917326 [P2P8][sock 22] Some problems at write: Broken pipe:32
2014-Jun-15 14:59:13.308392 [P2P1]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:13.420894 [P2P1]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()
2014-Jun-15 14:59:14.102139 [P2P0]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:14.102228 [P2P0]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()
2014-Jun-15 14:59:14.109085 [P2P0]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:14.109163 [P2P0]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()
2014-Jun-15 14:59:14.375326 [P2P4]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:14.375418 [P2P4]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()
2014-Jun-15 14:59:15.460551 [P2P1]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:15.460639 [P2P1]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()
2014-Jun-15 14:59:15.461740 [P2P1]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:15.461798 [P2P1]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()
2014-Jun-15 14:59:32.024017 [P2P5]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:32.043524 [P2P5]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()
2014-Jun-15 14:59:42.239133 [P2P5]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:42.260234 [P2P5]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:515 [88.193.177.21:18080 OUT]Failed to do_send
2014-Jun-15 14:59:45.678970 [P2P5]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:45.679094 [P2P5]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()

I get the same error, but for me it's "tom" instead of ric... the mystery thickens...

LOL! Are you serious?
Well, hopefully it is nothing as the other poster said. Have you tried moving coins in and out?

Thx,
IAS

[equipoise]

I had the same problem. I filed the ticket yesterday. It was escalated but still no payment.

Me too. They can't possibly pay us before their transactions get unstuck from the mempool or get mined (even a single block mined from an old code miner could be enough, because there is no limit of the block size). They can't even take an XMR loan and pay us now, because then the transaction could be mined and we will be payed twice (if they don't use the same inputs, which could be way too difficult). I expect this to be solved in a few days if not today.

Edit: I was wondering if they could invalidate all the old transaction by deleting the poolstate.bin file, refreshing the wallet from the .keys and then send all the balance to a new wallet with a standard (or larger) fee. Then the old transactions can't be mined, so they could safely resend them; however, it seems there is a problem with this approach too.

[Its About Sharing]

^It's OK, but if you see huge amount of those it's best to restart the daemon.

Can you say what these errors are from? I had restarted the daemon 2X and the same result.
Do other wallets interfere here or

Thx in advance,
IAS

[helloweiwei]

I had the same problem. I filed the ticket yesterday. It was escalated but still no payment.

Me too. They can't possibly pay us before their transactions get unstuck from the mempool or get mined (even a single block mined from an old code miner could be enough, because there is no limit of the block size). They can't even take an XMR loan and pay us now, because then the transaction could be mined and we will be payed twice (if they don't use the same inputs, which could be way too difficult). I expect this to be solved in a few days if not today.

Edit: I was wondering if they could invalidate all the old transaction by deleting the poolstate.bin file, refreshing the wallet from the .keys and then send all the balance to a new wallet with a standard (or larger) fee. Then the old transactions can't be mined, so they could safely resend them; however, it seems there is a problem with this approach too.

I had the same problem. Do not receive payment.This is fatal.

[dewdeded]

Its About Sharing: Just compile yourself from source. It compiles on every Mac.

To install dependencies with homebrew:
brew install miniupnpc cmake boost

Then just: "make" in the source directory.

[surfer43]

^It's OK, but if you see huge amount of those it's best to restart the daemon.

Can you say what these errors are from? I had restarted the daemon 2X and the same result.
Do other wallets interfere here or

Thx in advance,
IAS

ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
Failed to do_send()

These errors do not harm the functioning of the daemon AFAIK.

My pool's daemon gets this all_the_time and it still works properly, syncs, finds blocks, and broadcasts transactions.

[equipoise]

^The bug is well known to developers and they'll fix it, but it's not a high priority now. Basically your daemon is flooding other pears (and your) connection and those pears are disconnecting you. When you see a few of those in a line and then they stop for a while it's fine, but when you see huge amount (obviously you are monitoring your daemon) your best option is to exit the daemon (use "exit" or "q" in order to save the blockchain first) and start it again. This way you'll stop flooding the other pears connection (and yours too).

[sammy007]

^The bug is well known to developers and they'll fix it, but it's not a high priority now. Basically your daemon is flooding other pears (and your) connection and those pears are disconnecting you. When you see a few of those in a line and then they stop for a while it's fine, but when you see huge amount (obviously you are monitoring your daemon) your best option is to exit the daemon (use "exit" or "q" in order to save the blockchain first) and start it again. This way you'll stop flooding the other pears connection (and yours too).

Not a high priority now? So it's ok for pools to restart daemons several times a day initiating disconnects? I am silent about bandwidth usage.

[Its About Sharing]

Thanks for the comments guys.

Its About Sharing: Just compile yourself from source. It compiles on every Mac.

To install dependencies with homebrew:
brew install miniupnpc cmake boost

Then just: "make" in the source directory.

I tried installing from source but I must have had something extra already installed as the install said so. (it failed probably due to a package I already had installed)
I might try another install as you suggested. I'm just not sure about uninstalling the package mentioned and what the affects of that may be.
Perhaps it is just safer to wait it out...

Thx,
IAS

[equipoise]

^The bug is well known to developers and they'll fix it, but it's not a high priority now. Basically your daemon is flooding other pears (and your) connection and those pears are disconnecting you. When you see a few of those in a line and then they stop for a while it's fine, but when you see huge amount (obviously you are monitoring your daemon) your best option is to exit the daemon (use "exit" or "q" in order to save the blockchain first) and start it again. This way you'll stop flooding the other pears connection (and yours too).

Not a high priority now? So it's ok for pools to restart daemons several times a day initiating disconnects? I am silent about bandwidth usage.

Monero devs are working hard to address this and other problems with the code. This is a new technology and is not a bitcoin clone with all those issues already fixed. Stay calm and keep mining.

[anatolikostis]

Hi I have the problem
Error: transaction <5a65b629b7559ae477c97e55e203da7f841b9df2da9f5f7a2813f98541c442c4> was rejected by daemon with status "Failed"

The latest version. How to solve it?

the same problem:

wallet says: transaction <xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> was rejected by daemon with status "Failed"
daemon says: transaction verification failed:  <xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>

anybody who did any tx today?
Both GUI wallets (cryptonote/monero-qt) pulls "success tx" but realy it does not (there is no such tx in official blockchain)  

[uvt9]

....
anybody who did any tx today?

of course we do, stats showing that there was decent amount of transaction volume last 24 hours:
http://monerochain.info/charts/volume

[Keyboard-Mash]

Hi I have the problem
Error: transaction <5a65b629b7559ae477c97e55e203da7f841b9df2da9f5f7a2813f98541c442c4> was rejected by daemon with status "Failed"

The latest version. How to solve it?

the same problem:

wallet says: transaction <xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> was rejected by daemon with status "Failed"
daemon says: transaction verification failed:  <xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>

anybody who did any tx today?
Both GUI wallets (cryptonote/monero-qt) pulls "success tx" but realy it does not (there is no such tx in official blockchain)  

I got this when I tried to use an old daemon to broadcast a transaction. What I did was kill poolstate, p2pstate and my blockchain, and my wallet file (NOT the .keys file the other one) and then re download the blockchain and open the wallet again from the keys file (just type the orig wallet name) and then refresh the new wallet from start. This is prob overkill i think you only have to kill poolstate, but good practice if you've got general problems. I don't know if we have the same problem, but have you done the four above things yet?