08:00:11 -xmr-pr- slumericanB opened issue #8689: Pull 08:00:11 -xmr-pr- > https://github.com/monero-project/monero/issues/8689 13:45:11 -xmr-pr- ovhpse opened issue #8690: No stack trace on fedora 37 unless forcing libunwind 13:45:11 -xmr-pr- > https://github.com/monero-project/monero/issues/8690 17:08:16 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. 17:48:11 I think coinbase txes cannot be pruned. 17:48:32 Well, I guess this isn't true. You can prune them, and the operatiom doesn't remove anyhting :D 17:48:48 So they can be pruned and unpruned at the same time, pedantically. 17:49:09 Hmm. Actually, it might remove one byte, the sig type... 18:19:02 kayabanerve: For now, can I get a coinbase tx's size by counting the bytes of `pruned_as_hex`? 18:27:48 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. 18:28:11 (Guessing, I've not looked at the code) 18:28:26 The difference is either 0 or 1 byte anyway. 18:30:51 moneromoooo: My issue guessed they identified as pruned by virtue of being pruned by default lol 18:31:08 I have no code handling pruned TXs yet I handle coinbases without issue 18:31:28 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 18:31:40 Rucknium: should be fine. You apparently may be 1 byte off 18:33:38 Thanks. For my purposes that's close enough. I'm adding up the blockchain space used by p2pool payout transactions. 18:34:47 https://github.com/monero-project/monero/issues/8311 for my issue and https://github.com/serai-dex/serai/blob/develop/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) ;) 18:50:57 I'll try to get to it. I've got 20 hours left on my CCS which I have to work at some point... 18:54:31 :D Harassed an OSS dev into prioritizing my issue :D Today was a good day :D 18:54:45 /s. Obviously not the most important issue. Do what makes sense ;) 22:38:43 We can create an outgoing view key based on BP(+) steganography. 22:41:52 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 22:41:52 desired value (hash of the private view key), we can confirm if the BP sender is saying it's to us. 22:42:15 Eh. This should be in lab. Will move.