02:28:29 <ezra> Hey guys, whats the best way to accept payments with monero
02:28:37 <ezra> i dont want to use a service like coinpayments
02:29:05 <ezra> and i saw that monero hasa RPC api that comes shipped with the node but it looks like its only one walletat once
02:49:13 <ezra> actually i realized i can use paymentIDs
06:37:24 <dEBRUYNE> ezra: Make sure to use integrated addresses or subaddresses
06:37:29 <dEBRUYNE> long payment IDs have been depreciated
07:04:02 <ezra> yes that is fine dEBRUYNE i understand
07:04:10 <ezra> thats what i meant
07:04:13 <ezra> just wording was bad
08:20:31 <ErCiccione[m]> Does anybody see any issue with this? https://github.com/monero-project/monero-site/pull/1004
08:21:23 <ErCiccione[m]> If not i'll just ACK it. Makes sense to me.
08:22:22 <naughtyfox> Hey guys! I have quick question. Why do we seeding randomx hash with epoch start block hash? What did it made for?
14:37:24 <pricode> who do i need to poke in order to get this request merged ?:) https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/147
15:00:16 <hyc> naughtyfox: a seed hash is used so that the dataset doesn't need to be fully reinitialized on every hash
15:00:29 <hyc> the dataset init time is on the order of several seconds
15:02:03 <naughtyfox> so that's not a security reason, right? just a speed up?
15:02:22 <dEBRUYNE> pricode: It first needs to be reviewed by the community
15:03:13 <hyc> naughtyfox: pretty much. the epoch size, 2048 blocks, was chosen to be large enough to amortize the cost
15:03:34 <hyc> without giving too much of a precompute advantage
15:03:59 <hyc> why do you ask?
15:04:40 <naughtyfox> i was just watching the implementation and realized i gave the gap :)
15:05:10 <naughtyfox> just didn't understand what is it made for and decided to ask
15:05:35 <naughtyfox> i'm gonna read something about randomx inner workings. could you suggest sumething?
15:05:55 <naughtyfox> what is dataset for, for example
15:06:15 <asymptotically> naughtyfox: https://github.com/tevador/RandomX/blob/master/doc/design.md
15:06:38 <asymptotically> and specs.md goes into more detail
15:08:08 <naughtyfox> thank you
15:25:22 <dEBRUYNE> Does anyone remember what arguments were raised in opposition of encoding the restore height as word of the mnemonic seed?
15:25:32 <dEBRUYNE> It would add one additional word if I recall correctly
15:25:54 <dEBRUYNE> I remember it was briefly discussed a few years ago, but cannot distinctly remember why it was never implemented
15:28:18 <rbrunner> I don't remember either - maybe before my time - but I just can't imagine how you could encode so many bits in a single word.
15:33:58 <hyc> yeah, a single word is only worth about 11 bits
15:34:07 <hyc> maybe 12
15:35:31 <dEBRUYNE> Could maybe do the first two or three and pad with zeroes?
15:35:36 * dEBRUYNE not sure if that makes sense at all
15:49:26 <moneromooo> You don't have to encode the exact height, just a quantized low bound.
15:55:33 <fluffypony> I think I made an argument for just making it an index of every 100k blocks
15:55:49 <fluffypony> so 0 = beginning, 1 = > 100k < 200k etc.
15:55:57 <fluffypony> sorry > 0 < 100k
15:56:00 <fluffypony> you know what I mean