01:29:15
kiersten5821:matrix.org:
so i will need a new seed phrase in the cli wallet?
01:37:48
jeffro256:monero.social:
This is a better topic for Monero
14:22:31
rbrunner7:monero.social:
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:23:12
rbrunner7:monero.social:
But the latest version that I installed today does not seem to offer Polyseed?
14:23:23
ofrnxmr:xmr.mx:
correct
14:23:36
rbrunner7:monero.social:
:(
14:24:26
ofrnxmr:xmr.mx:
This was before the new rule
14:24:48
ofrnxmr:xmr.mx:
```
14:24:49
ofrnxmr:xmr.mx:
2025/03/30 - Bounties for established projects
14:24:51
ofrnxmr:xmr.mx:
Require pre-approval.
14:24:53
ofrnxmr:xmr.mx:
The author/bounty hunter MUST reach out to the project before starting work on it so they have a chance to concept ACK.
14:24:55
ofrnxmr:xmr.mx:
Evidence of such MUST be provided (public ACK of the bounty from the project)
14:24:57
ofrnxmr:xmr.mx:
Example: FeatherWallet bounties would require pre-approval from tobtoht
14:24:59
ofrnxmr:xmr.mx:
```
14:25:15
rbrunner7:monero.social:
Not sure what you mean. It does not work?
14:25:56
ofrnxmr:xmr.mx:
I mean that, previously you could make bounties for projects that dont feel like merging your work
14:26:11
ofrnxmr:xmr.mx:
New rules is that you have to confirm uptream that they are onboard with your idea
14:26:43
rbrunner7:monero.social:
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:26:58
ofrnxmr:xmr.mx:
yea
14:27:58
rbrunner7:monero.social:
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:28:25
ofrnxmr:xmr.mx:
j0j0 did it so its probably similar/same as anonero
14:29:00
ofrnxmr:xmr.mx:
anonero, feather, monfluo, cake, stack support polyseed
14:29:33
rbrunner7:monero.social:
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:01
ofrnxmr:xmr.mx:
did you create in cake and then restore in feather?
14:30:27
ofrnxmr:xmr.mx:
iirc there was a report from user that it wouldnt work. Will have to see if i can search it up
14:31:06
rbrunner7:monero.social:
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:31:37
ofrnxmr:xmr.mx:
Agreed lol
14:31:51
rbrunner7:monero.social:
Will later look at the source to see first hand what the apps really do.
14:32:32
rbrunner7:monero.social:
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:32:55
rbrunner7:monero.social:
So it's possible it once wasn't interoperable
15:13:47
rbrunner7:monero.social:
Hmm, that's surprising. Feather refuses the Cake seed with a message that "encrypted seeds are not supported".
15:15:14
Cindy:
probably their catch-all message for seeds they can't parse
15:15:52
rbrunner7:monero.social:
Don't think so, but a look into the source later will certainly tell me what's up.
15:46:40
ofrnxmr:xmr.mx:
So i wasnt crazy
16:09:19
rbrunner7:monero.social:
Not this particular way, no :)
16:13:40
ofrnxmr:monero.social:
I looked for the initial report but couldnt find it, and started to think i dreamed it up
22:38:35
kiersten5821:matrix.org:
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<clipped message>
22:38:35
kiersten5821:matrix.org:
es each import of the multisig data invalidate the previous data and sig/tx somehow?
22:44:27
kiersten5821:matrix.org:
https://github.com/monero-project/monero/blob/master/src/wallet/wallet2.cpp#L14551-L14552
22:44:27
kiersten5821:matrix.org:
```
22:44:29
kiersten5821:matrix.org:
// - Calling this function will reset any nonces recorded by the previous call to this function. Doing so will
22:44:31
kiersten5821:matrix.org:
// invalidate any in-progress signing attempts that rely on the previous output of this function.
22:44:33
kiersten5821:matrix.org:
```
22:44:35
kiersten5821:matrix.org:
i guess that answers it
23:57:09
kiersten5821:matrix.org:
hmm still can't figure out how much time it takes to expire
23:57:14
kiersten5821:matrix.org:
hmm still can't figure out how much time it takes to expire (didn't look too closely though)
23:59:01
ofrnxmr:xmr.mx:
I dont think its time based
23:59:22
ofrnxmr:xmr.mx:
cc [@woodser:monero.social](https://matrix.to/#/@woodser:monero.social)