07:36:06 <qorafsssbej> 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.
07:36:06 <qorafsssbej> 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.
11:58:47 <janrummens> I'm not an expert and read some books and did a little gpu mining on Monero
12:00:09 <janrummens> BUT could you point me to a cloud operator where I can lease some hardware mining equipment? No pools please.
12:04:55 <moneromooo> Try #monero, but cloud mining is extremely unlikely to be profitable.
12:05:18 <moneromooo> Especially GPU mining for monero.
12:05:47 <janrummens> yes thanks but want to switch to ryzen
12:08:40 <janrummens> have another question about nounces
12:09:07 <janrummens> I suppose that the nounces are used in monero like in bitcoin.
12:09:30 <janrummens> the generation of nounces is this always incremental?
12:09:52 <moneromooo> Whatever the miner feels like.
12:10:01 <moneromooo> Incremental is just easy/fast.
12:10:26 <janrummens> are the different schemes configurable?
12:11:01 <moneromooo> Sure. With the monerod miner, just replace the ++ with whatever function you want.
12:11:45 <moneromooo> There's not much point though, since you can't tell by looking at the starting nonce whether you'll find a hash below target without actually doing the work.
12:12:43 <janrummens> true, is there some parallellism involved and / of configurable?
12:12:51 <moneromooo> If you're on about fingerprinting the mining software, the monerod miner starts to increment from a random value, so that should not be fingerprintable since only the end nonce gets published.
12:13:34 <moneromooo> Hashing can be parallel, yes. Nonce generation is pointless to make parallel, it's just trivially fast and threaidng it would slow things down a lot.
12:13:58 <moneromooo> Maybe "generation" is a misnonmer, it implies substantial work.
12:14:01 <janrummens> yes indeed meaning hash generation
12:14:14 <moneromooo> Ah, then definitely.
12:14:41 <janrummens> but because it is random it is pure brute force
12:15:04 <moneromooo> Mining is brute force due to the properties of a good hash function.
12:16:54 <janrummens> so in order to be profitable you need to go above a certain threshold with your mining hardware hash generation ability.
12:17:19 <moneromooo> Yes, but since this doesn't seem to be about coding, see #monero for more.
12:17:32 <moneromooo> Unless you have questions about the code :)
12:18:23 <janrummens> not for the moment, though I'm massevly interested in the RandomX mining code and such.
12:19:43 <janrummens> thanks a lot for your time, I will come back with my questions on the code (c/c++ I have seen) if the gods permit it ;-)
12:19:53 <moneromooo> Sure.
12:20:51 <janrummens> Nice documentation by the way on the code around RandomX.
14:41:55 <gingeropolous> so,. because monero's gonna rocket to the moon and we'll inch ever closer to ossification, should we try and get some rough consensus going about that tx_extra?
14:41:58 <gingeropolous> https://github.com/monero-project/monero/issues/6668
14:42:30 <gingeropolous> im liking the "allow tx_extra in coinbase tx" options. leaves wiggle room, but ensures user-tx uniformity
14:42:53 <hyc> so only miners can stuff something into tx_extra?
14:44:04 <gingeropolous> yeah
15:15:15 <gingeropolous> i mean, it seems to have a rough consensus. I'm just curious if we're at the stage where we throw it really out there (i.e., reddit) to see what further sentiment might exist
15:29:00 <gglgsjzgkxe> Why does the Saviour of NASA take a group achievement award and present it as a proof of individual glory? twitter.com/hyc_symas/status/1203709575226183683
15:59:46 <gingeropolous> master is on xmrchain  (v0.17.0.0-dcba757dd)
18:59:00 <sech1> moneromooo how is the password applied when opening wallet? I mean how many passwords/second can be tested?
18:59:41 <sech1> i.e. I want to know the safe password length
19:00:01 <wfaressuissia[m]> cn/0 is bottleneck there
19:00:19 <wfaressuissia[m]> so cn/0 hashes per seconds
19:01:18 <sech1> I think I've found the code but there's also kdf_rounds parameter, so more than 1 cn/0 hash is calculated?
19:02:52 <luigi1111w> I think by default only 1
19:03:13 <moneromooo> Defaults to 1.
19:04:11 <sech1> If I set kdf-rounds from command line when creating the wallet, do I need to set it every time I open it?
19:04:45 <moneromooo> I think so.
19:05:15 <sech1> That's interesting. If cn/0 is used, then those original ASICs can be used to crack weak passwords
19:08:15 <luigi1111w> correct. Still fairly slow I would wager
19:21:46 <sech1> I did some math: given 1 joule/kh spent (2x the efficiency of Antminer X3), price of energy $0.03/kWh, $1 is enough to check 120 billion passwords. $1M is enough to check 120e+15 passwords. 10 characters password [a-zA-Z0-9] should be enough
19:29:57 <PurpleBerries> people use passwords that short?  0_o
19:38:26 <moneromooo> I use 1 character passwords, on the assumption no cracker will think I'm that dumb and start at 2.
19:39:38 <sech1> If the password is random and uses large enough character set, it can be short, but 10 characters is reasonable minimum
19:45:10 <wfaressuissia[m]> just spent 30 minutes and memorize whole secret spend key (only 64 characters)
19:45:12 <Inge-> sech1: the peeps behind hashcat looked at it some years back - and concluded it was pretty difficult
19:45:28 <wfaressuissia[m]>  * just spend 30 minutes and memorize whole secret spend key (only 64 characters)
19:45:41 <sech1> No way
19:46:01 <sech1> I spent a few days to memorize Pi to 30 digits
19:46:26 <sech1> Maybe I'm just bad at remembering random numbers...
19:46:47 <moneromooo> Did you go around in circles better after that ?
22:02:09 <selsta> .merges
22:02:10 -xmr-pr- 7332 7349 7373 7391
22:25:41 <moneronero> was cryptonote project moved to monero? it seems to be dead since 2015, is there an equivalent project today?
22:27:23 <moneromooo> Monero is based off cryptonote.
22:27:31 <moneromooo> The two have diverged over the years.
22:27:50 <moneromooo> There's a number of forks of more recent CN code AFAIK.
22:28:40 <moneronero> i see
22:29:36 <moneronero> is there any guide on forkin monero just like the cryptonote one? it seems pretty self explanatory, I was reading monero source and it's very big with lots of extra stuff that cryptonote doesn't have
22:29:50 <moneromooo> No.
22:38:10 <selsta> .merge+ 7088 7238 7310 7326 7358 7459 7460 7615 7620 7621 7622 7623 7631 7632 7636 7637 7638
22:38:10 <xmr-pr> Added
22:39:08 <gingeropolous> v0.17.0.0-dcba757dd uptime 0d 6h 42m 17s
22:39:09 <gingeropolous>  on xmrchain
22:39:24 <selsta> any concerns with adding https://github.com/monero-project/monero/pull/7387 ? we tested it on mac and linux and seems to work
22:39:25 <luigi1111w> bruh
22:39:27 <luigi1111w> .merges
22:39:27 -xmr-pr- 7088 7238 7310 7326 7332 7349 7358 7373 7391 7459 7460 7615 7620 7621 7622 7623 7631 7632 7636 7637 7638
22:39:28 <luigi1111w> .soon
22:41:52 <mwtqkmmn> “I thought, ‘I’m going to pump it and dump it,’ because I was interested and taking the ideas and implementing them in bitcoin. The bitcoin code base was far more interesting to me than monero, and I thought, ‘I’m not going to work on this codebase, it’s terrible,'” he recalls - fluffypony in an interview about Monero
22:43:27 <moneromooo> If it works, why not.
22:44:09 <selsta> functional tests will require 2 new python dependencies is the downside
22:44:24 <selsta> but cmake will skip the test if they are missing like with requests
22:45:06 <moneromooo> Common ones ? If it's stuff that doesn't come in OS packages, it looks like a bad idea.
22:45:37 <selsta> psutil monotonic
22:45:53 <selsta> not sure how "common" they are
22:46:34 <iDunk> mingw-w64-x86_64-python-psutil & mingw-w64-x86_64-python-monotonic in MSYS2.
22:47:20 <selsta> iDunk: could you test if 7387 breaks functional tests on windows? I never got tests running on Windows
22:47:56 <moneromooo> Looking at it it's a bit weird it cals pi rather than, say, CN, as a "let's use up CPU" function :)
22:47:58 <iDunk> IIRC, functional_tests fail on other stuff on Windows, but I'll try.
22:48:19 <moneromooo> I've got those two on fedora. Phew.
22:56:48 <selsta> moneromooo: I think you can close 7272 as it was replaced by 7308 if I understand this correctly
22:57:42 <moneromooo> Yes, I think it did. I'll close.
23:12:24 <selsta> .merge+ 7520 7538 7542 7549
23:12:25 <xmr-pr> Added