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

When can pool diggers?

For sure it is:)

Remember to vote for monero on swaphole!
https://www.swaphole.com/#!voting

(copy the whole link, simple machines forum breaks the links with a #)

I feel this coin is different from the other coins , I'll buy some and hold

A few of them are no big deal. Nothing really bad will happen if the error occurs while you are sleeping. Just restart it if you see a lot of them.

Orphans are normal. It doesn't mean that your block from mining was necessarily orphaned, it may be (and usually is) just some orphan from the network. That is an expected part of how block chains work and the reason why multiple confirmations are required.

when i check the log , i found there's many orphans in there, and also some network error, so what can i do ? why there's so many orphans? maybe there are more than 5 orphans at least, here's a part of my log:

2014-May-12 09:24:20.188696 [P2P8]ERROR /root/bitmonero/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-May-12 09:24:20.188772 [P2P8]ERROR /root/bitmonero/contrib/epee/include/net/levin_protocol_handler_a
sync.h:515 [54.187.205.25:18080 OUT]Failed to do_send
2014-May-12 09:24:20.188982 [P2P8]ERROR /root/bitmonero/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-May-12 09:24:20.189038 [P2P8]ERROR /root/bitmonero/contrib/epee/include/net/levin_protocol_handler_a
sync.h:515 [108.61.194.121:18080 OUT]Failed to do_send
2014-May-12 09:24:20.189407 [P2P8]ERROR /root/bitmonero/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-May-12 09:24:20.189468 [P2P8]ERROR /root/bitmonero/contrib/epee/include/net/levin_protocol_handler_a
sync.h:515 [140.180.190.181:18080 OUT]Failed to do_send
2014-May-12 09:24:20.318269 [P2P5]Block recognized as orphaned and rejected, id = <09e2e9c7e10ce84a266788
0d40a344489bb894c5163c4126b8bfd5be51226001>
2014-May-12 09:24:20.527331 [P2P1]Block recognized as orphaned and rejected, id = <09e2e9c7e10ce84a266788
0d40a344489bb894c5163c4126b8bfd5be51226001>
2014-May-12 09:24:21.598271 [P2P5][212.234.243.195:18080 OUT] SYNCHRONIZED OK
2014-May-12 09:24:21.989431 [P2P7]ERROR /root/bitmonero/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-May-12 09:24:21.989538 [P2P7]ERROR /root/bitmonero/contrib/epee/include/net/levin_protocol_handler_a
sync.h:638 [60.178.228.189:18080 OUT]Failed to do_send()
2014-May-12 09:24:21.989586 [P2P7]ERROR /root/bitmonero/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-May-12 09:24:21.989656 [P2P7]ERROR /root/bitmonero/contrib/epee/include/net/levin_protocol_handler_a
sync.h:638 [24.60.203.161:18080 OUT]Failed to do_send()

It won't break your daemon but it does cause extra connections to be opened. If you see a lot of them it is best to restart your daemon.

The is only one coin/chain.

EDIT: btc-mike, my comment wasn't specifically addressed toward your comment, but there most certainly are organized FUD and puppet campaigns. They've been continuous since BCN appeared. What frequently happens is innocent third parties don't realize it is fake and end up responding to and repeating the same stuff the puppets are posting. Since we can't shut down (or even definitively identify) the 30+ sock puppet accounts, it is best to just ignore them on move forward with building a useful coin.

The previous quote was posted in the Quazar thread by me. It was not a part of any FUD campaign, just my understand of things at the time. I now see that TFT is the problem.

Question: Are both coins using the same chain?

I think you're doing a fantastic job at mitigating the effect. The recent spike in November and December with BTC has brought on a plethora of new people who are trying to find their place in this community now that initial expectations are not quite matching up with reality. I would imagine that many have left, but the few that remain are still settling amongst the turbulent landscape.

I'm one of them. But instead, what I've found in spite of the initial expectations is something that I can now call a hobby. A vested personal interest rather than a simple business decision, something to expand my horizons. I've come to see that people like you, and a few others like you, are people I feel comfortable listening to .. people that I can take direction and learn from. Thanks for keeping us pointed in the right direction.

 Don't know why but after updating I can't access my wallet.

It is reasonably well explained here: https://bitcointalksearch.org/topic/m.6645981

It is odd given TFT's sentiments about the name change (linked above, quoted below) and hard forks these questions are still being asked again and again, but you have to understand that the world of cryptocoins has become rampant with FUD campaigns, puppet accounts and all sort of dirty tricks. It is sad that people want to operate that way instead of focusing on building the best technology and products, but there is nothing we can do about it, except minimize the disruption they cause. Fortunately most of their efforts are pretty transparent and ineffective (see comments a page or two back on this thread, or better yet don't).

Can somebody explain the difference between BitMonero and Monero and what happened in the past?

found this...

https://cryptonote.exchange.to

Please someone message me I want to buy more monero, I will pay on the high end

I don't have any feedback so we can do escrow or whatever the formal sell procedure is

Just for curiosity's sake has anyone encountered a problem with opening their wallets due to an incorrect password? I did not set a password when I made the wallet a few days ago, but now it tells me the password is wrong when I try to open it. Not a huge deal since there's only 1 block worth on there but it's kinda annoying all the same.

With today's update, blockchain sync, hashing and mining are much faster on Core 2 (is anyone still using Core 2's?). Does this hold for other arches?

I also was not able to download from this site, after I protected my Firefox with add-ons ghostery and noscript. mega wants to have write access to your system. I use a separate Live-System in a VM on SSD for this risky access.

I can't download the wallet from mega !

Thank you