luigi1112: please approve github actions here: monero-project/monero #8774

done

sech1: any idea here what causes bad_alloc? monero-project/monero #8790

selsta I commented there. Huge pages not working, it's not critical. It shouldn't spam logs though.

can someone please remind me where/how 'monero/crypto/amd64-64-24k.h' is generated, or how I can avoid using it?

ah nevermind, wasn't including it correctly :)

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 <libera.ems.host/_matrix/media/v3/do…d945823b59a993841e713bee0f4d434758a>)

* 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 <libera.ems.host/_matrix/media/v3/do…e7f38b5586a689892fb4804bed85dc85de2>)

This is 128-bit difficulty split into low and hig 64 bits

sech1: thx that make more sense

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?

* 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?

* 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?