01:30:04 so i will need a new seed phrase in the cli wallet? 01:38:37 This is a better topic for Monero 14:23:20 Monerujo Polyseed support was done a year ago already, according to bounty info here: https://bounties.monero.social/posts/116/2-200m-polyseed-support-for-monerujo-0-25m 14:24:01 But the latest version that I installed today does not seem to offer Polyseed? 14:24:12 correct 14:24:25 :( 14:25:15 This was before the new rule 14:25:37 ``` 14:25:38 2025/03/30 - Bounties for established projects 14:25:40 Require pre-approval. 14:25:42 The author/bounty hunter MUST reach out to the project before starting work on it so they have a chance to concept ACK. 14:25:44 Evidence of such MUST be provided (public ACK of the bounty from the project) 14:25:46 Example: FeatherWallet bounties would require pre-approval from tobtoht 14:25:48 ``` 14:26:04 Not sure what you mean. It does not work? 14:26:45 I mean that, previously you could make bounties for projects that dont feel like merging your work 14:27:00 New rules is that you have to confirm uptream that they are onboard with your idea 14:27:32 Ah, and that may be the case now with Monerujo you mean? The latest version is from Summer 2025 and could therefore include this - if it wanted ... 14:27:47 yea 14:28:47 Ok, anyway, if support is not yet "official" in Monerujo we have 1 wallet less that could do something differently because of different interpretations of the spec, so maybe that's net positive :) 14:29:14 j0j0 did it so its probably similar/same as anonero 14:29:49 anonero, feather, monfluo, cake, stack support polyseed 14:30:22 By the way, I just confirmed that also Polyseeds with offsets (or however you want to call that) are interoperable between Cake and Feather. At least as of today. Which is very good. 14:30:50 did you create in cake and then restore in feather? 14:31:16 iirc there was a report from user that it wouldnt work. Will have to see if i can search it up 14:31:55 So far only the other way round. To be complete, I can try to create in Cake and then restore in Feather. However, that would be very surprising if only one way round worked, no? 14:32:26 Agreed lol 14:32:40 Will later look at the source to see first hand what the apps really do. 14:33:21 At least in theory, you could treat Polyseeds differently according to the encoded restore height, and Cake may have improved something, starting at some height 14:33:44 So it's possible it once wasn't interoperable 15:14:36 Hmm, that's surprising. Feather refuses the Cake seed with a message that "encrypted seeds are not supported". 15:16:03 probably their catch-all message for seeds they can't parse 15:16:41 Don't think so, but a look into the source later will certainly tell me what's up. 15:47:29 So i wasnt crazy 16:10:08 Not this particular way, no :) 16:14:29 I looked for the initial report but couldnt find it, and started to think i dreamed it up 22:39:24 under what circumstances does this occur? `Failed to sign withdrawal tx: sign_multisig failed: Failed to sign multisig tx: This signature was made with stale data: export fresh multisig data, which other participants must then use (code: -35)` i thought it was just time, but i noticed my code which is rapidly exporting to each other got this error when trying to do a signature, do 22:39:24 es each import of the multisig data invalidate the previous data and sig/tx somehow? 22:45:16 https://github.com/monero-project/monero/blob/master/src/wallet/wallet2.cpp#L14551-L14552 22:45:16 ``` 22:45:18 // - Calling this function will reset any nonces recorded by the previous call to this function. Doing so will 22:45:20 // invalidate any in-progress signing attempts that rely on the previous output of this function. 22:45:22 ``` 22:45:24 i guess that answers it 23:57:58 hmm still can't figure out how much time it takes to expire 23:58:04 hmm still can't figure out how much time it takes to expire (didn't look too closely though) 23:59:50 I dont think its time based