10:53:27 <maxwilliamson> Hey guys, I'm wondering how subaddress scales.
10:53:46 <maxwilliamson> Can monero handle 100,000+ subaddresses in one wallet?
10:54:17 <azy> ye
10:55:37 <maxwilliamson> is that a yes?
10:56:02 <azy> it is
10:59:55 <Inge-> afaik more subadresses is basically like having a hash list to check against incoming tx, so very little overhead per extra subaddress
11:00:34 <azy> and you dont need to check each individual address for a payment, you can just look at the incoming transactions
11:00:44 <azy> it'll tell you which subaddress it's being paid into
11:00:51 <maxwilliamson> yeah that one I know
11:01:15 <azy> does the gui/cli wallet make handling 100k addresses easy? i'd imagine not
11:01:31 <azy> you can label them
11:01:50 <maxwilliamson> nah I'll be using rpc, no worries
12:55:19 <maxwilliamson> guys, if double_spent_seen is true, what steps should be taken?
12:56:08 <moneromooo> Typically increase the number of confirmations you require before assuming you'll keep the money long term.
12:56:51 <maxwilliamson> I'm also curious how the daemon will react if a block is orphaned
12:58:03 <maxwilliamson> if I get_transfer and get tx in an orphaned block, how does the daemon notify me?
13:00:27 <moneromooo> It doesn't. It has no idea what txes are yours.
13:00:51 <maxwilliamson> ah
13:01:42 <moneromooo> Well, scratch that. I'll assume you mean the wallet daemon. I'm not sure exactly, but some combination of --tx-notify (in the wallet) and --block-notify (in the node) should get you that.
13:05:50 <maxwilliamson> I'm trying to judge the best way.
13:06:19 <maxwilliamson> I need to receive payments.
13:06:39 <maxwilliamson> So, at first I thought I'll use tx_notify to watch for payments
13:06:50 <maxwilliamson> but then I need to track confirmations of indiv txes.
13:07:38 <maxwilliamson> I think using block-notify, and then sorting out txes with confirm > 3 is the best way
13:08:53 <maxwilliamson> waddya guys think?
13:20:19 <moneromooo> From memory, when I did this, I used get_bulk_transfers, and triggered at >= N confirmations.
13:29:47 <maxwilliamson> I think you are referring to get_bulk_payments but payment_id is phased out so..
13:31:13 <moneromooo> Quite possibly, the name was from memory.
13:31:26 <moneromooo> If you give an empty list of payment ids, it returns all.
20:03:12 <binaryFate> After computer has been suspended and woke up, I had monerod using a whole core fulltime even after bieng fully synced. Logs where non stop this:
20:03:15 <binaryFate> 2019-12-14 11:45:03.687 T Throttle throttle_speed_in: packet of ~0b  (from 0 b) Speed AVG=   0[w=9.205]    0[w=9.205] /  Limit=16 KiB/sec  [0 0 0 0 0 0 0 0 0 0 ]
20:03:16 <binaryFate> 2019-12-14 11:45:03.687 T Throttle <<< global-IN: packet of ~0b  (from 0 b) Speed AVG=   2[w=9.205]    2[w=9.205] /  Limit=8192 KiB/sec  [0 0 223 0 0 0 223 2655 5310 10620 ]
20:03:18 <binaryFate> 2019-12-14 11:45:03.687 T Setting -13:42:10.984143 expiry
20:03:20 <binaryFate> 2019-12-14 11:45:03.687 E Setting timer on a shut down object
20:04:05 <binaryFate> I guess the negative timer has to do with the suspending. No other clue what exactly was using one core non stop in the logs.
20:05:53 <kpcyrd> any chance the monerod binary tests for AVX2 instruction support during build?
20:06:19 <moneromooo> set_log to 0 till that's gone
20:06:33 <kpcyrd> I'm trying to run a binary I built on one computer on another computer but it segfaults with illegal instruction
20:06:34 <moneromooo> The throttle logs are *very* noisy when there's been a long pause.
20:06:39 <kpcyrd> the instruction being andn
20:06:53 <moneromooo> Hmm. Nevermind. Negative seems bad, yes.
20:07:17 <binaryFate> I don't mind about the logs, but it was using a lot of CPU. Gave it 20mn and then restarted it, then all good.
20:07:17 <moneromooo> Then build it on that computer, or set the arch to something the second computer supports.
20:09:07 <binaryFate> I think I had that twice, but did not care first time as I had to reboot shortly anyway. So I can probably reproduce.
20:10:12 <kpcyrd> moneromooo: how do I set the arch for the monero build
20:11:23 <moneromooo> The -march or -cpu option.
20:11:35 <moneromooo> One is old, I never remember which.
20:11:54 <moneromooo> binaryFate: how much time did that computer sleep ?
20:12:14 <moneromooo> (roughly)
20:12:43 <kpcyrd> this is what I have right now https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/monero#n44
20:12:43 <binaryFate> night + morning, The -13h timer might be correct
23:27:36 <maxwilliamson> hey guys, I'm getting problematic log lines
23:30:25 <maxwilliamson> nvm, figured ouit
23:30:47 <moneromooo> kpcyrd: if you look at CMakeLists.txt, it uses both -march and -mcpu. Use those. I think I was thinking of -mtune for the obsolete one.
23:31:20 <moneromooo> IIRC -march is what you want and -mcpu is the tune replacement.
23:31:45 <moneromooo> So you'd use -march=i386 to ensure the code gen can work on all i386 and later.
23:32:16 <moneromooo> The GCC doc likely lists the available archs.
23:52:30 <iDunk> I'd just try -D ARCH="x86-64".