Pages:
Author

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

member
Activity: 342
Merit: 24
Bittrex delisted Monero along with ZCash and Dash which was a weird decision sparking concerns about a regulator crackdown on privacy coins.
Monero is known to have the best privacy and we have also read previously about the IRS hiring Chainalysis to find a way to trace the transactions.

Can Bittrex know something others don't or acted before anyone else for their own reasons? Will Monero be delisted by more exchanges? Price drops and I'll be waiting to buy.
legendary
Activity: 3570
Merit: 1959
We all know the benefits of Monero and expect better prospects in the future, but apparently the government is very serious about creating problems. Recently, the media mentioned that the analytical company CipherTrace was able to track Monero transactions and this tool was created by order of the US Department of Homeland Security. In addition, the very popular ShapeShift platform, which allowed exchanging cryptocurrencies anonymously in order to avoid legal problems, delisted Monero. The impression is that something is not good.

I found this very helpful and interesting, and no I don't work here or any bullshit hahaha

https://www.coindesk.com/spagni-fluffypony-monero-cryptographers-one-step-ahead-regulators
full member
Activity: 1316
Merit: 108
We all know the benefits of Monero and expect better prospects in the future, but apparently the government is very serious about creating problems. Recently, the media mentioned that the analytical company CipherTrace was able to track Monero transactions and this tool was created by order of the US Department of Homeland Security. In addition, the very popular ShapeShift platform, which allowed exchanging cryptocurrencies anonymously in order to avoid legal problems, delisted Monero. The impression is that something is not good.
full member
Activity: 1179
Merit: 210
only hodl what you understand and love!
legendary
Activity: 2268
Merit: 1141
CLI & GUI v0.17.1.8 'Oxygen Orion' released (includes patch for memory exhaustion attack)!

https://www.reddit.com/r/Monero/comments/kncbj3/cli_gui_v01718_oxygen_orion_released_includes/
sr. member
Activity: 582
Merit: 250
Owns of Waya Wolf Coin - WW Supports the Wolf Park
Hello All,

I love this Monero Coin!! I have been trading for a while now, but like mentioned, it seems to be undervalued and I am bagging the coin. 

Best wishes for the upcoming New Year!!

CHeers,
Waya
legendary
Activity: 2702
Merit: 2053
Free spirit
Lord, hear our prayers!


and by the way there is a thread for price speculation here.

https://bitcointalksearch.org/topic/xmr-monero-speculation-753252


many thanks,
legendary
Activity: 3570
Merit: 1959
With out reading all the posts above i am wondering if XMR price movement is as tied to Bitcoin like Ethereum is ?
It has been doing well the last 3 months its good to see this coin is still strongly used - payment ; mining ; plenty nodes on the network etc...


Personally I tend to think it sticks more to USDT. I also think it is and has been way undervalued for quite some time.
newbie
Activity: 84
Merit: 0
With out reading all the posts above i am wondering if XMR price movement is as tied to Bitcoin like Ethereum is ?
It has been doing well the last 3 months its good to see this coin is still strongly used - payment ; mining ; plenty nodes on the network etc...
legendary
Activity: 2268
Merit: 1141
Please try applying the ban list:

1. Download this file and place it in the same folder as `monerod` / `monero-wallet-gui`: https://gui.xmr.pm/files/block_tor.txt

2. Go to the `Settings` page -> `Node` tab.

3. Enter
Code:
--ban-list block_tor.txt
in `daemon startup flags` box.

4. Restart the GUI (and daemon).


Oh wow, thank you, I have been having this issue for a while now and I always just resort to the CLI since I was thinking it was just me. Will try this and update shortly, thanks as always dEBRUYNE! Smiley

You're welcome Smiley
legendary
Activity: 3570
Merit: 1959
Please try applying the ban list:

1. Download this file and place it in the same folder as `monerod` / `monero-wallet-gui`: https://gui.xmr.pm/files/block_tor.txt

2. Go to the `Settings` page -> `Node` tab.

3. Enter
Code:
--ban-list block_tor.txt
in `daemon startup flags` box.

4. Restart the GUI (and daemon).


Oh wow, thank you, I have been having this issue for a while now and I always just resort to the CLI since I was thinking it was just me. Will try this and update shortly, thanks as always dEBRUYNE! Smiley

Update - works like a charm, thanks so much again! Smiley 
legendary
Activity: 2268
Merit: 1141

I restored from seed on the latest GUI v0.17.1.7 to be a cold wallet in an offline machine. I then generated a view-only wallet from it which I synced in an online machine. My balance is off. All transactions shown are "Received" (green dots). I was able to identify a recent "Send" transaction that is indicated as "Received" (green dot) so I assume the rest of my outputs over a few years (which I am unable to identify) are the same. I shouldn't complain since my balance is a bit more than it should be but I know this is gonna haunt me later down the line. Did I miss a step in setting up this cold/view-only wallet? What gymnastics do I have to do to resolve this issue?


Try exporting the key images from the offline wallet and subsequently importing them in the hot wallet. See (5):

https://github.com/monero-ecosystem/monero-GUI-guide/blob/master/monero-GUI-guide.md#send-monero

Furthermore, several seconds after GUI v0.17.1.7 Wallet and Daemon fully sync, it would go back to syncing mode again with "Daemon blocks remaining: 2". Sometimes, it would drop to "1" momentarily then goes back up to "2" again but would never fully sync again from here on.

Please try applying the ban list:

1. Download this file and place it in the same folder as `monerod` / `monero-wallet-gui`: https://gui.xmr.pm/files/block_tor.txt

2. Go to the `Settings` page -> `Node` tab.

3. Enter
Code:
--ban-list block_tor.txt
in `daemon startup flags` box.

4. Restart the GUI (and daemon).
legendary
Activity: 2268
Merit: 1141
I have been fighting this attack for days. The only way I can keep my node running is to restart it every hour or so, even with the block list.  I have conceded defeat and  shut down. Hoping for a fix in an updated release, but the effectiveness of this attack is certainly worrisome.

Do you know how to compile a binary? If so, please compile a binary from the `release-v0.17` branch.

https://github.com/monero-project/monero#compiling-monero-from-source

Add
Code:
-b release-v0.17
to clone (and subsequently compile) the proper branch.
full member
Activity: 1179
Merit: 210
only hodl what you understand and love!
I have been fighting this attack for days. The only way I can keep my node running is to restart it every hour or so, even with the block list.  I have conceded defeat and  shut down. Hoping for a fix in an updated release, but the effectiveness of this attack is certainly worrisome.

Just built a script in crontab to kill all hourly, update the tor list from github and restart all again  Wink

My script seems to work, which kills all monerod processes every hour and restarts that every hour and minute

1. I built a srcipt that is called every hour and one minute in the crontab
Code:
#!/bin/bash
rm -fR torbulkexitlist
wget https://check.torproject.org/torbulkexitlist
cd /home/user/monero-x86_64-linux-gnu-v0.17.1.7
sudo -u user ./monerod --detach --rpc-bind-ip 0.0.0.0 --confirm-external-bind --hide-my-port --ban-list /home/user/torbulkexitlist
exit 0

2. in /etc/crontab i added two lines
Code:
0 *    * * *    root    killall -15 monerod
1 *    * * *    user    /home/user/monerorestart.bash &>/dev/null

Still after 45min my memory is more or less exhausted, so the ban list does not seem to do what it is supposed to, but it's worth the try


EDIT: Updated the download of TOR exit relays with the TOR own list --> https://check.torproject.org/torbulkexitlist
EDIT 1: Changed killall -9 to killall -15, not to hurt the DB more than i have to do

Doing good today, after 50 minutes online in the cycle my memory is looking good and also the CPU's are working on normal level


Has the attack ended or is it just the low transaction count that drives this?
full member
Activity: 1179
Merit: 210
only hodl what you understand and love!
I have been fighting this attack for days. The only way I can keep my node running is to restart it every hour or so, even with the block list.  I have conceded defeat and  shut down. Hoping for a fix in an updated release, but the effectiveness of this attack is certainly worrisome.

Just built a script in crontab to kill all hourly, update the tor list from github and restart all again  Wink

My script seems to work, which kills all monerod processes every hour and restarts that every hour and minute

1. I built a srcipt that is called every hour and one minute in the crontab
Code:
#!/bin/bash
rm -fR torbulkexitlist
wget https://check.torproject.org/torbulkexitlist
cd /home/user/monero-x86_64-linux-gnu-v0.17.1.7
sudo -u user ./monerod --detach --rpc-bind-ip 0.0.0.0 --confirm-external-bind --hide-my-port --ban-list /home/user/torbulkexitlist
exit 0

2. in /etc/crontab i added two lines
Code:
0 *    * * *    root    killall -15 monerod
1 *    * * *    user    /home/user/monerorestart.bash &>/dev/null

Still after 45min my memory is more or less exhausted, so the ban list does not seem to do what it is supposed to, but it's worth the try


EDIT: Updated the download of TOR exit relays with the TOR own list --> https://check.torproject.org/torbulkexitlist
EDIT 1: Changed killall -9 to killall -15, not to hurt the DB more than i have to do
legendary
Activity: 1081
Merit: 1001

I restored from seed on the latest GUI v0.17.1.7 to be a cold wallet in an offline machine. I then generated a view-only wallet from it which I synced in an online machine. My balance is off. All transactions shown are "Received" (green dots). I was able to identify a recent "Send" transaction that is indicated as "Received" (green dot) so I assume the rest of my outputs over a few years (which I am unable to identify) are the same. I shouldn't complain since my balance is a bit more than it should be but I know this is gonna haunt me later down the line. Did I miss a step in setting up this cold/view-only wallet? What gymnastics do I have to do to resolve this issue?

Furthermore, several seconds after GUI v0.17.1.7 Wallet and Daemon fully sync, it would go back to syncing mode again with "Daemon blocks remaining: 2". Sometimes, it would drop to "1" momentarily then goes back up to "2" again but would never fully sync again from here on.

full member
Activity: 1179
Merit: 210
only hodl what you understand and love!
I have been fighting this attack for days. The only way I can keep my node running is to restart it every hour or so, even with the block list.  I have conceded defeat and  shut down. Hoping for a fix in an updated release, but the effectiveness of this attack is certainly worrisome.

Just built a script in crontab to kill all hourly, update the tor list from github and restart all again  Wink
newbie
Activity: 56
Merit: 0
I have been fighting this attack for days. The only way I can keep my node running is to restart it every hour or so, even with the block list.  I have conceded defeat and  shut down. Hoping for a fix in an updated release, but the effectiveness of this attack is certainly worrisome.
full member
Activity: 1179
Merit: 210
only hodl what you understand and love!
full member
Activity: 1179
Merit: 210
only hodl what you understand and love!
the same with bitmonero.log log level 3

You probably have another instance running. I see this in your log:
Code:
2020-12-26 16:25:02.558     7f2b41bcb780        ERROR   net     contrib/epee/include/net/abstract_tcp_server2.inl:1023  Failed to bind IPv4: bind: Address already in use
2020-12-26 16:25:02.558     7f2b41bcb780        FATAL   net     contrib/epee/include/net/abstract_tcp_server2.inl:1072  Error starting server: Failed to bind IPv4 (set to required)

Restart the computer and try again.

As i see that, monerod is trying to restart itself, but failing. I do not have any other monerod running, but thank you for your comment  Wink
Pages:
Jump to: