Expose an our_xpub field in revaultd's getinfo so the GUI can keep it in its context (or even poll it on demand)
Have the GUI call listonchaintransactions <deposit outpoint> after a listvaults to check if the PSBT's partial_sigs contain a signature for derivation_index at input 0
Stuff it on revaultd side:
Have a new vault status or a new column in DB
@edouard: I think the first one would be easier for now, since you already call listonchaintransactions for each vault on the homepage so this would not bloat it either. Wdyt?
Related: https://github.com/revault/revaultd/issues/105
There are two ways to approach this:
our_xpub
field inrevaultd
'sgetinfo
so the GUI can keep it in its context (or even poll it on demand)listonchaintransactions <deposit outpoint>
after alistvaults
to check if the PSBT'spartial_sigs
contain a signature forderivation_index
at input 0@edouard: I think the first one would be easier for now, since you already call
listonchaintransactions
for each vault on the homepage so this would not bloat it either. Wdyt?