10:04:50 I guess it's not possible to know the tx id of multisig txs until they're completely signed? 10:11:29 or more generally, it's not possible to know if partially signed multisig txs are actually broadcast to spend funds from the wallet, unless the last signer/publisher notifies the others when the tx is signed? 10:27:20 The former, obviously not, or it'd allow having a invalid tx with the same txid as a valid one. 10:28:46 The latter, I'm not sure I understand. If you mean "I signed a tx, but it is not fully signed yet, can I know when/if it's on chain later", then you can. Just check the inputs. 10:30:02 Unless you do not want to match a sinilar tx signed by another set that does not include you. Then I think you cannot tell the difference. 10:30:22 If you meant something else, ask more precisely. 10:58:53 yes I want to know if a partially signed multisig tx is later broadcast, or its same inputs spent, without being notified by the last signer. how can one check the inputs, since I thought the inputs cannot be checked as spent without re-exchanging multisig info? 11:18:20 They're in cleartext on the chain. 11:18:53 Check those plus the key images. Just the key images ought to be enough, unless you signed several txes spending the same key image. 21:14:35 selsta: I'd be more comfortable if we understood that permission error for 8602. automated invocations of sudo/root make me paranoid. 21:14:58 but that would run in a isolated VM anyway? 21:15:09 but yes I understand would be good to figure out 23:35:50 rbrunner: I built the v0.18.1.2 binaries from github and I got the same error as you. Here is what I did. I downloaded all the dependencies using the apt method. After building, I also downloaded the entire blockchain. When I tried to deterministically bring up a wallet, it threw a "can't find the daemon error". It then started syncing with the daemon "in the background". But, I specified to start at 2,200,000 block height and 23:35:50 instead it went back to 1,800,000 something. It took a couple of hours to work through the block chain. Looking at "top" command in another screen, the wallet was dropping out after a few seconds and then restarting. The wallet was a failure after completing its synching. 23:39:05 Downloaded the program from GetMonero and all worked fine, even with the blockchain I had previously loaded. I also replaced the new cli wallet portion in with the bad install, but it did not help. 23:40:38 * rbrunner: I built the v0.18.1.2 binaries from github and I got the same error as you. Here is what I did. I downloaded all the dependencies using the apt method. After building, I also downloaded the entire blockchain. When I tried to deterministically bring up a wallet, it threw a "can't find the daemon error". It then started syncing with the daemon "in the background". I had specified to start at 2,200,000 block height 23:40:38 and instead it went back to 1,800,000 something. It took a couple of hours to work through the block chain. Looking at "top" command in another screen, the wallet was dropping out after a few seconds and then restarting. The wallet was a failure after completing its synching. 23:41:59 I suspect this bug has been around for a while as few people bother to build directly from github. 23:43:35 s/loaded/downloaded/ 23:43:45 since the gitian builds are fine, doesn't sound like an actual bug in monero source. could be something broken in the dependencies 23:44:49 hyc: I agree with you completely. 23:47:17 or ... a dependency's API has changed incompatibly but still compiles with the way we use it. that ould be gross.