01:00:53 <selsta> luigi1112: please approve github actions here: https://github.com/monero-project/monero/pull/8774
01:01:55 <luigi1112> done
02:22:41 <selsta> sech1: any idea here what causes bad_alloc? https://github.com/monero-project/monero/issues/8790
05:29:27 <sech1> selsta I commented there. Huge pages not working, it's not critical. It shouldn't spam logs though.
21:01:44 <woodser[m]> can someone please remind me where/how 'monero/crypto/amd64-64-24k.h' is generated, or how I can avoid using it?
21:05:54 <woodser[m]> ah nevermind, wasn't including it correctly :)
22:27:39 <someoneelse49549> Hi, can someone explain to me the purpose the difficulty_low/difficulty_high field in `alt_block_data_t`. In blockchain.cpp its used like this:... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/04d66d945823b59a993841e713bee0f4d434758a>)
22:27:58 <someoneelse49549>  * Hi, can someone explain to me the purpose the `difficulty\_low`/`difficulty\_high` field in `alt_block_data_t`. In blockchain.cpp its used like this:... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/abddae7f38b5586a689892fb4804bed85dc85de2>)
22:32:03 <sech1> This is 128-bit difficulty split into low and hig 64 bits
22:32:48 <someoneelse49549> sech1: thx that make more sense
23:36:35 <someoneelse49549> monerod is storing the cumulative difficulty as a uint_128t (theorically as its boost), but for now the cumulative difficulty (269952836198516580) have reached 1.46% of the total value a uint_64t can take. Is there any chance in a reasonable future the upper 64 bits can be occupied?
23:36:57 <someoneelse49549>  * monerod is storing the cumulative difficulty as a uint_128t (theorically as its boost), but for now the cumulative difficulty (269952836198516580) have reached 1.46% of the total value a uint_64t can take. Is there any chance in a reasonable future the upper 64 bits can be occupied?
23:42:23 <someoneelse49549>  * monerod is storing the cumulative difficulty as a uint_128t (theorically as its boost), but for now the cumulative difficulty (269952836198516580) have reached 1.46% of the total value a uint_64t can take. Is there any chance in a reasonable future that the upper 64 bits can be occupied?