06:51:55 Quick update on the "Monero kidnapping case" - today the police have arrested ... *wait for it* .... *drums* ... The husband. 07:05:39 the norway one? 07:06:45 ok found the article at dagbladet 07:12:53 yeah 07:19:32 Inge-: :D 07:25:53 midipoet: ^ just fyi 07:36:07 Inge-: the husband? that's quite an elaborate cover up if it was indeed that. 07:45:33 it was the butler 07:52:05 midipoet: We are not surprised. 07:55:51 but yeah, amazingly elaborate if so. and took 1.5 years before he was apprehended 07:56:17 This is might be an interesting movie script 07:56:29 Inge-: can you link the source? 07:56:56 I want to google translate it lol 07:58:20 selsta: there is almost no info yet. https://www.aftenposten.no/norge/i/rA2gKe/anne-elisabeth-hagens-ektemann-er-paagrepet? 07:58:43 he was apprehended in his car, car taken away, his office building cordoned off. 07:58:56 press conference in 30 minutes 08:34:16 is this about the "they kidnapped my wife and demand bitcoin" guy? 08:37:12 s/bitcoin/monero/ 08:37:14 yes 08:37:45 interdasting 08:40:58 its always the husband 08:42:15 i wonder what evidence appeared 08:43:29 Inge-: ty, keep us updated 08:46:32 azy: still pretty elaborate for a 68-69 year-old 08:46:55 hes an engineer billionaire 08:47:07 still, Monero is pretty greek for most people 08:47:25 https://premium.vgc.no/ap/images/ff67c182-0e24-480a-825d-d37de0fd2c00?fit=crop&q=80&w=980 08:47:27 look how rich he looks 08:47:40 He is charged with murder or assisting in the murder of his wife 08:48:03 i wonder why he did i 08:48:04 t 08:49:57 sounds like a movie plot 08:56:18 09:56 < Inge-> This is might be an interesting movie script 08:56:48 they basically added nothing else. 4 weeks incarceration while they continue to secure evidence 08:57:38 he'll likely have researched all what he said the kidnappers used 08:57:46 his google searches will fuck him 08:59:12 so he manages to come up with a Monero solution, and perform cryptocurrency transactions, without being caught for it - but his google searches will foil him? 09:02:29 how do you learn about such things without having investigated them? 09:03:23 DDG? Tor? Tails? 09:03:58 all he said was that he received a message from the kidnappers demanding monero. whats to get caught with? at what point do the police check his computer history? 16:23:39 Hey, quick question: is the following a valid attack (for a global adversary with loads of $$) 16:24:31 Consistently create loads of small transaction, sending money to one's self using plenty of accounts (not sure if even needed) 16:25:31 Thus producing plenty of key images that other normal users use in their ring. Wouldn't this make tracking way easier given enough transactions? 16:26:05 If this is a valid attack: Does it have a name so that I can do some more research? If it's not a valid attack: Where is my mistake in thinking? 16:26:16 sort of like a Sybil attack 16:26:31 deluding users into thinking their anonymity set is larger than it is 16:26:51 hmm, not an expert, but it sounds plausible. One caveat is that you'd have to do a lot of transactions, and it'd be quite obvious 16:27:02 "why is our transaction volume up by 25x" 16:27:13 flooding attack 16:27:23 already discussed in a couple different papers 16:27:28 Thanks for that term! Well, transaction volume would have to look at least somewhat organic 16:27:54 Can you link me some of them by any chance? @hyc 16:28:05 look on monero research lab webpage 16:29:09 will do, thanks! 16:32:59 Guest74: MRL-0001 and MRL-0004 iirc 16:33:04 Those papers describe similar attacks 16:33:56 Let's say the transaction does indeed increase by some large factor (e.g.x10). How do you think would the community react? Would all (legit) users just stop using monero? Wouldn't that effectively result in "destroying the project" if an adversary holds it up long enough, thus creating loads of doubt inside the community? 16:34:32 @deb 16:34:51 Thanks! dEBRUYNE 16:35:49 There are some mitigations in place to alleviate any potential impact 16:36:01 With respect to community behavior, basically impossible to predict 16:36:06 As there are a variety of factors on which it depends 16:37:41 Fair enough regarding the community. What mitigations are you talking about? Is there a way to somehow detect the adversary-transactions and kind of exclude them from being picked as decoys? 16:38:05 dEBRUYNE: what are these mitigations? 16:44:15 Trying to find the relevant commit 16:45:09 https://github.com/monero-project/monero/commit/b8787f430262520a9e81267802b869b1a7cde245 16:45:29 The mitigation is in curbing exponential growth essentially 16:48:51 makes sense to me, although it doesn't prevent adversaries that can pretend to look like organic growth (not sure how feasible this is). But I'm guessing that's simple a gamble on organic growth always being (significantly) bigger - essentially the same gamble TOR takes by hoping most nodes are not controlled by a single adversary? 16:50:12 Tor has systems for preventing Sybil attacks 16:50:45 interesting! (still pretty new to all of this) 18:52:50 hello anybody here? 18:53:28 hi 18:54:18 is this the real xmr irc ? 18:54:52 yep XD 18:54:57 indeed it is. as far as it goes 18:59:13 There's another secret channel. We only filter out who gets to go and who doesn't. 19:05:32 Vitalik Buterin didn't make it in. He failed at the basic knowledge of thermodynamics. 21:11:00 test 21:11:25 test OK 21:13:36 nvm test failed 21:14:32 hi folks 21:15:24 last time i used my monero wallet, i used monero-wallet-cli to access it, and when I started it up, I had to wait a few minutes for the refresh to complete -- i.e. it said "starting refresh" "Height 1968272 / 2086877" 21:16:37 i am confused because, then today I go to use it again, and when I open it again, it says the same -- not unusual -- but, the block height last time i used it was definitely higher than 1999999, because i remember it being "Height 1xxxxxx / 2xxxxxx" last time 21:17:03 so i am wondering, why would the refresh start from something lower than the block height from last time the wallet was used? 21:17:43 *maybe* i am just mis-remembering, but I could swear.. 21:20:10 Henry151: maybe you didn’t save properly? 21:20:32 maybe? i didn't know that there was any saving to do; I think i exited with a keyboard interrupt 21:20:50 how do you save? 21:20:52 should be ok normally 21:21:18 i know that i left it open, running, on screen for several days 21:21:22 then i closed it a few days ago 21:21:28 maybe 2 days ago. 21:21:55 i don't know if i did a keyboard interrupt, or maybe, i had it open in an ssh terminal window, and i just closed the terminal window on my local side 21:22:22 if it didn’t close properly it might be the issue 21:22:36 anyway, it is rather annoying, because getting from block height 1976479 all the way back up to 2086878 is taking a long while 21:22:45 so i would prefer to close it properly next time 21:22:57 is there a command from moner-wallet-cli to tell it to close correctly? 21:23:05 exit is ok, ctrl+c is ok 21:23:15 you can also type save to save the wallet 21:23:21 ah. 21:23:39 ok, great, thank you. I will save a couple times and exit properly, next time, because this is absurd 21:23:44 any reason it doesn't autosave? 21:23:56 also, why is this happening anyway? I don't really understand -- I have a monero node running, the block height should be current 21:24:24 i thought monero-wallet-cli just sorta interacted with my running node, so i figured if my node is up to current height, what is happening? 21:24:42 Henry151: your node is current height but your wallet has to get scanned 21:24:55 hmm 21:25:00 ok 21:25:05 the wallet scans blocks from the node for your outputs 21:25:23 the daemon does not now anything about your wallet 21:25:23 maybe if i leave my monero-wallet-cli running in a tmux or something, that way it is always ready-to-go when i need it 21:25:26 know* 21:26:05 because like, i.e., right now, I have had to let a transaction time out that was waiting for payment, because this is going to take a while. Fortunately this time there is not any real urgency but I would like to be able to access my monero rapidly in a time-sensitive situation 21:26:22 if you open the wallet once a month or so 21:26:32 then I don’t think it should take longer than 1-2 minutes 21:26:46 unless slow hardware 21:26:51 or slow internet 21:27:07 ok. I see. I had figured the same, but then i guess because i failed to save or failed to close properly, it didn't work and is reloading from all the way months and months ago 21:28:03 23:23 any reason it doesn't autosave? <-- we will probably add auto save to GUI, I don’t know if CLI has this feature 21:28:10 hardware is reasonably fast, this is running on a home webserver, gigabit internet, many processors, it's an older webserver but it is able to for example transcode several 720p video streams at once, while serving a half-dozen websites, without any problem 21:28:37 and the client hardware? 21:28:41 scanning is done client side 21:29:03 a $1500 laptop i bought a little over a year ago, lenovo p51 21:29:09 decently quick 21:29:13 ok, and how long did it take? 21:29:26 well it is now at 1987318 21:29:36 i think the "client" is still the webserver 21:29:53 because i access it by doing ssh into the server, then from the server prompt, i run monero-wallet-cli 21:30:07 ok, yep then it is the webserver 21:30:10 selsta: afaik there isn't any reason to not have it auto save. Seems like a really bad ux design to not have it do something incase the pc crashes or terminal window get closed for some reason 21:30:32 maybe there is some reason for it not saving 21:30:45 i would definitely say, that an autosave feature would be *great* in the cli interface 21:31:09 i had assumed, the first time that I waited while it synce from 19xxxx to 2xxxxxx that i wouldn't have to wait like this again 21:31:20 its basic ux 21:31:25 but, apparently, because I exited in a non-clean manner and without typing save first, it didn't. 21:31:36 its 2020 not 1990 lol 21:31:48 like I said, there might be auto saving 21:31:48 I think it is fairly reasonable for an end-user to assume that it will automatically save when the block height reaches current. 21:32:01 yes, I recall having problems with this too 21:32:09 whenever it is synced, if you close it normally, it will save it 21:32:18 I see. 21:32:40 I would recommend altering that, so that instead the logic is, when it reaches "synced" state, it saves automatically. 21:32:58 that way, it doesn't matter how you close it, it saves as soon as it has reached a "synced" status. 21:33:00 it should save it at intervals 21:33:10 or that, sure. 21:33:14 yes GUI will add every X minutes 21:33:17 or catch any interrupt event and save on that 21:33:27 is there a gui presently? or is that in the pipeline? 21:33:33 yea there is a gui 21:33:39 interesting 21:33:43 maybe i will take a look at it 21:34:12 but i generally prefer to do my things from cli whenever it's not a big inconvenience 21:34:18 I think it does catch signals like SIG_HUP or SIG_KILL 21:34:27 the gui basically a front end for the daemon. Its not a standalone app. At least it wasn't a year or two ago when I last tried it 21:34:46 not really a frontend for the daemon 21:34:57 shillo: well that makes sense, that describes the basic relationship between bitcoind and bitcoin-qt, doesn't it? 21:34:59 it’s like monero-wallet-cli just with GUI 21:35:34 it can do basic daemon things like start stop 21:35:34 oh yea. Forgot it comes in a bunch of executables 21:35:46 but otherwise it’s just a wallet 21:35:48 but the gui version does things different. 21:35:56 for my bitcoin node i am running bitcoind and then i connect to it with armory wallet. So i'm not sure really how bitcoin-qt interacts with bitcoind or what but i know my armory wallet is talking to my bitcoind 21:36:35 bitcoin-qt used to compile as a single executable. Not sure if it still does or not. 21:37:37 i want to see bitcoin turn into monero over the course of time... personally i think that bitcoin has such a big headstart that even an alternative like monero, that has some significant advantages over the original bitcoin, still has no chance of ever overcoming the headstart bitcoin has in terms of established infrastructure and public perception etc 21:37:40 bitcoin is a giant bloat ware. XD 21:38:47 i would like to see bitcoin change, over time, incorporating the features that monero has that make it preferable, like the stronger privacy protections 21:40:22 i was a very early user of bitcoin, I didn't buy a bunch and hold on to it and get rich, but, I used it because I didn't have access to traditional banking services, i.e. western union, bank accounts, debit cards, etc 21:40:42 for several years 21:42:27 it was extremely useful. However, I wish that it had the privacy features monero has 21:42:45 dito. I used Bitcoin to pay my vpn provider that had limited access to fiat payment provider - because Visa did not like them. 21:43:06 in 2015 or so 21:44:15 fiat payment beyond borders is still a bit problematic. 21:45:30 I did all my christmas shopping December 2012 using bitcoin... still look at those receipts from bitinstant sometimes, and get sad 21:45:33 Henry151: woukd be great if bitcoin had the privacy of Monero. But nobody can see that happening. Monero is what the noob thought they bought, when they bought Bitcoin. Maybe Bitcoin is a better "digital gold" and better "programmable money" - except for the fact it is the Panopticoin. 21:47:39 bitcoin is doing some of the stuff. Mimblewimble, schnorr sigs, etc 21:48:01 Probably not enough to be useful. But perhaps enough to stop the blacklisting of KYC-free monero exchangers. 21:49:16 Bitcoin could not scale on a global level without loosing it's decentralised nature. A world dominating crypto currency forced on you with a giant block size - No thanks. Crypto scales very good by diversity. Smaller blockchains and choice - because different use cases need different solutions. 21:50:04 Same true for Monero. 21:50:17 monero is held together by elbow grease and prayers, though 21:50:32 if you look at the confirmation times for $X of security, they're absurdly long 21:51:01 giant block size was what Nakamoto envisioned, it may interest you to know