Rucknium: moneromoooo: I literally have an open issue how coinbase are always 'pruned" in the RPC :p Sorry for being a couple days late to chime in.

I think coinbase txes cannot be pruned.

Well, I guess this isn't true. You can prune them, and the operatiom doesn't remove anyhting :D

So they can be pruned and unpruned at the same time, pedantically.

Hmm. Actually, it might remove one byte, the sig type...

kayabanerve: For now, can I get a coinbase tx's size by counting the bytes of `pruned_as_hex`?

Probably, since what is probably happening is that the pruned part is looked up, nothing (or empty) is found, so the code might be thinking the pruned part is missing.

(Guessing, I've not looked at the code)

The difference is either 0 or 1 byte anyway.

moneromoooo: My issue guessed they identified as pruned by virtue of being pruned by default lol

I have no code handling pruned TXs yet I handle coinbases without issue

So while, tbf, I don't handle networking code (and that may be where the difference is), I'd guess there's a 0-byte difference

Rucknium: should be fine. You apparently may be 1 byte off

Thanks. For my purposes that's close enough. I'm adding up the blockchain space used by p2pool payout transactions.

monero-project/monero #8311 for my issue and github.com/serai-dex/serai/blob/dev…p/coins/monero/src/rpc.rs#L252-L266 for the hell I coded around it. moneromoooo, I'd love if you chimed in the exact details/fixed my issue by having it appear in both (if there is no technicality on doing so) ;)

I'll try to get to it. I've got 20 hours left on my CCS which I have to work at some point...

:D Harassed an OSS dev into prioritizing my issue :D Today was a good day :D

/s. Obviously not the most important issue. Do what makes sense ;)

We can create an outgoing view key based on BP(+) steganography.

If a BP is from a seeded RNG (some derivation of the view pair), then it'll have a very specific output. You can perform stegnography via taking one of its scalars and adding/substracting some intended message. Recovery would be generating the same BP, and checking for a difference. There will always be a difference (as it'll either be completely different, and gibberish, or the encoded message). By checking if the message is the

desired value (hash of the private view key), we can confirm if the BP sender is saying it's to us.

Eh. This should be in lab. Will move.