00:23:58 how to avoid for block unlock_time to get block number and not usual unlock_window (60) 00:24:33 without changes in my case block unlock_time = block height 00:37:21 anyone here 03:28:36 is it currently still recommended to run monerod with torsocks or rather with --tx-proxy? 04:51:50 what cpu is best for mining monero? 05:05:05 best by which criteria? 05:05:29 AMD 3900x is pretty good 05:05:36 Inge-, biggest hashrate 05:05:52 I have about 10k in the bank 05:06:00 I wanna start up a crypto mining shop 05:06:07 so then perhaps a new epyc 64-core system? 05:06:25 threadripper 3970x does 35+ KH/s 05:07:46 hmm 05:07:47 ok 05:07:53 best hashrate per dollar 05:09:43 take 10k and buy monero 05:10:23 you will get more monero that way 05:55:30 ^ 05:55:39 .mine 35000 09:07:33 niocbrrrrrr: who does actually mine monero then? I mean, for someone out there it must be profitable... 09:48:35 The matrix has broken. 09:49:26 reddit.com/r/glitchinthematrix 10:09:26 hm. BTC congesting 10:10:08 buy buy buy 10:35:10 is it still recommended to run monerod with torsocks or rather with --tx-proxy? 10:57:25 hello 16:26:50 I am unable to create a wallet on my Nano X from the Monero GUI. I keep getting this message: Error writing wallet from hardware device. Check application logs 16:26:57 Please help. 16:40:35 Al97: Are you running the most recent Ledger Monero App and Ledger Live firmware? 16:42:34 I just downloaded the most recent .15.0.4 and I just did the same with the ledger. I would think that the ledger would have given me the most up to date. I downloaded the ledger about a week ago. 16:47:44 Al97: What is the exact error? It should say more. 16:49:57 That's all it says in red under the advanced options arrow whenever I click create wallet 16:51:24 Are you running Ledger Monero app v1.5.1? Is the Ledger Monero app opened? 16:51:30 is Ledger Live closed? 16:53:16 it was closed. Now its open. I think this may have been a breakthrough (noob learning). I will reach back out if not. Thanks. 16:54:32 Ledger Live should be closed 16:54:39 so that it does not interfere with Monero 16:55:20 Al97: Which operating system are you using btw/ 16:55:23 It was closed when my error message came. 16:56:14 But I opened ledger live and the device asked me to accept or reject when I clicked create wallet. I have not selected either on the device yet. 16:56:36 Al97: see on the bottom there should be a second message https://usercontent.irccloud-cdn.com/file/tdG7atJc/error 16:56:44 this is the important message 16:57:18 also when creating a wallet you have to accept it on the ledger by exporting your view key 16:58:33 I am running windows 10 64 bit 16:58:59 I just didn't know if you wanted me to accept it yet because ledger live is open 16:59:16 yes, accept it 16:59:26 even with ledger live open? 16:59:26 Ledger Live being open can be a problem but not necessary 16:59:31 ok 16:59:44 so if there is a problem try again with Ledger Live closed 17:00:07 ok. asking me to give wallet a PSWD 17:00:19 okay, seems to work now 17:00:46 I think so. I'll reach out if problems arise. You guys are moneyJ! Thanks! 17:01:00 no problem 18:58:27 @M5M400 are you there? 20:00:02 hey i was just poking around and it seems the hashes for cli in hashes.txt on getmonero.org are for a newer release than what is downloadable (0.15.0.4) 20:00:20 the hashes are for 0.15.0.5 20:01:46 ping binaryFate I think 20:01:46 pong 20:06:20 I'm a noobie to Monero and am trying to learn a bit more about it. Ring signatures provide plausible deniability from a blockchain analysis perspective, but if a passive network adversary observes you broadcasting a send transaction does that effectively negate the senders anonymity? 20:06:53 numin0us, not really 20:07:11 possibly degrades it, but the adversary still doesn't know which input is the broadcasters 20:07:40 there's also a new feature called dandelion++ that helps mitigate passive observer information collectors 20:16:46 Ah cool that seems pretty neat! Can it be used in conjunction with TOR/VPNs, and does that add extra protection? 20:22:05 Also, is there any documentation about how new features are added to Monero? I'd be interested to know how it differs from bitcoin @jwintern 20:22:16 @jwinterm 20:24:05 uh, it's a more speedy process for sure numin0us 20:24:17 not sure how much formalized structure there is around it 20:24:36 also, I believe it can be used with tor, definitely vpn 20:24:58 numin0us, #monero-dev is the development channel here and there are discussions on github issues 20:25:19 #monero-research-lab is a channel for discussing lower TRL type changes I guess 20:25:23 further out changes 21:05:34 22:00 hey i was just poking around and it seems the hashes for cli in hashes.txt on getmonero.org are for a newer release than what is downloadable (0.15.0.4) <-- GUI is v0.15.0.4 CLI is v0.15.0.5 21:29:59 right but 0.15.0.5 is not on getmonero.org, and the non-gpg-signed hashes displayed on the web page are for 0.15.0.4 as well 21:31:13 grubles: it is on getmonero.org 21:31:28 can you make a screenshot? 21:31:41 can you try a different browser / clear your caches 21:31:51 oh yeah that's my mistake 21:32:00 i somehow downloaded the gui 21:34:43 hey grubles: The CLI version downloadable on getmonero.org should be 0.15.0.5 and this is indeed the case as far as I can see. Did you maybe confuse with GUI version (still 0.15.0.4)? 21:35:28 ah I missed the last lines of discussion above. Nevermind, glad you sorted it out 23:33:32 on blockchain.cpp there is "unlock_time is either a block index or a unix time" 23:33:44 in my case is always block index 23:33:54 without changes 23:34:06 any suggestion? 23:34:21 if i'm not mistaken, it is unix time only for very old transactions, like a few years ago now. 23:36:43 for new chain without changes when mining start always unlock_time = block number 23:37:22 i cant understand why decide that unlock_time must be block number and not time 23:37:42 i cant understand why decide that unlock_time must be block number and not 60 23:38:23 it's easier for every node to agree on the same block number than the same time, i think 23:38:32 you would only see the old behavior if you were running very old software 23:39:38 u mean that if i inert v12 i wont c this 23:40:39 also, minutes per block varies randomly. so if you only have 2 blocks in 20 minutes, instead of 10, using the time instead of the block number would result in weakened security 23:42:48 i'm not sure in which version the change was made. older than 0.12, i think 23:43:25 even if i insert v12 on 2block same behaviour! 23:43:35 i don't understand what you mean by that. 23:44:37 if i change hardfork file to start with v12 on 2block 23:44:57 why would you expect that to change the behavior? and why do you want to change it in the first place? 23:45:13 block number is the correct way, using timestamp in the beginning seems to have been a mistake. 23:46:32 if block number is 999 unlock_time will be 999 23:46:58 is this positive? 23:54:11 what are you using to construct the transaction? monero-wallet-cli sets it to 0 by default, at least in v0.15 23:54:32 im talking about new chain 23:54:33 but having it be the current block number has the same effect (tx can be spent immediately) 23:54:54 ndorf: he is trying to fork monero for a few months now lol 23:55:23 lol 23:55:27 the wallet that constructs the tx picks the unlock_time. why is new chain relevant? 23:55:39 ah 23:55:49 thanks for the heads up, lol 23:56:13 assume everyone is i guess? 23:56:23 anybody who's anybody has their own monero fork 23:57:09 anybody who's anybody ?? 23:57:19 I am nobody :( 23:57:41 nobody is nobody