17:06:24 <m-relay> <r​ucknium:monero.social> What is the status of FCMP pruning? Is the size of pruned FCMP txs known?
17:58:23 <m-relay> <o​frnxmr:monero.social> All ik is that a pruned db is about half the size of full db on stessnet, where all but ~7gb (full) is fcmp
17:59:11 <m-relay> <o​frnxmr:monero.social> That doesnt answer your question, but just an observation
18:24:44 <m-relay> <j​effro256:monero.social> The ratio should be lower on mainnet b/c the testnet history is dominated by lots and lots of empty blocks
18:25:09 <m-relay> <j​effro256:monero.social> Yes it's known, I can generate a table today
18:29:49 <m-relay> <r​ucknium:monero.social> That would be great. Thank you. I am looking at https://github.com/ArticMine/Monero-Documents/blob/master/TXSize2025R06.ods
18:35:30 <m-relay> <r​ucknium:monero.social> `get_transactions` with `decode_as_json:true` still has some elements named as RingCT, e.g. `rct_signatures` and `rctsig_prunable`. Is that intended?
19:43:14 <m-relay> <j​effro256:monero.social> Yes, you need to call with `prune=true`
19:44:52 <m-relay> <j​effro256:monero.social> `rct_signatures` will always be present b/c it contains info like RingCT version, fee, and output amount commitments (which are needed to scan RingCT txs)
19:45:54 <m-relay> <j​effro256:monero.social> A pruned transaction shouldn't contain the `rctsig_prunable` field though