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

[pa]

Does anyone know how to run the daemon with Tor on OS X? Care to share some tips?

[dEBRUYNE]

Does anyone know how to run the daemon with Tor on OS X? Care to share some tips?

Have you tried the instructions from the links in this thread?

https://www.reddit.com/r/Monero/comments/3wuls1/add_a_bit_of_info_about_using_bitmonerod_with_tor/

[pa]

Does anyone know how to run the daemon with Tor on OS X? Care to share some tips?

Have you tried the instructions from the links in this thread?

https://www.reddit.com/r/Monero/comments/3wuls1/add_a_bit_of_info_about_using_bitmonerod_with_tor/

This command seems to work to start bitmonerod (0.9.1 binary):

Code:

DNS_PUBLIC=tcp torsocks ~/monero.mac.x64.v0-9-1-0/bitmonerod --p2p-bind-ip 127.0.0.1

But when I run simplewallet using the usual command, refresh just hangs and there are error messages appearing in the daemon:

ERROR   {2} {p1} 2016-01-19 10:02:27.723574 [abstract_tcp_server2.inl+937 ::handle_accept] Some problems at accept: Bad address, connections_count = 1
[Jan 19 10:02:59] ERROR torsocks[54822]: General SOCKS server failure (in socks5_recv_connect_reply() at socks5.c:516)

Do I need to start simplewallet with torsocks too?

[medusa13]

since icebreaker deleted my post(and also an other one, forgot the username), i will leave it here:

A reply of yours, quoted below, was deleted by the starter of a self-moderated topic. There are no rules of self-moderation, so this deletion cannot be appealed. Do not continue posting in this topic if the topic-starter has requested that you leave.

You can create a new topic if you are unsatisfied with this one. If the topic-starter is scamming, post about it in Scam Accusations.

this thread was good. but after the current deletion session just a joke. there was no reason to delete the post of illodin since it was ontopic. all in all your behavior is not a good advertisement for monero, icebreaker. it just seems buthurt and immature.
hate me now, delete the post and flame me, but someone needs to say it. i am not the only one that thinks like this for sure, maybe others do not have the courage to speak up. this is also my coin and i was here before you. I am annoyed by this childish behavior, you guys damage the public impression regarding my investment and we soon reach the point where i can not tollerate this anymore.

just my opinion.

your (for now still) friendly monero whale from next door.

who do you think you are deleting my post like that? not even a try to justify?
people like you kill my love for monero and this community, its the most annoying thing right now. its not the dash trolls, its YOU!
no one elected you to be our small dog to bark out in the park in the name of monero. i dont like it and there are many more. if you like monero you should respect this, people like me provided liquidity 1.5 years ago so the coin is recognizable to fish brains like you.

monero has always been a currency with a commnunity strongly affiliated with things like intellect, foresight and intelligence - you massively hurt this image in public and therefore, hurt the coin itself

if you think you belong to this community: please come here and explain why you think your posts/threads help monero in any way. and if so, how?

we can talk about everything.

jsut dont refuse to talk and continue like nothing happend..this would not be wise, you should respect my concern (and i am not the first one telling you this)

[aiwe]

Concerning Wolf's AMD miner.

After two days of mining I can tell it is quite stable. Crashed only twice when Photoshop was using GPU too. It also takes 13% of CPU - i7 2600K during work.

It is too early, but judging from charts on dwarfpool, my personal hashrate is almost the same as it was before with rival miner.


P.S. We should have started own thread for this.

[iCEBREAKER]

There is a certain "academic approach" in Bitcoin from people like Adam Back (an actual academic in a sense) and Greg Maxwell that you have to appreciate. It involves developing small advancements (or small wins if you prefer that phrase) that are extremely well supported with research and mathematics, and is often focused on advancing knowledge in ways that won't even ever be deployed on a large scale.

That is very different from a more commercial approach that often tries to deliver a "solution" to "customers", but often delivers stuff that isn't very well supported or sound, and almost inevitably becomes obsolete and ultimately outcompeted or leapfrogged by some other commercial product.

Monero, by the way, has a somewhat intermediate approach (that is my observation and opinion, not a statement of policy).

Given a choice between startup-style 'failing fast' and crytographic best practices (which are by nature necessarily highly academic), I prefer Monero tend toward the latter approach.

I'm here for a new and improved (complement to) Bitcoin, not a fancier version of Apple Pay.

[novag]

What do you think Monero can be a major alternative to Bitcoin? All prerequisites are available.

[smooth]

Does anyone know how to run the daemon with Tor on OS X? Care to share some tips?

Have you tried the instructions from the links in this thread?

https://www.reddit.com/r/Monero/comments/3wuls1/add_a_bit_of_info_about_using_bitmonerod_with_tor/

This command seems to work to start bitmonerod (0.9.1 binary):

Code:

DNS_PUBLIC=tcp torsocks ~/monero.mac.x64.v0-9-1-0/bitmonerod --p2p-bind-ip 127.0.0.1

But when I run simplewallet using the usual command, refresh just hangs and there are error messages appearing in the daemon:

ERROR   {2} {p1} 2016-01-19 10:02:27.723574 [abstract_tcp_server2.inl+937 ::handle_accept] Some problems at accept: Bad address, connections_count = 1
[Jan 19 10:02:59] ERROR torsocks[54822]: General SOCKS server failure (in socks5_recv_connect_reply() at socks5.c:516)

Do I need to start simplewallet with torsocks too?

No.

Are you running simplewallet on the same system?

Strange that wouldn't work, several other people have used this and none have reported a problem.

[aiwe]

Not now, I did not bought it enough yet while it is still relatively cheap.

[dEBRUYNE]

Not now, I did not bought it enough yet while it is still relatively cheap.

Still pllenty available below 0.0015.

[novag]

I think tomorrow 0.002<

[iCEBREAKER]

Not now, I did not bought it enough yet while it is still relatively cheap.

Still pllenty available below 0.0015.

Plenty for plankton, minnows, and a few dolphins.

For a whale, much less a pod, not at all.

Also, this trollbox chatter should be in our Speculation thread.

*slaps own wrist, says 7 Hail Satoshis*

[Drhiggins]

So can someone tell me how the daemon is (-8days) ahead]

I think this daemons data may be corrupted.  I have this running on an old spindle HHD (slower than hell)  I have an SSD on the way and I think I'll just re-sync from scratch once installed but any Ideas why this message shows up?  My other open daemon is running fine with no errors on another machine.


2016-Jan-19 20:12:33.976115 [P2P6][31.6.70.206:34959 INC] SYNCHRONIZED OK
2016-Jan-19 20:12:33.976115 [P2P2][45.63.14.235:48551 INC] SYNCHRONIZED OK
2016-Jan-19 20:12:45.021900 [P2P7][107.170.19.65:42753 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:52.769040 [P2P3][217.118.66.161:41543 INC]Sync data returned u
nknown top block: 919725 -> 913363 [6362 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:53.972043 [P2P7][107.170.19.65:42756 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:59.248541 [P2P3][107.170.19.65:42758 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started

[smooth]

What does 'diff' show as your top block? Those may be messages about peers that are screwed up due to the earlier fork, and your node might be fine.

[luigi1111]

So can someone tell me how the daemon is (-8days) ahead]

I think this daemons data may be corrupted.  I have this running on an old spindle HHD (slower than hell)  I have an SSD on the way and I think I'll just re-sync from scratch once installed but any Ideas why this message shows up?  My other open daemon is running fine with no errors on another machine.


2016-Jan-19 20:12:33.976115 [P2P6][31.6.70.206:34959 INC] SYNCHRONIZED OK
2016-Jan-19 20:12:33.976115 [P2P2][45.63.14.235:48551 INC] SYNCHRONIZED OK
2016-Jan-19 20:12:45.021900 [P2P7][107.170.19.65:42753 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:52.769040 [P2P3][217.118.66.161:41543 INC]Sync data returned u
nknown top block: 919725 -> 913363 [6362 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:53.972043 [P2P7][107.170.19.65:42756 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:59.248541 [P2P3][107.170.19.65:42758 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started

You seem to be connected to a few naughty peers. I'd suggest spanking them. (107.170.19.65:42753 and below, note the others say "SYNCHRONIZED OK")

[Drhiggins]

So can someone tell me how the daemon is (-8days) ahead]

I think this daemons data may be corrupted.  I have this running on an old spindle HHD (slower than hell)  I have an SSD on the way and I think I'll just re-sync from scratch once installed but any Ideas why this message shows up?  My other open daemon is running fine with no errors on another machine.


2016-Jan-19 20:12:33.976115 [P2P6][31.6.70.206:34959 INC] SYNCHRONIZED OK
2016-Jan-19 20:12:33.976115 [P2P2][45.63.14.235:48551 INC] SYNCHRONIZED OK
2016-Jan-19 20:12:45.021900 [P2P7][107.170.19.65:42753 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:52.769040 [P2P3][217.118.66.161:41543 INC]Sync data returned u
nknown top block: 919725 -> 913363 [6362 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:53.972043 [P2P7][107.170.19.65:42756 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:59.248541 [P2P3][107.170.19.65:42758 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started

You seem to be connected to a few naughty peers. I'd suggest spanking them. (107.170.19.65:42753 and below, note the others say "SYNCHRONIZED OK")

Ok so just block them through the the daemon with the ban feature I assume?

[smooth]

So can someone tell me how the daemon is (-8days) ahead]

I think this daemons data may be corrupted.  I have this running on an old spindle HHD (slower than hell)  I have an SSD on the way and I think I'll just re-sync from scratch once installed but any Ideas why this message shows up?  My other open daemon is running fine with no errors on another machine.


2016-Jan-19 20:12:33.976115 [P2P6][31.6.70.206:34959 INC] SYNCHRONIZED OK
2016-Jan-19 20:12:33.976115 [P2P2][45.63.14.235:48551 INC] SYNCHRONIZED OK
2016-Jan-19 20:12:45.021900 [P2P7][107.170.19.65:42753 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:52.769040 [P2P3][217.118.66.161:41543 INC]Sync data returned u
nknown top block: 919725 -> 913363 [6362 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:53.972043 [P2P7][107.170.19.65:42756 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:59.248541 [P2P3][107.170.19.65:42758 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started

You seem to be connected to a few naughty peers. I'd suggest spanking them. (107.170.19.65:42753 and below, note the others say "SYNCHRONIZED OK")

Ok so just block them through the the daemon with the ban feature I assume?

Are you sure they aren't banned already? It should happen automatically but I'm not sure that every possible sort of bad peer behavior does get blocked. If it is the case that they escape the ban then yes you can ban them manually.

[Drhiggins]

So can someone tell me how the daemon is (-8days) ahead]

I think this daemons data may be corrupted.  I have this running on an old spindle HHD (slower than hell)  I have an SSD on the way and I think I'll just re-sync from scratch once installed but any Ideas why this message shows up?  My other open daemon is running fine with no errors on another machine.


2016-Jan-19 20:12:33.976115 [P2P6][31.6.70.206:34959 INC] SYNCHRONIZED OK
2016-Jan-19 20:12:33.976115 [P2P2][45.63.14.235:48551 INC] SYNCHRONIZED OK
2016-Jan-19 20:12:45.021900 [P2P7][107.170.19.65:42753 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:52.769040 [P2P3][217.118.66.161:41543 INC]Sync data returned u
nknown top block: 919725 -> 913363 [6362 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:53.972043 [P2P7][107.170.19.65:42756 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:59.248541 [P2P3][107.170.19.65:42758 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started

You seem to be connected to a few naughty peers. I'd suggest spanking them. (107.170.19.65:42753 and below, note the others say "SYNCHRONIZED OK")

Ok so just block them through the the daemon with the ban feature I assume?

Are you sure they aren't banned already? It should happen automatically but I'm not sure that every possible sort of bad peer behavior does get blocked. If it is the case that they escape the ban then yes you can ban them manually.

Ok cool, well its good to know someone is watching all these I.P.'s  There are some shady motherF$#@'s out there.  Will do and I'll keep an eye on my daemon's running.  Thanks for the help.

[oblox]

So can someone tell me how the daemon is (-8days) ahead]

I think this daemons data may be corrupted.  I have this running on an old spindle HHD (slower than hell)  I have an SSD on the way and I think I'll just re-sync from scratch once installed but any Ideas why this message shows up?  My other open daemon is running fine with no errors on another machine.


2016-Jan-19 20:12:33.976115 [P2P6][31.6.70.206:34959 INC] SYNCHRONIZED OK
2016-Jan-19 20:12:33.976115 [P2P2][45.63.14.235:48551 INC] SYNCHRONIZED OK
2016-Jan-19 20:12:45.021900 [P2P7][107.170.19.65:42753 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:52.769040 [P2P3][217.118.66.161:41543 INC]Sync data returned u
nknown top block: 919725 -> 913363 [6362 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:53.972043 [P2P7][107.170.19.65:42756 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started
2016-Jan-19 20:12:59.248541 [P2P3][107.170.19.65:42758 INC]Sync data returned un
known top block: 919725 -> 913265 [6460 blocks (-8 days) ahead]
SYNCHRONIZATION started

You seem to be connected to a few naughty peers. I'd suggest spanking them. (107.170.19.65:42753 and below, note the others say "SYNCHRONIZED OK")

Ok so just block them through the the daemon with the ban feature I assume?

Noticed the same thing on a Win7 9.1 build today. These are the peers I have banned:

[Drhiggins]

So it looks like the defacto ban period set in the daemon is 24 hours.