<o​frnxmr:xmr.mx> cc [@woodser:monero.social](https://matrix.to/#/@woodser:monero.social)

<w​oodser:monero.social> it's not time based, but it can become stale with reorgs

<w​oodser:monero.social> at least to my knowledge

<k​iersten5821:matrix.org> are you sure? the docs say it's time based docs.getmonero.org/multisignature/#spending, and additionally, i tested on a local chain with no new blocks being produced, and it still gave this error after a few minutes of sitting there.

<k​iersten5821:matrix.org> ```

<k​iersten5821:matrix.org> Note: Once you synchronize the partial key images, there is a certain time window by which you can create and send your transaction. I'm unsure exactly how long the time window is. If you leave it too long you will see the output:

<k​iersten5821:matrix.org> Error: Multisig error: This signature was made with stale data

<k​iersten5821:matrix.org> ```

<w​oodser:monero.social> ah ok, don't know how much time before it becomes stale

<w​oodser:monero.social> we build into our protocol exporting and importing again if it becomes stale for any reason

<o​frnxmr:xmr.mx> the docs arent always gospel

<k​iersten5821:matrix.org> yeah, but i did test locally and it expired despite nothing happening

<o​frnxmr:xmr.mx> Stale data sounds to be like old data, not expired data

<o​frnxmr:xmr.mx> To me*

<w​oodser:monero.social> it'll also become stale if you create a new tx

<k​iersten5821:matrix.org> the only thing that changed when it expired locally was the time, i never created any new tx, never exported or ran any other command, never made new blocks

<k​iersten5821:matrix.org> i'm pretty sure the docs are correct based on that

<k​iersten5821:matrix.org> it looks like only the sender of a multisig tx can know the destination? one of the wallets that wasn't the last signer just shows this

<k​iersten5821:matrix.org> 213 out - 2026-01-24 01:55:55Z 0.017000000000 96fcfd36cb6bd1e10e9d6eae89b38547e2a45bdb86f0a1da27c59dd340201bf8 0000000000000000 0.002599200000 - 0 -

<k​iersten5821:matrix.org> the one that is shows this

<k​iersten5821:matrix.org> 213 out - 2026-01-24 01:55:55Z 0.017000000000 96fcfd36cb6bd1e10e9d6eae89b38547e2a45bdb86f0a1da27c59dd340201bf8 0000000000000000 0.002599200000 49(restofaddresshere):0.017000000000 0 -

<k​iersten5821:matrix.org> is there a way to get it to know? i did use export_multisig_info but the other wallets still didn't show the address

<k​iersten5821:matrix.org> is this the problem the new upgrade's view keys will solve?

<k​iersten5821:matrix.org> 🤔

<o​frnxmr:xmr.mx> No

<o​frnxmr:xmr.mx> Recipient address isnt saved on chain

<o​frnxmr:xmr.mx> Lets say you have a non-multisig wallet running on 2 different devices. Only the device that sent the tx knows the address that it was sent to

<k​iersten5821:matrix.org> and it's impossible to prove it to the other instance?

<k​iersten5821:matrix.org> so that won't change with the new upgrade?

<k​iersten5821:matrix.org> wait, you could just send a spend proof to prove it to the other instances, no?

<o​frnxmr:xmr.mx> Right

<w​oodser:monero.social> kiersten: you can use 'describe_transfer' for other wallets to verify unsigned tx's address and amounts. for example: github.com/haveno-dex/haveno/blob/f…/haveno/core/trade/Trade.java#L1596

<p​lowsof:matrix.org> does kiersten have to read this reg proofs? monero-project/monero #8819#issue-1656289739

<k​iersten5821:matrix.org> but how do you relate the unsigned version to the version that you receive? if i sign a tx, send it to the next guy, and he is the one who signs + broadcasts, then how do i know the tx in my mempool that is outbound from me is the one i checked when it was unsigned?

<k​iersten5821:matrix.org> in the code you sent, that's the one that broadcasts it

is this for multisig or regular tx

<k​iersten5821:matrix.org> multisig

if the guy changes it

doesn't it invalidate the signature you signed on it?

<w​oodser:monero.social> kiersten: when the tx is signed, the tx id becomes available, so you have a handle to the specific signed tx

<k​iersten5821:matrix.org> only the last signer knows this though, describe_transfer on an intermediate one doesn't show it

<w​oodser:monero.social> yeah, couldn't say on intermediate signers

oh, multsig uses a secret sharing

Apologies if this is a dumb question. I was wondering if anything else would be needed to fix #10274 besides this:

Just wanted to check before making a PR or something

diff is for /src/rpc/zmq_server.cpp

<v​tnerd:monero.social> That should be it, but have you tested it?

Yes, and it seemed to be working fine.

The daemon started up without any errors, and P2Pool also recognized it. I'll try again with the chain synced before submitting.