-
Maxattax
if you buy monero on a kyc exchange, does that not just totally defeat the purpose of kyc?
-
Maxattax
1. join kyc exchange
-
Maxattax
2. buy xmr
-
Maxattax
3. transfer to wallet offsite
-
Maxattax
4. exchange xmr to anything else on another non-kyc exchange
-
Maxattax
5. call it a loss or say you bought something with the xmr
-
Maxattax
6. profit (untraceable monies?????)
-
gingeropolous
naw, the bank, er exchange, did what they had to do.
-
Maxattax
gingeropolous: they fulfilled kyc, but could the feds really come after you at that point?
-
gingeropolous
i dunno. i never think its a wise idea to try and food the taxmen. unless of course your a billionaire, then you can do it with legal crap and make it too costly for them.
-
bonedaddy
running monero-wallet-gui from the cli and letting it run eventually gives me an error `E Failed to fetch and verify signed hash: signature checksum doesn't match the expected value`
-
bonedaddy
never seen this before, and i've used this version of monero-wallet-gui a number of times before
-
selsta
bonedaddy: getmonero.org cert is expired, should be fixed in a couple hours
-
bonedaddy
makes sense, thanks
-
selsta
error should go away afterwards
-
sixStringHobo
here i am looking it up and double checking to make sure before I posted about it
-
sixStringHobo
-
sixStringHobo
thought someone trying something naughty
-
shabash
my client keeps getting stuck on 2 daemon blocks remaining
-
shabash
sometimes briefly going to 1 but then back to 2
-
shabash
is it a problem with my computer/network?
-
selsta
shabash: do you run your own daemon?
-
selsta
also CLI or GUI?
-
shabash
-
shabash
no selsta
-
shabash
GUI
-
selsta
-
shabash
sorry selsta I misinterpreted your first question
-
shabash
yes I was running local node
-
selsta
-
selsta
follow this guide
-
shabash
it does not connect to node.xmr.to
-
shabash
does it need daemon username or password?
-
shabash
I followed the "If you run Simple mode" instructions
-
shabash
it just says network status connecting
-
shabash
let me try another remote node
-
selsta
88.198.199.23:18081 works
-
selsta
but you can just use your own guide by adding the ban list
-
selsta
your own node*
-
shabash
so far so good with the block list
-
dgoddard__
I'm doing fine on 0.17.1.7 with selsta's banlist. One interesting IP got automatically blocked and unlocked
-
dgoddard__
2020-12-16 04:03:49.010 I Host 100.19.74.83 blocked.
-
dgoddard__
2020-12-17 04:38:47.814 I Host 100.19.74.83 unblocked.
-
kloinka
MyI GUI wallet got stuck, updating my remote node fixed it.
-
shabash
idk I couldn't connect to 2 different remote nodes
-
shabash
maybe I wasn't doing something right
-
selsta
no, looks like the issue were on the nodes side
-
kloinka
Check version running on node?
-
kloinka
I use my own remote node in-house 😎
-
shabash
the new client on windows is very pretty
-
shabash
thank you for maintaining the block list selsta
-
scudyreal
All you are fighting for is e-penis of a guy you never met, that doesn't even have common decency to pay you for your time.
-
scudyreal
Do you think they care about Monero, or privacy or anything other than money?
-
fluffypony
jess: ^^
-
» jess rolls out of bed
-
fluffypony
LOL apologies
-
jess
no we need fireice to stop waking up before me
-
p3rL
fluffypony wen xmr pump sir
-
fluffypony
p3rL: never
-
p3rL
then make it dump :D
-
p3rL
xmriers wanna see something new
-
Mochi101
fluffypony, I found the video of what was going on right before your boating accident:
youtu.be/j--SsrgSF9I
-
fluffypony
LOL
-
dgoddard__
I'm guessing 45.140.176.144 is now on selsta's blocklist ;) fireice is now using IPs from Saudi Arabia telcom. I wonder if he's on that IP legally....
-
selsta
is it on my block list?
-
selsta
how did you get that IP?
-
dgoddard__
It's the one that was used a few hours ago talking about epenises and BADCACA
-
dgoddard__
"scudyreal"
-
selsta
these are botnet IPs
-
dgoddard__
ok
-
selsta
I don’t bother adding as they don’t seem to be used for monero
-
dgoddard__
:+1
-
anchor[m]
this is why I hope blacklists aren't going to be the "fix"
-
anchor[m]
it's just poor mitigation and turns into cat & mouse
-
selsta
what is the alternative in the short term?
-
selsta
we can’t get the whole network to update quickly
-
anchor[m]
I'm no programmer or cryptographer but if it's this easy to attack the monero network I'm honestly baffled
-
selsta
how do you know it is "easy"?
-
anchor[m]
Because it's a child doing it
-
selsta
we have a fix for it included in v0.17.1.7, but the majority of network has to update to it
-
selsta
which will take a while
-
anchor[m]
Didn't they say the same about .6?
-
selsta
no
-
selsta
.6 contained mitigations against the specific attack he was doing
-
selsta
which he changed afterwards
-
dgoddard__
A child can do SQL injection, you'd be surprised how many Fortune500 companies had their entire source code pwoned by Aurora
-
anchor[m]
<selsta ".6 contained mitigations against"> I see
-
selsta
the problem is a bit of information asymmetry, he can see what we are developing on github and has multiple days to find ways to circumvent it before we release
-
selsta
we can’t see what he is preparing obviously
-
moneromooo
People seem to get the wrong idea, which might be the point. The network's fine.
-
selsta
yea, this is mostly a GUI specific DoS because the GUI expects the daemon to be synched before transacting
-
dgoddard__
Running 0.17.1.17, did I find a new kind of Bad Node? 2020-12-17 17:10:05.919 I Host 159.89.121.89 blocked.
-
dgoddard__
2020-12-17 18:36:53.143 I [88.99.83.181:33204 INC] Sync data returned a new top block candidate: 2254342 -> 2254340 [Your node is 2 blocks (4.0 minutes) ahead]
-
dgoddard__
2020-12-17 18:36:53.143 I SYNCHRONIZATION started
-
dgoddard__
2020-12-17 19:44:49.380 W ge_frombytes_vartime failed at 415
-
dgoddard__
IP not in selsta's list
-
dgoddard__
How can I figure out which peer is saying the false blockheight?
-
sethsimmons
sync_info
-
dgoddard__
ty
-
dgoddard__
I assume height 1 means "newly syncing"? I also see a few sort of randomly lower than I have, presumably that height being where they are at in the syncing process
-
moneromooo
I think they're typically nodes that are set to not sync. Those should probably be dropped after a peer list is sent.
-
dgoddard__
yep, they (those at height 1) drop off after peer list
-
dgoddard__
ty