08:13:33 <plowsof> trasherdk what file is created? does the .keys file exist without the cache? does it throw the !exists error? it functions correctly for me. is docker involved?
08:14:55 <m-relay> <t​rasherdk:monero.social> No, only the DB file. Pretty much the same size as a valid DB file `33112401` bytes.
08:19:29 <m-relay> <t​rasherdk:monero.social> This is the sequence:
08:19:29 <m-relay> <t​rasherdk:monero.social> ```
08:19:30 <m-relay> <t​rasherdk:monero.social> open_wallet: {
08:19:31 <m-relay> <t​rasherdk:monero.social>   error: { code: -1, message: 'Failed to open wallet' },
08:19:32 <m-relay> <t​rasherdk:monero.social>   id: '0',
08:19:33 <m-relay> <t​rasherdk:monero.social>   jsonrpc: '2.0'
08:19:34 <m-relay> <t​rasherdk:monero.social> }
08:19:35 <m-relay> <t​rasherdk:monero.social> close_wallet: {
08:19:36 <m-relay> <t​rasherdk:monero.social>   error: { code: -13, message: 'No wallet file' },
08:19:37 <m-relay> <t​rasherdk:monero.social>   id: '0',
08:19:38 <m-relay> <t​rasherdk:monero.social>   jsonrpc: '2.0'
08:19:39 <m-relay> <t​rasherdk:monero.social> }
08:19:40 <m-relay> <t​rasherdk:monero.social> create_wallet: {
08:19:41 <m-relay> <t​rasherdk:monero.social>   error: { code: -21, message: 'Cannot create wallet. Already exists.' },
08:19:42 <m-relay> <t​rasherdk:monero.social>   id: '0',
08:19:43 <m-relay> <t​rasherdk:monero.social>   jsonrpc: '2.0'
08:19:44 <m-relay> <t​rasherdk:monero.social> }
08:19:45 <m-relay> <t​rasherdk:monero.social> address: {
08:19:46 <m-relay> <t​rasherdk:monero.social>   error: { code: -13, message: 'No wallet file' },
08:19:47 <m-relay> <t​rasherdk:monero.social>   id: '0',
08:19:48 <m-relay> <t​rasherdk:monero.social>   jsonrpc: '2.0'
08:19:49 <m-relay> <t​rasherdk:monero.social> }
08:19:50 <m-relay> <t​rasherdk:monero.social> balance: {
08:19:51 <m-relay> <t​rasherdk:monero.social>   error: { code: -13, message: 'No wallet file' },
08:19:52 <m-relay> <t​rasherdk:monero.social>   id: '0',
08:19:53 <m-relay> <t​rasherdk:monero.social>   jsonrpc: '2.0'
08:19:54 <m-relay> <t​rasherdk:monero.social> }
08:19:55 <m-relay> <t​rasherdk:monero.social> Exiting...
08:19:56 <m-relay> <t​rasherdk:monero.social> ```
08:19:57 <m-relay> <t​rasherdk:monero.social> https://paste.debian.net/1313035/
08:50:45 <m-relay> <t​rasherdk:monero.social> It's easily avoided by just sending a create_wallet first, and catching that error, opening instead, but....
08:50:45 <m-relay> <t​rasherdk:monero.social> The `wallet_open` should return a `file not found` error.
19:03:12 <rbrunner> Do FCMP based transactions retain their "prunability"? Will it still be possible to throw away the bulk of the bytes, like it's possible for today's transactions if you choose to "prune" the blockchain?
20:00:01 <m-relay> <r​avfx:xmr.mx> I would like to know too, I was in the impression that FCMP would make it even more pruneable than it's possible now
21:28:51 <m-relay> <j​effro256:monero.social> Yes, it would be
21:29:33 <m-relay> <j​effro256:monero.social> FCMPs would basically just replace the binned reference set and groottle proofs in current Seraphis txs