It looks like there is some sentiment around 0.012.
It was some critical FIB level but now its broken pretty hard. Where is the next strong support , around 0.007xx?? 0.0111 (old ATH), which is also approximately the 68.2% retracement level if you draw from the low (0.0016x) to the high (0.0265). If that breaks there will probably be psychological suppport at 0.01. |
|
|
|
Did you gracefully exit monerod? Because the bans should be saved then. You can gracefully exit by typing "exit" into monerod. Thus, gracefully exit and restart monerod should do the trick.
I was, but I try once again. Tried, and nothing, you are wrong. Apparently bans do not get saved. There's a patch coming to fix your issue, as far as I know. |
|
|
|
The node will be banned upon restarting monerod.
How do you know that? After restart bans is empty. Help tells nothing about it. Did you gracefully exit monerod? Because the bans should be saved then. You can gracefully exit by typing "exit" into monerod. Thus, gracefully exit and restart monerod should do the trick. |
|
|
|
I've baned 89.108.104.135 but it looks like ban has no efect, why? 2016-Oct-02 13:27:19.171203 [P2P5][77.119.242.22:18080 OUT]Synced 1030793/1148631
bans
46.163.76.25 banned for 86194 seconds
192.99.5.100 banned for 85920 seconds
95.93.190.100 banned for 85866 seconds
89.108.104.135 banned for 86074 seconds
45.79.84.193 banned for 85839 seconds
46.23.158.207 banned for 85889 seconds
2016-Oct-02 13:27:59.318989 [P2P6][77.119.242.22:18080 OUT]Synced 1030993/1148631
2016-Oct-02 13:28:18.321372 [P2P9][77.119.242.22:18080 OUT]Synced 1031193/1148631
2016-Oct-02 13:28:31.599284 [P2P3][89.108.104.135:18080 OUT]Synced 1031393/1148631
2016-Oct-02 13:28:42.647752 [P2P6][89.108.104.135:18080 OUT]Synced 1031593/1148631
2016-Oct-02 13:29:01.581068 [P2P1][89.108.104.135:18080 OUT]Synced 1031793/1148631
2016-Oct-02 13:29:12.801195 [P2P5][89.108.104.135:18080 OUT]Synced 1031993/1148631
2016-Oct-02 13:29:21.372872 [P2P1][89.108.104.135:18080 OUT]Synced 1032193/1148631
2016-Oct-02 13:29:39.086927 [P2P5][89.108.104.135:18080 OUT]Synced 1032393/1148631
2016-Oct-02 13:30:03.863995 [P2P5][89.108.104.135:18080 OUT]Synced 1032593/1148632
2016-Oct-02 13:30:10.374794 [P2P9][89.108.104.135:18080 OUT]Synced 1032793/1148632
The node will be banned upon restarting monerod. |
|
|
|
due to personal business I could not gather any news from the last 2 meetings. What happened there ?? please share with us in short. The meeting of last week was postponed to this week. The logs of the meeting(s) before that can be read here: https://getmonero.org/blog/ |
|
|
|
i use xmr.to exchange yesterday but my btc did not arrive until now. anybody here we can contact for help? first time try for the exchange and having hard time to use the simple wallet make me confused. please help.
You a not alone... you have same experience also? Be patient, I am sure they will respond soon. Bear in mind that the guys running it probably also have day jobs. |
|
|
|
Fluffypony is busy fixing it. |
|
|
|
Oups, how could i miss to post that  GUI should be ready soon: <fluffypony> Kermit_: do you mean the GUI wallet, or the next tagged release? <Kermit_> Yes gui <kintaji> fluffypony - Okay. Just to say there are some oddities with the current flag page. Can expand at a later time. <fluffypony> Kermit_: not certain yet - I'll look at building beta binaries in the next week or so <Kermit_> Thanks https://getmonero.org/2016/09/11/overview-and-logs-for-the-dev-meeting-held-on-2016-09-11.htmlThat was from over 2 weeks ago. If you have been following things you'll know that fluffypony is not doing the beta binaries because there are still bugs. Yes there is information all over the place so it's sometimes hard to keep track. Just yesterday there were some GUI commits. As far as I know he means the issues reported by medusa, which you can see here: https://github.com/monero-project/monero-core/issuesAs far as I can see from the commits, all issues have been fixed except #26. Also, not sure about #29, but that's more a feature than a bug. |
|
|
|
Fluffypony is busy fixing it. |
|
|
|
|
Show Posts
