00:00:10 <monerofanboy> Tor and i2p bring in all sorts of legal concerns, especially tor entrance and 1000% for tor exit nodes.
00:02:49 <Inge-> whats up with Erik Vorhees - https://twitter.com/ErikVoorhees/status/1345100565735378947?s=19
00:03:07 <kinghat[m]> never had an issue on hetzner with noisy neighbor. also told me you can host all the network nodes, basically.
00:03:32 <M5M400> node.supportxmr.com was running fine for 2 years on a hetz vps
00:03:44 <M5M400> but nodes only need bandwith
00:03:48 <kinghat[m]> legal concerns for TOR exit nodes? i think there is a bunch of libraries that host exit nodes here in the US
00:04:19 <kinghat[m]> M5M400: ya thats why i went with hetz because bandwidth.
00:04:48 <kinghat[m]> just looking to get something closer to me because of the latency.
00:04:56 <monerofanboy> yes, huge legal concerns for running a tor exist node in the US.
00:05:34 <kinghat[m]> there are exit nodes in the us. like i said, i think there are libraries that run some here.
00:06:43 <kinghat[m]> also all the i2p traffic is encrypted and there is no practical exiting of the i2p network
00:07:01 <monerofanboy> If I remember correctly, I believe in a youtube videos in which they specifically state to form an llc if hosting a tor exist node, to avoid the police searching your personal computers if pedo stuff is detected from the out-going node.
00:07:08 <sethsimmons> <Inge- "whats up with Erik Vorhees - htt"> Very odd
00:07:19 <sethsimmons> His whole approach to the ShapeShift delisting was weird
00:07:31 <sethsimmons> https://twitter.com/sethisimmons/status/1345124584186634245?s=21
00:09:56 <monerofanboy> Tor lists hetzner, DO, OVH, and Online s.a.s. as providers to avoid, so idk why you would knock ovh for not wanting a tor exist node when hetzner apparently does not want them either.
00:13:24 * zed19[m] uploaded an image: download (2).jpeg (68KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/zZvlSaJuAxanyPDdGkYfCawJ/download (2).jpeg >
00:19:22 <kinghat[m]> im just saying OVH doesnt want any type of nodes, not just TOR. no I2P or crypto. hetzner says go right ahead with I2P and crypto.
00:19:30 <kinghat[m]> ive never ran a TOR node.
00:55:14 <maraga> hello
00:55:17 <maraga> happy new year
00:56:41 <maraga> is possible to choose a specific tx on pool for mining
01:00:00 <slighty_toasted> If you're the one running the daemon which the pool is mining on, definitely.
01:00:25 <maraga> yes im
01:00:37 <maraga> the command?
01:01:03 <maraga> i checked help all on cli but didnt find smth
01:01:12 <slighty_toasted> I'm not sure it's as easy as a single command
01:01:35 <Inge-> sethsimmons: https://old.reddit.com/r/xmrtrader/comments/ko9s3k/daily_discussion_friday_january_1st/ghrygd3/
01:11:28 <slighty_toasted> https://www.reddit.com/r/Monero/comments/kom0hv/torserversnet_but_for_monero_nodes/
01:11:39 <slighty_toasted> Any thoughts and concerns would be appreciated
01:12:58 <sethsimmons> <Inge- "sethsimmons: https://old.reddit."> Thanks will read
01:19:02 <monerofanboy> "im just saying OVH doesnt want any type of nodes, not just TOR. no I2P or crypto."  Than you should report to OVH the 50 OVH IPs that the attacker is using on OVH's network...... If OVH does not do anything about those attacking nodes, OVH is not going to complain about a person running a legit crypto node on their network.
01:19:58 <maraga> is monero going down because of this attacks?
01:20:06 <maraga> monero price i mean
01:21:53 <slighty_toasted> maraga: Nope. https://www.reddit.com/r/Monero/comments/koexu5/montero_delisted_from_bittrex_on_jan_15th_thats/
01:22:59 <maraga> that is not a serius thing.there is allways bisq as solution
01:23:45 <maraga> and i believe that negative news are positive news for monero
01:26:27 <maraga> anyone to help on how to choose tx for mining?
01:53:03 <dgoddard> "tx" for mining? You choose a mining pool, and if you want a dedicated rig for it, a rig. Nothing else to choose AFAIK
02:43:46 <zed19[m]> bittrex is trash anyway
02:44:15 <zed19[m]> bimbos
02:50:01 <aum> XMR in freefall -- is there any specific news triggering that?
02:51:08 <selsta> bittrex delisting caused panic
02:51:42 <hyc> moronic since bittrex xmr volume was near zero already
02:52:15 <hyc> dunno how anyone can believe free markets are so great when investors are so irrational
02:52:38 <nioc> mebbe that's why :)
02:54:32 <camalonso> just some random traders dumping. I just hope not many exchanges follow.
03:02:01 <nioc> there is no reason for them to follow
03:02:22 <nioc> bittrex has had issues for a long time that lead to this
03:03:20 <zed19[m]> now i can buy some moneroooo
03:09:50 <aum> righto, good time to bottom-pick and quadruple my position then :)
03:10:21 <aum> did bittrex cop a squeeze from regulators?
03:10:43 <nioc> there was no explanation
03:11:18 <nioc> just have to infer based of the past history
03:11:40 <nioc> based on past***********
03:12:26 <nioc> reposting link  https://old.reddit.com/r/xmrtrader/comments/ko9s3k/daily_discussion_friday_january_1st/
03:12:45 <nioc> https://twitter.com/jespow/status/1345117102009536512
03:18:32 <dgoddard> @nioc : "Tweet
03:18:32 <dgoddard> See new Tweets
03:18:32 <dgoddard> This is not available to you"
03:19:06 <nioc> did you try reloading
03:19:31 <nioc> sometimes tweets don't load the first time
03:19:58 <nioc> I haz no tweeter account
03:20:47 <ndorf> WTF, bittrex
03:22:53 <nioc> ndorf: I was kicked off of bittrex, mebbe a year or more ago, because the NY regulators didn't like that they were still allowing people like Mickey Mouse to sign up after they were warned to get their house in order
03:24:32 <dgoddard> Reload worked.
03:24:36 <nioc> \o/
03:24:58 <nioc> ndorf: Happy New Year!!!
03:26:16 <ndorf> nioc: oof, haha.
03:26:25 <ndorf> i think i will close my bittrex account citing monero delisting as the reason
03:26:33 <ndorf> and happy New Year to you as well!
03:28:56 <aum> as long as kraken keeps XMR open
03:31:30 <ndorf> kraken is great. it sucks to have only one exchange to rely on though
03:32:31 <h2017> ndorf it'll be better soon because litecoin will have mimblewimble and then it's going to be harder for exchanges to get rid of privacy coins
03:32:50 <h2017> i guess this discussion really belongs on xmrtrader right?
03:32:58 <h2017> i mean #Monero-markets
03:33:09 <ndorf> i mean, they might be okay with the weak ass privacy of mimblewimble but not the stronger privacy of monero
03:33:48 <ndorf> maybe, i dunno. i assume if someone is bothered by this conversation they'll let us know :)
03:33:59 <h2017> true. it's not my place to tell people what to do
03:34:04 <h2017> not my chan
03:34:27 <h2017> but i'll be respectful and  only talk about market stuff on #monero-markets
03:36:19 <nioc> ndorf: grin was also delisted
04:03:52 <Beags[m]> way I see it, monero being delisted = more competition on localmonero
04:05:34 <Beags[m]> would be nice to minimize the nokyc premium
04:13:42 <theircuser> Right, but I'll start to get a bit worried about localmonero later on. I don't think Monero is going to be delisted from all exchanges, but if so, then it'll be matter of time until the feds start to have a big problem with localmonero
04:17:43 <theircuser> As for kyc or nokyc, matter of time until it starts to get abused hard and becomes practically useless https://wilderko.medium.com/how-does-kyc-aml-pose-a-serious-threat-to-your-privacy-and-should-not-be-used-at-all-88f7acd3f3b
04:38:44 <Beags[m]> what country is local monero hosted in?
09:24:30 <tficharmers> Beags[m]: Hong Kong I think. Might be wrong.
09:43:40 <hatchproject> jess: I can tell you why you can't stop the 'spam'. You are thinking in cult doctrine. If it was real spam, and I was selling Viagra for example - you could easily ban keywords and urls. Instead, stop being a sheep, think like a cult leader. Recoginse that this 'spam' is just some bullshit that you tell to the sheep.
09:43:40 <hatchproject> When you do that, solution will present itself. Observe. 'spam' -> 'FUK talks bad things about Monero on our IRC' (Don't say that out loud obviously, that will get you excommunicated) Solution? Get off-the-shelf sentiment analyser, detect anyone who 'talks bad things about Monero' and ban them.
12:02:28 <kiwi_48> Is there a discord server that is generally used?
12:22:47 <sech1> kiwi_48 https://discord.gg/3GDDeqjypN
13:06:16 <xmrmatterbridge> <underzero> Hello there. I'm a SysAdmin and I have a server infected with monero minner malware. I was looking for on GitHub a kind of tool for checking the execution of Xring protocol. Can someone help me?
13:07:23 <moneromooo> No clue what Xring, but for the monero malware part, http://mrw.getmonero.org/ might help.
13:11:17 <Ammar__> I just learned about monero
13:11:48 <Ammar__> And I got excited when I heard the asic resistant feature
13:12:30 <moneromooo> It has great sides, and also not great ones. A hard path to follow for sure.
13:12:53 <Ammar__> I don't understand what that means in details. But it just means that small fish still got a chance at mining this. Even with cpu.
13:12:53 <Quotes> But it's easy! https://www.youtube.com/watch?v=RXJKdh1KZ0w
13:13:37 <Ammar__> Thanks for the link. I will watch it than come back. I have more questions.
13:14:56 <Ammar__> What is this video about?
13:17:22 <Mochi101> Ammar__, technology
13:17:24 <moneromooo> What video ?
13:17:39 * moneromooo assumes someone on the kill list replied 
13:17:42 <Mochi101> moneromooo, Quotes
13:17:56 <moneromooo> Oooh :D
13:18:25 <Mochi101> moneromooo, the "i don't understand" trigger
13:19:08 <Ammar__> Well, what the best guide out there on mining xmr?
13:20:25 <Ammar__> Also, what's makes you mine faster, more cpus, or more powerful ones?
13:20:39 <Mochi101> both
13:23:01 <Ammar__> So what asic resistant really means if cpu power is still a contributing factor?
13:23:28 <Mochi101> CPU != ASIC
13:23:45 <Ammar__> Oh.
13:24:31 <Ammar__> Means rigs like gridseed and the likes can't mine it
13:25:00 <moneromooo> The PoW algorithm monero uses tries to use modern CPU strengths. Making an ASIC for it basically means developing a lof of an actual CPU.
13:25:48 <moneromooo> The idea's that Intel/AMD/ARM are already pretty good at this, so topping them is gonna be a high bar, even with the ability to drop some parts of hte CPU you don't need.
13:26:48 <Ammar__> I see. Now this make sense to me. Thanks.
13:28:10 <Ammar__> Is it possible to develop a better algorithm to mine it if someone's try too?
13:29:03 <moneromooo> Probably.
13:29:47 <moneromooo> It's like everything else. Doing better is almost always possible, it just takes more and more effort for less and less improvement.
13:30:05 <moneromooo> In general, etc, etc.
13:30:47 <marmulak> yup
13:30:52 <marmulak> very smart
13:31:00 <marmulak> so how about that delisting, eh?
13:35:03 <sech1> This delisting will be forgotten in a couple of weeks
13:37:32 <marmulak> I will never forget
13:41:28 <sech1> 1/1/21 Never forget!
14:51:50 <bigslim[m]> <sech1 "This delisting will be forgotten"> Probably not
14:51:59 <dav> Hi there. I made an XMR withdrawal from binance which seems to have gone through but hasnt come through to my wallet. I've tried Mymonero and monero gui. it has been about 4 hours now. does anyone have any suggestions?
14:53:24 <bigslim[m]> <dav "Hi there. I made an XMR withdraw"> Should coMe through immediately but not settle for 10? Blocks
14:53:56 <bigslim[m]> Did you copy paste the address from your gui wallet to binance withdrawal box?
14:55:45 <dav> i scanned it. Ive checked the addresses from binance destination address and my wallet and they match
14:58:16 <dav> obviously a transaction sent is logged what about when it arrives in wallet? is that logged other than locally?
15:06:24 <checkmate1984[m]> <coffeeroaster "CLI Android install: install it "> Sorry it took a while "$ file monero-wallet-climonero-wallet-cli: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /system/bin/linker64, with debug_info, not stripped"
15:07:29 <dav> Is this just unheard of? RE XMR not arriving in wallet? is there anyway to debug this?
15:07:49 <moneromooo> It's heard of a lot. The two main reasons are:
15:08:06 <moneromooo> - your daemon and/or wallet isn't done syncing/scanning
15:08:37 <moneromooo> - your wallet is set to ignore everything before a certain block that's after your tx
15:09:01 <moneromooo> For the second problem, type "set" in monero-wallet-cli, then check the value of refresh-from-block-height.
15:09:33 <moneromooo> If it's a value larger than 2.26 million, try setting it to 2.5 million and issue: rescan_bc
15:10:13 <moneromooo> For the first problem, type "status" in monero-wallet-cli, check it claims it's at about 2.2657 million.
15:13:54 <dav> i'll work with that for now, I haven't used monero-wallet-client yet so ill give those a go. thanks
15:14:39 <selsta> you can also do this with the GUI
15:15:28 <selsta> go to settings -> info, click on "(change)" next to wallet restore height and then on ok twice
15:15:37 <selsta> then wait until a full refresh is done
15:21:28 <M5M400> dav: I've had a miner today reporting that a payment from my pool didn't hit his mymonero wallet too. I verified it's on the chain. he can see subsequent TX though. maybe their service has a problem atm
15:26:30 <dav> that worked. thanks, i can rest now! cheers guys
15:26:51 <moneromooo> The refresh-from-block-height one ?
15:27:01 <dav> yes
15:27:11 <moneromooo> How did you originally create this wallet ?
15:27:37 <dav> in MyMonero
15:28:00 <moneromooo> Well, glad it's all good now :)
15:28:25 <dav> me to lol ☺️
16:03:41 <alexhugo> monero got delisted on bittrex
16:03:58 <alexhugo> any opinion?
16:04:35 <dEBRUYNE> alexhugo: https://www.reddit.com/r/Monero/comments/kouacy/havent_heard_of_anything_on_the_regulatory_side/
16:07:50 <maraga> hello
16:10:33 <alexhugo> on how many places xmr can be sold
16:11:04 <maraga> bisq one of the best
16:11:41 <maraga> just is running in java and need lot of resource
16:11:58 <maraga> sometimes dont play at all!
16:20:16 <maraga> why i have always   "pending" for transfer on new chain
16:20:26 <maraga> even if i do relay tx nothing changes
16:20:36 <maraga> when i do flush_Tx money are back in wallet
16:21:36 <dEBRUYNE> maraga: Which version of the wallet are you using?
16:21:48 <maraga> the latest
16:21:52 <moneromooo> Maybe your tx is invalid. Might hapen if your local daemon is not synced, or the db is shot in some specific way. Or you might be connected only to asshole nodes that don't relay txes.
16:22:21 <maraga> tx is valid
16:22:45 <maraga> im connected to one node and no issue on connection
16:23:10 <moneromooo> Try downloading https://gui.xmr.pm/files/block.txt, run ban @block.txt, then try again after you have a few connections.
16:27:50 <maraga> is possible to choose from cli or daemon specific tx to mine?
16:29:29 <moneromooo> No.
16:32:41 <selsta> maraga: which node are you using?
16:33:53 <maraga> im talking about new chain
16:59:01 <monerouser1144> Hi all, is it normal for sync_info to show several peers being 2 blocks behind? (e.g. 2265773 with current being 2265775)
16:59:16 <moneromooo> Yes.
17:09:34 <monerouser1144> Regarding "generic" network attacks (not those specifically aimed at the p2p / rpc protocols) please check https://security.radware.com/ddos-threats-attacks/ddos-attack-types/ddos-attacks-on-network-resources/ and https://blog.radware.com/security/2017/11/http-attacks/ I wonder if monerd would be susceptible to resource exhaustion attacks ...
17:11:37 <moneromooo> It is.
17:17:03 <monerofanboy> Many attacks can be mitigated by a host with ddos scrubbing. UDP floods, iCMP floods, syn floods, Can all be mostly mitigated by a host with good ddos scrubbing.
17:17:05 <bigslim[m]> People still spamming monero nodes?
17:18:20 <moneromooo> I think so. I didn't look today.
17:18:28 <moneromooo> But yesterday yes.
17:18:43 <bigslim[m]> I haven’t updated for a few point releases
17:19:08 <bigslim[m]> Did you guys implement auto ignore of known bad nodes?
17:19:11 <moneromooo> My logs are back to normal atm so I don't see what's happened recently, but I assume they're still at it.
17:19:24 <bigslim[m]> Or just delete p2plists?
17:19:46 <moneromooo> Depends on your definition of auto, ignore, known and bad :)
17:20:27 <selsta> yep, they are still doing this attack
17:20:27 <bigslim[m]> Heh
17:20:41 <moneromooo> There's a DNS based list of known bad nodes you can use to ban them, it's not default though.
17:20:46 <bigslim[m]> Do we still have to manually block bad ip?
17:21:01 <moneromooo> And various detection of various assholery, but this will never catch everything.
17:21:07 <bigslim[m]> Why not default the bad nodes?
17:21:25 <bigslim[m]> The chances of a good operator getting that IP is quite slim
17:21:36 <monerouser1144> monerofanboy I am asking because I was wondering if would be possible/effective to use HAproxy in front of monerod http://cbonte.github.io/haproxy-dconv/2.4/intro.html#3.1
17:21:41 <bigslim[m]> Unless bad actor using vpn
17:21:44 <moneromooo> It gives an attack vector of getting to write to that list and ban good nodes.
17:21:59 <bigslim[m]> Yea
17:23:15 <bigslim[m]> 19 more days....
19:16:43 <monerofanboy> To follow up from earlier, an HAproxy would help to mitigate some attacks,but definitely not all. I.e., I tested a syn flood against my own POS consumer router and I was easily able to overwhelm my router. An HAProxy would help against to protect an attack like that, coming from one single remote attacker; however, an attacker who is sending an syn
19:16:43 <monerofanboy> flood from 25 hosts at once would saturate and overwhelm my bandwidth from my ISP.
19:18:02 <monerofanboy> So a HAProxy would help, but against a determined attacker, at some point, an HAProxy is no help at all.
19:20:24 <monerofanboy> This is where host ddos scrubbing from companies like OVH, Amazon, etc help a ton, because both Amazon and OVH and the bandwidth to withstand huge DDOS attacks and can scrub the traffic going into a VPS server, hopefully keeping the server from being ovewhelmed.
19:20:39 <monerofanboy> have the bandwidth*
19:59:01 <selsta> Lyza: we might have found the freezing issue
19:59:15 <selsta> or one more, don’t know if there are multiple
20:14:41 <Lyza> great news! it does seem like there might be a couple diff ones but idk. my nodes been behaving today
20:14:54 <Lyza> since earlier anyway
20:26:04 <selsta> Lyza: hope your node freezes again so that we can get gdb output
20:26:17 <selsta> seems like my freeze is due to a recent patch
20:40:07 <bigslim[m]> where daemon block list?
20:40:52 <bigslim[m]> 0.17.1.8-release
20:41:15 <selsta> https://gui.xmr.pm/files/block_tor.txt
20:42:49 <bigslim[m]> omg
20:43:00 <bigslim[m]> any way to ban all of them or do we have to run each one?
20:43:12 <selsta> --ban-list /path/to_block_tor.txt
20:43:24 <bigslim[m]> oh nice
20:43:40 <selsta> or `ban @/path/to/block_tor.txt 99999999` when you want to reload it while monerod is running
20:45:29 <bigslim[m]> hmm did not work
20:46:05 <bigslim[m]> unknown command: --ban-list C:\Users\pathto\monero\block_tor.txt
20:46:23 <bigslim[m]> oh duh have to start cli with that add on
20:46:35 <edi_> try it on linux :]
20:46:51 <selsta> like I said, or use the ban @path command
20:46:57 <selsta> then you can use it after it is started
20:47:14 <selsta> ban @C:\Users\pathto\monero\block_tor.txt 9999999
20:47:28 <bigslim[m]> ahh good to go
20:47:59 <edi_> selsta: i found another block list somewhere, but I'm wondering is there a place where the xmr community keeps this info in sync? or how does that work?
20:48:18 <bigslim[m]> ban @C:\Users\PoopyDiaper\Desktop\Rando,\monero\block_tor.txt worked
20:48:22 <bigslim[m]> haha
20:48:34 <selsta> edi_: which one did you find?
20:48:46 <edi_> one on reddit, but can't exactly remember the post
20:48:57 <edi_> its much shorter than yours
20:49:05 <edi_> (or the one you referred to)
20:49:18 <selsta> https://gui.xmr.pm/files/block.txt ?
20:49:26 <edi_> ah, could be
20:49:35 <selsta> this one is the same as the other, just without tor exit nodes
20:49:43 <bigslim[m]> still getting the error 2021-01-02 19:11:59.123 E failed to find transaction input in key images. error on cli
20:49:44 <edi_> yeah I think it is
20:49:55 <edi_> ah oke, I figured it had smth to do with tor :)
20:49:58 <bigslim[m]> with img number
20:50:33 <edi_> but my next question , why/when are tor exit nodes problematic,
20:50:36 <edi_> ?
20:50:43 <bigslim[m]> then 2021-01-02 19:11:59.124 E transaction id = <tx id number>
20:50:47 <selsta> because someone uses them to send crafted packets
20:50:54 <selsta> so we temporarily ban them
20:51:07 <selsta> bigslim[m]: don’t think this is related to the ban list
20:51:09 <edi_> oke, so how you deal with the problem that ip's can change quickly?
20:51:11 <selsta> what are you trying to do?
20:51:20 <edi_> running a node, safely :)
20:51:27 <selsta> meant bigslim[m] :D
20:51:31 <edi_> lol
20:51:41 <selsta> yes, they can get new IPs, it is not a long term solution
20:51:56 <bigslim[m]> selsta:  no this has been here since IIRC 17.1
20:53:53 <bigslim[m]> it happens only after I update to latest version and run the first time. Then after I do not get the errors.
20:54:13 <bigslim[m]> so just updated to 17.8 and got the errors, now restarted daemon and no errors
20:54:36 <bigslim[m]> maybe its picking up the wrong chain tx's from back then or something.
20:55:42 <edi_> selsta: so if you run a node without the blocklist, what's the worst that can happen?
20:58:26 <moneromooo> Currently, your node crashes if it doesn't have renough memory, which is something like a couple dozen GB I think ? Not sure about the number.
20:58:40 <bigslim[m]> 32 GB ok :)
20:58:42 <moneromooo> Well, more like killed by the OOM killed, but same differnce.
20:59:35 <moneromooo> 64 GB definitely enough. 4 GB definitely not enough.
20:59:57 <sech1> I've seen 39 GB used on a 64 GB server with .8 release
21:00:05 <bigslim[m]> jeesh
21:00:48 <bigslim[m]> I do not think I have ever used more than maybe 20gb at a time and thats running 4 VM and 2 daemons at the same time
21:03:04 <edi_> i limit my node at 4GB
21:03:19 <edi_> +/-
21:04:01 <edi_> but it runs on a machine with more overhead
21:05:26 <edi_> so it's some weird sort of DDOS attack they're employing? or what do they hope to accomplish
21:05:30 <edi_> bring the network down?
21:05:32 <edi_> :]
21:07:33 <selsta> no clear goal, probably just disruption and annoying node operators
21:07:48 <selsta> but it’s good if it causes us to find and fix issues
21:11:17 <h2017> i've got my own node, so i've never used someone else's node. when you use simple wallet mode, for instance, and your node just connects to another one, what happens if it connects to a rogue node. couldn't the rogue node just have a completely wrong blockchain?
21:11:22 <edi_> exactly, free bug bounty :)
21:12:39 <h2017> so you could be bamboozled into making transactions that never happen at the very least, by relying on someone else's node. is this not true?
21:12:41 <edi_> h2017: i'm not sure how this exactly works, but I *assume* your node doesn't rely on a single another node
21:13:16 <selsta> h2017: if you use the strangers node they can feed you wrong information, yes
21:13:19 <selsta> remote node*
21:14:08 <h2017> h2017, i notice that it relies on bootstrap mode, where your monerod instance connects to a node. is it a single other node that it connects to, or a bunch (as edi was saying).
21:16:10 <moneromooo> Single.
21:16:43 <h2017> so there is no way to be sure that you are not connecting to one of the attacker's node's when you run your wallet in simple mode
21:17:00 <edi_> i was wrong, I understood you talked about node <-> node comms
21:17:18 <h2017> edi i think i used wrong terminology
21:18:01 <edi_> but there I'm pretty sure you got it right, if you connect your wallet to a rogue node
21:18:08 <edi_> there isn't really a way of knowing
21:18:14 <h2017> right
21:18:23 <edi_> so the recommendation is to run your own node for maximum security
21:18:28 <h2017> yes
21:18:44 <h2017> not just security but transactions that will actually go onto the blockchain
21:19:30 <edi_> you might be right, not sure on that one
21:19:55 <h2017> edi, the rogue node could just trick you into accepting everything you do and then throwing it away
21:20:23 <edi_> okay
21:20:24 <h2017> or making stuff up with it's own fake blockchain
21:20:46 <edi_> so in theory its possible for an attacker to fake the xmr blockchain
21:21:00 <edi_> and have your authentic xmr sent to his "fake network"
21:21:11 <edi_> so you lose all that money?
21:21:22 <h2017> no you wouldn't lose it i don't think
21:21:34 <h2017> but you would be fooled into thinking you had transacted on the real monero blockchain
21:22:16 <h2017> you might lose your sanity
21:22:20 <edi_> oke, haha
21:22:32 <selsta> afaik he can fool you into thinking that you received monero that you didn’t receive
21:23:02 <edi_> maybe its more intel gathering than attacking?
21:23:14 <sech1> but he needs to mine some blocks to do it, right? As many blocks as the number of confirmations you need
21:24:03 <sech1> So if you're a merchant and accept 0-conf transactions, attacker can eclipse your node, send a tx to you and send the same output to himself on the real network
21:24:26 <selsta> this is about using an attacker remote node
21:24:54 <selsta> hmm
21:32:46 <bigslim[m]> this is why we use our own nodes
21:32:57 <bigslim[m]> This is the way
21:35:25 <ComplyLast> this is the way.
22:29:46 <fibonacci> https://www.jw.org/finder?wtlocale=E&docid=502019178&srcid=share
22:30:48 <u9000[m]> kinda random
23:49:27 <Beags[m]> i guess its for people who hodl'd altcoins other than monero