Look on the bright side. At least you don't need to obsess over signs of life from FUK now.

I think everyone here knows that most Monero exchange withdrawals and desposits are traceable (Breaking Monero - poisoned outputs). How does it feel to go out and lie to people that they are private and then earn less than holding BTC on your bag?

Two more simple CI PRs from me. This concludes my "hot" ideas for this coding session. For the rest of the week I will focus more on reviews and user issues.

G'night.

@moneromooo the result of print_block +hex when nonce=0: paste.debian.net/1188606

Thanks

It's 0 in the dump, so the problem isn't in deserilization.

When not 0, is the nonce random, or always the same ?

random

Is the hex dump the same when it claims a non zero nonce ?

Since it can be parsed, the block dump is probably not corrupted, so it's likely it got saved with the wrong nonce by... wahtever stores it.

You're *sure* it's the same block, right ?

Like, it could not be two different blocks at the same height due to a reorg or somehting like that ?

the hex dump changes on the next non-zero nonce

'Oddly, no one who was directly involved with the SIR-C missions and currently still working the Lab, remembers the name Howard Chu, except for one who vaguely recalls Eugene Chu as having a brother names Howard'

Ed Caro, NASA Chief Engineer. cryptogazette.com/wp-content/uploads/2019/12/1-768x1445.png

get_blocks_by_height.bin only returns 1 block at that height, unless there is another way to check if there was a re-org and multiple blocks at that height

You'd get the alt blocks (there's a RPC for this) and compare height I guess.

Though if it was that, you'd get random mismatches, not just X and 0.

Where do you get that block from ?

ie, read from LMDB ?

it's returned from monero-daemon-rpc get_blocks_by_height.bin which is running a local stagenet within 2 folders in the same directory

I occasionally pop blocks to an earlier state if it could be related to that

Do you ever get bad info for another field than nonce ?

the other fields seem ok

jess: can you exclude xmr-pr from sigyn? looks like our github bot got killed for "spam"

or how does that work?

oops

where?

oh i see

results are returned from get_alternate_chains and get_alt_blocks_hashes but not for that height as far as I can tell

the bot is in #monero-dev, #monero-gui and #monero-site (not sure if important)

Ah, if you still have the "bad" DB the dump above came from, does the RPC still show 0, and is the hex dump still the same ?

who runs the bot?

dsc_

yes nothing has changed; it still returns nonce 0 for that block. guessing the sporadic failure was a result of testing different block ranges

selsta: i'll talk to them because it's a little tricky to give exempts to stuff that changes IPs

ideal would be give it an account and a cloak, then exempt the cloak

ok ty

ok. i gave it ip-based exemptions in the meantime