00:01:37
woodser:monero.social:
it's not time based, but it can become stale with reorgs
00:02:17
woodser:monero.social:
at least to my knowledge
00:02:32
kiersten5821:matrix.org:
are you sure? the docs say it's time based https://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.
00:02:33
kiersten5821:matrix.org:
```
00:02:35
kiersten5821: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:
00:02:37
kiersten5821:matrix.org:
Error: Multisig error: This signature was made with stale data
00:02:39
kiersten5821:matrix.org:
```
00:03:43
woodser:monero.social:
ah ok, don't know how much time before it becomes stale
00:04:30
woodser:monero.social:
we build into our protocol exporting and importing again if it becomes stale for any reason
00:07:24
ofrnxmr:xmr.mx:
the docs arent always gospel
00:07:48
kiersten5821:matrix.org:
yeah, but i did test locally and it expired despite nothing happening
00:07:49
ofrnxmr:xmr.mx:
Stale data sounds to be like old data, not expired data
00:08:03
ofrnxmr:xmr.mx:
To me*
00:15:10
woodser:monero.social:
it'll also become stale if you create a new tx
00:17:28
kiersten5821: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
00:17:35
kiersten5821:matrix.org:
i'm pretty sure the docs are correct based on that
02:22:08
kiersten5821: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
02:22:09
kiersten5821:matrix.org:
213 out - 2026-01-24 01:55:55Z 0.017000000000 96fcfd36cb6bd1e10e9d6eae89b38547e2a45bdb86f0a1da27c59dd340201bf8 0000000000000000 0.002599200000 - 0 -
02:22:11
kiersten5821:matrix.org:
the one that is shows this
02:22:13
kiersten5821:matrix.org:
213 out - 2026-01-24 01:55:55Z 0.017000000000 96fcfd36cb6bd1e10e9d6eae89b38547e2a45bdb86f0a1da27c59dd340201bf8 0000000000000000 0.002599200000 49(restofaddresshere):0.017000000000 0 -
02:22:15
kiersten5821: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
02:22:20
kiersten5821:matrix.org:
is this the problem the new upgrade's view keys will solve?
02:22:22
kiersten5821:matrix.org:
🤔
02:26:40
ofrnxmr:xmr.mx:
No
02:26:57
ofrnxmr:xmr.mx:
Recipient address isnt saved on chain
02:28:52
ofrnxmr: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
02:56:32
kiersten5821:matrix.org:
and it's impossible to prove it to the other instance?
02:56:39
kiersten5821:matrix.org:
so that won't change with the new upgrade?
02:57:36
kiersten5821:matrix.org:
wait, you could just send a spend proof to prove it to the other instances, no?
02:58:38
ofrnxmr:xmr.mx:
Right
10:30:22
woodser:monero.social:
kiersten: you can use 'describe_transfer' for other wallets to verify unsigned tx's address and amounts. for example: https://github.com/haveno-dex/haveno/blob/f9ea863162ba7cc6827d3fc85449b5cb1dd7ccc4/core/src/main/java/haveno/core/trade/Trade.java#L1596
10:39:48
plowsof:matrix.org:
does kiersten have to read this reg proofs? https://github.com/monero-project/monero/issues/8819#issue-1656289739
15:50:24
kiersten5821: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?
15:53:20
kiersten5821:matrix.org:
in the code you sent, that's the one that broadcasts it
15:57:16
Cindy:
is this for multisig or regular tx
15:57:56
kiersten5821:matrix.org:
multisig
15:58:38
Cindy:
if the guy changes it
15:58:44
Cindy:
doesn't it invalidate the signature you signed on it?
16:02:31
woodser:monero.social:
kiersten: when the tx is signed, the tx id becomes available, so you have a handle to the specific signed tx
16:03:33
kiersten5821:matrix.org:
only the last signer knows this though, describe_transfer on an intermediate one doesn't show it
16:03:50
woodser:monero.social:
yeah, couldn't say on intermediate signers
16:13:05
Cindy:
oh, multsig uses a secret sharing
21:40:53
jpk68:
Apologies if this is a dumb question. I was wondering if anything else would be needed to fix #10274 besides this:
21:41:01
jpk68:
https://paste.debian.net/plainh/65b9e09f
21:41:11
jpk68:
Just wanted to check before making a PR or something
21:43:16
jpk68:
diff is for /src/rpc/zmq_server.cpp
21:54:02
vtnerd:monero.social:
That should be it, but have you tested it?
21:58:09
jpk68:
Yes, and it seemed to be working fine.
22:02:31
jpk68_:
The daemon started up without any errors, and P2Pool also recognized it. I'll try again with the chain synced before submitting.