00:06:25 why does the blockchain download get progressively slower, even after ringCT 00:11:03 The last 20,000 are taking an eternity 00:11:11 more txns 00:11:14 usage has gone up 00:11:17 txns? 00:11:24 transactions 00:11:29 more transactions per block 00:11:31 Ah 00:12:01 Well maybe they should make the progress bar on file size not amount of blocks >.< 00:12:47 the gui has no way to know the total size 00:12:57 it only knows the count of blocks 00:17:43 couldn't it just ping getmonero 00:18:32 or just code in "after block [number] increase enstimated file size" 00:18:48 And it would be pretty accurate 00:32:38 i don't see why it can't at least use the usual progress bar bag of tricks. it can start doing a running average of block processing times 02:06:49 UHHHHH 02:07:07 so after the blockchain was finished downloading 02:07:14 I close the program 02:07:31 It asks if I want to keep the daemon running in the background 02:07:39 I'm like "okay sure" 02:07:50 I restart my computer and open it again 02:08:46 "Couldn't open wallet: internal errror: "file/path/walletname.keys" is opened by another wallet program" 02:11:51 lol 02:11:58 xmr is rekted 02:12:29 had a good short tho 02:13:16 cool story bro. 02:14:05 #monero-markets 02:14:14 h2017: it's a troll 02:14:15 us restrictions may rekt this coin tho 02:14:39 if 125 is broken this is coin is totally ruined 02:14:42 what restrictions? 02:15:09 US may block privacy coins 02:15:20 source? 02:15:40 don't talk about price in this chan 02:15:50 take this convo to #monero-markets 02:15:51 and guess what xmr sticks to good standards and doesn’t offer an option to disable untraceable transactions 02:15:58 okay sorry 02:16:06 lol, XMR will never offer that option. 02:16:47 what reason is there to believe that US would block or ban XMR? 02:17:30 ndorf if they did many coins would be affected since many are acquiring privacy features 02:17:50 lol search bruh i’m not revealing a top secret fbi document 02:18:08 ah, so no basis in reality whatsoever. just FUD. like i said cool story bro 02:18:13 including bitcoin litecoin, bitcoin cash and doubtless many others that aren't specifically privacy coins 02:18:36 exactly, in fact LTC are planning to adopt mimblewimble algorithm 02:19:20 no bitcoin doesn’t offer that same anonymity as monero 02:19:52 so imagine all the people un the us being told they couldn't legally trade or transact in those coins unless they hard forked in with the priv features stripped out 02:19:55 that's what it would come to 02:20:06 loool just search by yourself. 02:20:14 but i woudldn't put such an edict past western governments, but it's not likely to happen tommorrow 02:20:18 i'm in the US and transact in Monero, as well as Monero<->fiat, regularly. no one has complained.\ 02:20:56 ndorf i know. there is not law or regulation that singles out privacy coins 02:21:05 i'm just imagining what it would be like if there was 02:21:13 they obviously cannot stop you. they just would prevent exchanges and institutional from paying/getting xmr 02:21:55 but this would raise an eyebrows especially from irs side. 02:22:10 i submit dozens of pages with "Monero" all over them to the IRS every year. no issues there, either. 02:24:29 You have GOT to be kidding me 02:24:35 I'm just using a remote node 02:24:38 screw this shit 02:24:48 what happened? 02:25:04 So after it finished redownloading the blockchain 02:25:13 I was like okay, it seems to be working 02:25:22 I went to close the program 02:25:37 It asked if I wanted to keep the daemon running in the background 02:25:41 I said yes 02:25:44 I restarted my PC 02:25:50 I open the wallet again 02:26:10 And it said another wallet program already had that .keys open 02:26:31 is this windows, linux or something else? 02:27:06 Linux 02:27:24 well I tried copying it to a different folder and opening that 02:27:27 it seemed to work 02:27:37 but then the blockchain filepath was messed up? 02:27:44 It was trying to download it again 02:27:50 so I set the filepath again 02:27:54 And 02:28:06 "Failed to start the daemon" 02:28:07 "Failed to start the daemon" 02:28:08 "Failed to start the daemon" 02:28:08 "Failed to start the daemon" 02:28:09 "Failed to start the daemon" 02:28:43 that is bizarre. is there anything interesting in the daemon log? 02:29:01 are we absolutely sure the daemon isn't running twice? `ps auxww | fgrep monerod` ? 02:30:56 only one instance 02:40:30 hm, sounds like one is already running and you're trying to start a second one? 02:40:43 you could cleanly stop that one and try again, but it's probably better to figure out why the first one isn't doing what you want 02:42:00 `ps auxww` should show you all the parameters. is the correct --data-dir specified there? 02:42:16 (blockchain path) 02:45:55 just 'ps auxww'? 02:46:03 made a ton of stuff pop up 02:46:05 | grep monerod 02:46:41 encrypt+ 4894 0.0 0.0 8900 736 pts/0 S+ 20:46 0:00 grep -F --color=auto monerod 02:46:54 thats all it says 02:47:54 ok, so there are 0 instances. does it still give you the Failed to start error if you try now? 02:48:19 and if so, can you find the bitmonero.log file and see what errors if any are in there? 02:48:29 should be under whatever your data-dir is 02:55:10 I deleted it all 02:55:17 im making a new wallet 02:57:00 d 02:57:29 seems like mymonero dont work 02:58:22 * M7361[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/HtXrfCucggKJmQWcAJsPXwmt/message.txt > 02:59:10 whats a goodnodetoonncetto 03:00:39 node.xmr.to:18081 or node.moneroworld.com:18089, off the top of my head. there are surely others 03:00:49 VashTheStampede: what issue are you having with MyMonero? 03:03:02 VashTheStampede: what issue are you having with MyMonero? 03:04:10 um so after I remade my wallet and all that it seems to be working, i deleted everything except that golder that ahs t he blockchain and reloaded that. I'm afarid if I close the gi and open it again it won't work ._. 03:05:19 Snowstorm: i wish i could promise that it will work, but without knowing what the problem even was, i can't do that. however, if you write down the seed words and keep them in a safe place, you will never lose any funds no matter what. you can always restore the wallet from those seed words. 03:05:35 well the wallet is empty 03:05:41 so I'm not worried about that 03:05:49 right, well presumably it won't stay that way 03:05:52 yeah 03:06:04 okay I'm going to close the GUI and open it again 03:06:08 and if it doesn't work 03:06:13 I'm switching to remote node 03:06:38 remote node will work fine, as long as you don't try to restore an ancient wallet 03:07:19 as for figuring out what went wrong with your setup, you probably want someone knowledgeable about the GUI in particular to help with that. if you have no luck here, try reddit.com/r/monerosupport -- it's quite active 03:07:37 of course you could always try the CLI ;) 03:07:38 oh 03:07:38 * ndorf ducks 03:11:30 YES 03:11:34 IT FRICKING WORKED 03:11:42 I closed and opened it 03:11:48 and it didn't crap out this time 03:11:59 glad to hear it. 03:18:46 Can you try sending me like 5 cents or something to make sure it's working right? 03:20:27 test 86JYN1pSEo7ZZk6W7MbQNRYR8dSLrWt3Rc4t7UHNUgMPdHraZNwoCtKfLLA1msrXSUT85r2TjrM1bKdn5pwZmKCeDwKevL9 03:38:42 Has anyone tried running a node and wallet-rpc-server on an Amazon Graviton (ARM) server? Did it work out of the box? 04:02:46 https://cutt.ly/AnonMail 12:36:44 I just got two error messages while syncing up my node: `Transaction spends at least one output which is too young` 12:37:15 Does that refer to the transactions contained in the blocks I'm syncing, or does it refer to one in the mempool? 12:38:30 Could it be that a tx picked a ring member that is too young? Or will it still get rejected by protocol? 12:38:36 It doesn't say. Ignore that. 12:38:56 It just got rejected, it told you that. 12:39:45 I'll move those messages to non default someday. 12:40:07 Ok, it wasn't clear whether it was referring to the blocks I was syncing or to a tx in the mempool 12:40:20 What's the difference ? 12:41:45 Such a tx in a block is getting confirmations, which would be a violation of protocol, while such tx in the transaction mempool is just a sign that someone is futzing with their client 12:43:03 (Or rather: it would imply a violation in the intent of the protocol, since we introduced the 10 confirmations requirement for spending a while back) 15:32:15 hi 15:55:19 https://moneroaddress.org/ still good, right? 15:55:30 hi presentjack[m] 16:07:47 gingeropolous: AFAIK yes 18:24:54 https://twitter.com/SarahJamieLewis/status/1354729912666517505 19:48:58 FIY, you want to know why you are getting those daily messages? Cults NEED to control information. That's why people like lh1008 get savagly attacked (also called disconnection) for even talking to me. Break the information embargo, break the cult. Who would sign up to Scientology if they knew from the get-go that is is about a sci-fi alien overlord? Who would sign up to MAGA if they knew what a loser Trump is? 19:48:58 You don't sign up to MAGA to do a failed Viking LARP and some time off in club fed. You sign up because you feel like shit and they promise to give you self-respect. It is a total lie of course, you are still a joke even when cosplaying a Viking. Just like Monero's promise of privacy is a lie. 19:58:06 hey ya'll, been unable to connect to remote nodes over gui on Qubes. What gives? 19:58:12 anyone else having this issue? 20:00:49 It just sits on "Network status: Connecting" 20:01:04 does Qubes use Tor? 20:01:18 yep, but this Qube I have setup is over clearnet 20:01:38 which remote node did you try? 20:01:41 your own or a public one? 20:02:23 so far ive tried node.moneroworld.com and uwillrunanodesoon.moneroworld.com 20:02:25 public ones 20:02:27 not my own 20:02:45 normally they work just fine, never had an issue 20:03:47 gingeropolous: ^ 20:03:53 gagdenfren: try a non moneroworld one 20:04:11 alright lets give it a go 20:04:13 e.g. node.xmr.to:18081 node.supportxmr.com:18081 20:05:02 gagdenfren, i've noticed during high network load that you need patience with remote nodes 20:05:11 how long did you wait before you bailed and tried a different one? 20:05:38 im trying this node atm - node.supportxmr.com 20:05:43 yeah selsta , my poor uwillrunanodesoon has 120 rpc cnxns currently 20:05:44 how long? idk normally within minutes I guess 20:06:06 i need to do that haproxy load balancing ive been talking about 20:06:22 yeah, try node.supportxmr.co and node.xmr.to 20:06:31 er, .com on the first one, ure already trin it 20:06:36 gingeropolous: is uwillrunanodesoon.moneroworld.com inside gdb currently? 20:06:41 yep 20:06:58 how long should it take to connect to a remote node? 20:07:14 it should be less than 20 seconds. if the node is slammed, can be a minute 20:07:29 im bout to change the url to runafuckingnodeforchrissakes.moneroworld.com 20:07:30 oh okay that helps 20:07:59 gagdenfren: node.xmr.to:18081/get_info works here 20:10:32 yep that node doesnt work 20:10:37 so its something on my end then 20:11:40 node.xmr.to:18081 also does not work for you? 20:11:44 not sure why though. I downloaded the latest gui version 20:11:51 uh im pretty sure i was using it 20:11:54 i'll double check 20:12:07 I guess Qubes like privacy, prevents you from doing the wrong thing :) (assuming the remote node isn't yours, which it usually isn't) 20:12:09 im just resetting my moner oqube 20:12:14 lol moneromooo 20:12:29 haha nah qubes will still let you give away ur privacy if you want 20:12:30 mebbe its firewalling outgoing cnxns? 20:12:47 Seriously, it's like telling some random "hey, here's my secret, don't tell anyone". 20:12:52 yeah i am concerned about some firewalling, so im rerouting it past the firewall and resetting the qube 20:13:24 Qubes is da best OS tho, if you aint using it I highly recommend it 20:13:29 whonix is so great with tor :D 20:16:47 EY IM IN 20:17:01 Damn, it was probably the firewall doin some weird shit 20:17:16 even though this qube has no firewalling 20:17:44 im connected through node.xmr.to 20:17:52 cheers guys 20:20:03 gagdenfren: there are also issues with high traffic remote nodes not accepting new connections 20:20:21 ah 20:20:37 welp, eitherway im in 20:46:46 Seriously, it's like telling some random "hey, here's my secret, don't tell anyone". >>> well, isn't that sorta similar to pushing a tx on the p2p network without tor/i2p? 20:46:58 i.e., the first to receive your tx in dandelion is a rando 20:47:20 i mean yeah, the rando has no way to know that its *your* tx 20:47:25 which i guess is the difference 20:48:59 i guess a hack would be to use the rpc to gather and construct the tx, and then disconnect from that rpc daemon, then reconnect to the p2p network to push as a normal node 20:49:07 which is kinda what the GUI does now mebbe 20:53:39 but that seems pretty silly. if it comes through via p2p, you can assume its not the senders. but if it comes through via rpc, it is the senders 20:53:48 so.... just push through p2p connection? 20:57:13 ugh someone matrix c++ coding skills into my brain 21:31:16 To some extent, but not the full extent. We removed a number of leaks from wallet to daemon, but it's really wasting time on stuff we should not have to. 21:31:50 I guess I'm just annoyed that people just don't give a shit. 21:32:44 Don't care about running their own nodes? Or don't care about wallet data leakage? 21:42:43 sethsisin smmons since you use copperheados what is your opinion on them registering grapheneos.ca and grapheneos.net and redirected them to their site as well as making legal threats to grapheneos devs? :) 21:42:53 i mean, if its not monero GUI users using remote nodes, they'd use either mymonero (stores viewkey), i guess cakewallet (runs their own remote node infra?), or keep their monero on exchanges 21:42:59 * sethsisin smmons since you use copperheados what is your opinion on them registering grapheneos.ca and grapheneos.net and redirecting them to their site as well as making legal threats to grapheneos devs? :) 21:43:08 That has nothing to do with Monero so feel free to DM me if you want to know more of my thoughts. 21:43:20 * sethsimmons since you use copperheados what is your opinion on them registering grapheneos.ca and grapheneos.net and redirecting them to their site as well as making legal threats to grapheneos devs? :) 21:43:22 obvi the last option is the worst, and the other 2 are .... better? 21:43:25 Cake defaults to their nodes but can use any. 21:43:30 than some rando? 21:43:41 And includes other community nodes that are already included with a single tap. 21:43:48 Probably, yeah 21:44:00 Thats why I'm trying hard to simplify the process of running your own node 21:44:17 Ideally we need a cheap plug-and-play solution, but simple VPS nodes via Ansible/Docker is a good interim IMO. 21:44:18 so centralized services are better than some rando? 21:44:32 Centralized and generally trusted, yes IMO 21:44:40 I would never recommend MyMonero though 21:44:51 But trusting a remote node without exposing view key is fine if not ideal. 21:45:00 But I always would point people to run their own node. 21:45:04 MyMonero has use cases 21:45:15 But I always would point people to run their own node. >>. yeah obvi 21:45:22 i wonder what the friction points are at this point 21:45:22 For sure, I just can't recommend them myself. Not a fan of exposing view key for any reason personally. 21:45:28 gagden damn we lost him 21:45:37 sethsimmons: ideally you would run your own mymonero node 21:45:44 Difficulty to run at home. 21:45:54 We need to have a simple GUI for running a node as a taskbar/tray service 21:45:56 use a remote node over tor if your worried about ip leak and dont want to run your own node. 21:46:08 Is that.. easy? 21:46:10 sethsimmons, so its always on? 21:46:20 I've never tried but that type of light-wallet server would be nice if simple to setup. 21:46:29 Yes, and starts at boot etc. 21:46:43 sethsimmons: vtnerd's light wallet server is as easy as running a normal node once you have it compiled 21:46:53 but this is all a bit early so issues still happen 21:46:53 Mostly the fact that you have to sync both a node AND the wallet. For someone who has no concept of what a block height is, that's a double whammy to start off 21:46:54 Once you're done with IBD resource usage is not noticeable IMO. 21:47:21 Yes, all the more reason people need to have an easy to run always-on node, so they only have to worry about wallet sync 21:47:37 Then long-term implement light-wallet server on your own node for no/fast wallet sync on top of that. 21:48:02 Might post on Reddit about this idea, actually, see if anyone is interested 21:49:11 Trouble is, most people don't have devices running 24/7 that aren't a phone or a router 21:49:20 Most people 21:49:24 Nor the concept of running a pc 24/7 in general 21:49:35 * Most people have a desktop or laptop that is on most of the time, IMO 21:49:49 So start on boot monerod is enough to remove the UX hurdle IMO 21:50:19 Sure, but then the complaints of "my pc is super slow when booting" will start rolling in 21:50:59 So if we want to go that way, we'd have to have a default setup that only uses like 1 core and minimizes impact on system performance 21:51:00 It would only cause a minor resource sink right when started up but can constrain bandwidth/CPU 21:51:44 * laughs in no data caps * 21:52:18 It wouldn't expose RPC externally or open up incoming connections by default, so data usage isn't a concern after IBD. 21:54:07 the .... womp womp of this is probably not many people need something up to transact every day 21:54:15 like, this sort of setup would be ideal for a merchant 21:54:34 Sad, but true for now 21:54:41 But we need to get ahead of real usage 21:56:47 but if its not synced and they go to use it and its gotta sync for a couple hours.... that kinda sucks 21:59:47 https://www.reddit.com/r/Monero/comments/l7a7pd/request_for_proposal_creating_a_light_monero/ 22:01:17 sethsimmons: https://ccs.getmonero.org/proposals/tobtoht_feather_dev_q1_2021.html 22:01:22 he has that listed 22:01:44 oh 22:01:44 Missed that item 22:01:50 I'll add a note about that 22:02:08 it will be quite a bit of work as you have to program for every OS separately most likely 22:02:45 C++ Windows, Objective C / Swift for Mac, and don’t know if Linux even has a standard for system tray icons 22:03:34 In that case would probably need a contributor per platform, in theory. 22:04:47 Would you mind commenting this info and any other ideas you have there, as you're much more familiar with what would be required? 22:10:20 sethsimmons: commented the same as I wrote here 22:10:23 did not think a lot about it 22:21:16 i hope 30 GB of space isn't too much to ask