00:17:09 <xtuh> .mine 1000
00:17:18 <xtuh> .mining 1000
00:17:28 <xtuh> .pool 1000
00:17:33 <xtuh> .?
03:26:36 <gingeropolous> xtuh, checkout #monero-pools
09:37:34 <dEBRUYNE> https://twitter.com/TheBitfi/status/1331303523296948224
09:37:45 <dEBRUYNE> If Trezor and Ledger managed to get it properly up to date in time, surely they should be able to do too?
09:55:29 <fluffypony> dEBRUYNE: they're talking nonsense
09:55:43 <fluffypony> they use MyMonero's backend, and they haven't paid in like a year, so we've cut them off
09:56:03 <fluffypony> I'm waiting for the lawyer to wake up and then I'll see about making a public statement
09:56:45 <selsta> no idea what bitfi even is
09:56:59 <fluffypony> also I'm like 90% sure that woodser's C++ lib can be compiled for ARM
09:57:08 <fluffypony> so it's doubly nonsense
09:57:10 <selsta> hardware wallet?
09:57:29 <fluffypony> selsta: yeah - basically an "airgapped" Android device that you have to enter your seed into each time
09:59:06 <dEBRUYNE> Yeah they use a 'passphrase == seed' feature basically
09:59:23 <selsta> hmm I remember now, that’s the McAfee wallet
09:59:46 <dEBRUYNE> Right
10:00:08 <dEBRUYNE> It is basically like a brain wallet, which numerously has proven to be insecure
10:01:59 <dEBRUYNE> fluffypony: If they use the back-end of MyMonero, presumably no code related changes are required on their side, right?
10:02:11 <dEBRUYNE> Thinking of it, that may not necessarily be the case
10:03:08 <selsta> if the transaction is generated locally code changes are required
10:19:08 <xmrmatterbridge> <rbrunner7> "they use MyMonero's backend, and they haven't paid in like a year, so we've cut them off" Really wonderful to hear such background info first-hand.
10:21:15 <fluffypony> dEBRUYNE: yeah they would just pull in the latest MyMonero library and off you go
11:59:42 <fluffypony> https://twitter.com/fluffypony/status/1331567968657039360
12:04:13 <sethsimmons> <fluffypony "https://twitter.com/fluffypony/s"> Thanks for that, makes a lot more sense now
12:10:41 <selsta> luigi1111w: you available today for tagging?
12:14:42 <selsta> .merges
12:14:42 -xmr-pr- 6747 6826 6829 6830 6849 6856 6858 6873 6892 6895 6897 6898 6903 6913 6915 6920 6921 6922 6924 6937 6943 6949 6954 6960 6971 6973 6995 6999 7008
12:15:20 <selsta> .merge+ 7018 7020 7021
12:15:20 <xmr-pr> Added
13:02:13 <dEBRUYNE> fluffypony: I see, thanks for clarifying
13:02:22 <dEBRUYNE> Even more astounding then
13:02:50 <dEBRUYNE> They blame their own refusal to pay on the Monero developers essentially, whilst CLSAG was a worthwhile upgrade and announced significantly in advance
13:49:12 <ErCiccione> selsta moneromooo: what phrasing do you suggest to use here? i want to make sure it's clear https://github.com/monero-project/monero-site/pull/1328
13:50:39 <selsta> "Will be undefined"
13:53:10 <ErCiccione> So only "will be undefined if node is fully synced"? no mention of zeros?
13:55:02 <ErCiccione> Well i guess it cannot be zero, if it's undefined once you are fully synced
13:56:34 <lh1008> Hello everyone, I'll drop this link here. Maybe someone knows what might be happening. https://github.com/monero-project/monero/issues/7041
13:57:04 <lh1008> I'll try to do do it in another wallet and see if it happens again. :) Good day everyone
14:02:22 <selsta> ErCiccione: it can be zero but not guaranteed so undefined is better
14:02:52 <ErCiccione> got it. Thanks. Just pushed the change
15:10:28 <luigi1111w> selsta yes
15:10:51 <luigi1111w> what's the list?
15:11:11 <selsta> ok, 7039 and 7044
15:11:18 <selsta> you have to approve 7044
15:12:42 <selsta> tag name is v0.17.1.5
15:26:04 <janrummens> is it 'consensus' that determines what miner program to use? There must be a way to opt for a certain miner program. If the majority of nodes use RandomX a new node that uses an old mining algo will not be able to connect to other (or to less) nodes?
15:27:14 <sethsimmons> The mining algorithm, not program, is a part of consensus rules.
15:27:14 <sethsimmons> No one can produce a valid block that is not created using RandomX.
15:27:50 <janrummens> ok and how is this imposed?
15:28:05 <janrummens> by versioning?
15:28:17 <sethsimmons> Restricting to a single program would be detrimental to the ecosystem, multiple miners are ideal.
15:28:34 <sethsimmons> I’m not sure how the consensus rule around mining is technically enforced.
15:29:26 <janrummens> that is what I'm trying to find out
15:30:23 <janrummens> I read that bitcoin has some versioning, so that two nodes connect if they have the same version.
15:30:33 <sethsimmons> I’m sure someone else in here knows the technical details 🙂
15:30:53 <janrummens> would be very gratefull to understand this
15:32:38 <luigi1111w> selsta just those two patches and tag?
15:32:51 <selsta> yes I think so
15:33:00 <selsta> we merged the other things yesterday
15:33:52 <luigi1111w> there you go
15:33:54 <luigi1111w> plz confirm
15:39:44 <selsta> confirmed
15:54:23 <selsta> iDunk scoobybejesus hyc TheCharlatan jonathancross and whoever else participates in reproducible builds, v0.17.1.5 would be tagged now
15:54:42 <iDunk> Already building
15:54:51 <selsta> nice :)
15:55:13 <iDunk> I'll have to leave soon, so my hashes might be a bit late.
16:08:37 <ErCiccione> Some RPC calls need to be documented. Any help would be appreciated: https://github.com/monero-project/monero-site/labels/%F0%9F%93%9A%20docs%3A%20dev%20guides
16:31:38 <moneromooo> janrummens: by calculating the hash the miner claims to have calcualted, and chekcing it's below the target. The chances of it being below the target for hte wrong algorithm are very very slim.
16:31:55 <moneromooo> But if it passes, it'll be accepted anyway.
16:34:14 <janrummens> @moneromooo so it uses a specific way of calculating the hash?
16:34:43 <moneromooo> Yes. Hashes are deterministic.
16:35:00 <janrummens> heu?
16:35:46 <janrummens> I'm a bit lost now.
16:37:24 <moneromooo> It means a given set of inputs always yields the same output.
16:37:36 <janrummens> they are deterministic in the type of hash algoritme then. MD5, SHA-256, etc
16:38:13 <janrummens> "It means a given set of inputs always yields the same output" ha ja ok
16:38:41 <janrummens> besides the collisions :-)
16:39:51 <janrummens> "The chances of it being below the target for hte wrong algorithm" this I don't fully understand
16:40:56 <moneromooo> Easy to see with a contrived example: Set the hash of a message (made from bytes) to be the 8 bit value made by xoring all the bytes, with a starting value of 0.
16:42:03 <moneromooo> If you hash that message with H1 and get a value below, say, 8, then you hash it with H2, which is a similar algorith, but adds the bytes instead, it'll sitll be below 8 for 1/32 inputs on average (assuming random inputs).
16:42:26 <moneromooo> Now the hashes we work with have 256 bit output.
16:43:11 <janrummens> ok ok yes I see
16:44:10 <jonathancross> <selsta "iDunk scoobybejesus hyc TheCharl"> Thanks for the ping!
16:45:11 <janrummens> thank you for this explanation !
16:49:45 <dEBRUYNE> Will make a Reddit thread for the hashes
16:49:54 <dEBRUYNE> & Don't forget to make pull requests on the gitian sigs repo too :p
16:50:12 <janrummens> one other question how does a node who want to solve the puzzle what hash algo it needs to use? Is it just by looking at the target?
16:52:32 <janrummens> or does it randomly executes the H1,H2, etc?
16:53:19 <moneromooo> It knows by looking at the block major version. It changes when the hash algorithm changes.
16:53:36 <scoobybejesus> my hashes: https://paste.debian.net/1174296/
16:57:13 <janrummens> ok I see the missing piece (I think), much appreciated
16:59:54 <janrummens> must go through the example and have a look in the code. is their an extensive explanation besides https://github.com/tevador/RandomX and would like to find the code
17:00:13 <janrummens> where this : "It knows by looking at the block major version"
17:00:46 <janrummens> happens
17:01:45 <janrummens> so the argon, blake, are the algo's?
17:03:49 <janrummens> ok I suppose https://github.com/tevador/RandomX has enough info :-)
17:07:21 <janrummens> the audits are interesting as well, sorry to spam you with this. will stop. cy.
17:31:29 <TheCharlatan> thanks for the ping selsta
18:11:06 <selsta> my nodes started banning a lot of peers, anyone seeing something similar?
18:12:03 <selsta> a lot of them appear to be tor exit nodes
18:18:21 <TheCharlatan> selsta with .5?
18:18:40 <selsta> with .3
18:21:59 <hyc> yes, seeing that too. probably wallet-rpc connections triggering it
18:22:19 <hyc> but could be p2p as well, haven bumped loglevels to check
18:22:46 <selsta> seems to me that someone trying something with tor exit nodes
19:01:11 <hyc> ironic, since they could just connect to my onion address instead of exiting tor network at all
19:04:57 <moneromooo> Or it's some asshole who wants to prevent others from using tor exit nodes to use monero nodes. More incentive to run hteir own node :)
19:11:53 <hyc> ah that kinda makes sense, discourage people from using tor because it's decreasing the effectiveness of his own asshole nodes
20:44:01 <iDunk> https://paste.debian.net/hidden/0a8afa26/
20:46:17 <hyc> ah didn't realize it was tagged, starting a build now
22:28:38 <keatonofthedrake> Hey Dev chat, getting a really weird issue on Windows 10 64 bit version 17.1.4. The application will be open for a random amount of time and then both my screens go black for a few seconds, the desktop re-appears and the Monero GUI is no longer open. Is there any log that I can provide for helping with trouble shooting?
22:31:00 <keatonofthedrake> Trying to re-open the GUI now and it gets to the password lock screen then does the black screens and its no longer open when the desktop appears again
22:33:01 <keatonofthedrake> trying the low graphics mode the application has opened again and hasnt crashed
23:19:19 <selsta> keatonofthedrake: your Windows screens going black sounds a bit graphics drivers related, but not sure from the description
23:20:25 <keatonofthedrake> hey selsta yeah its the first time its ever done that through all the different releases. Running a RTX 2070 with updated drivers. wondering if there was a log of the crash I could provide from somewhere