Antoine Poinsot
Antoine Poinsot
> we assume at least 1 of the stakeholders' wallets is not compromised One of their HW* if it can be generated by the HW. If you are the last...
> That's what I was getting at with .... Yes but the premise is wrong, they don't need to verify it but to trust the HW (they don't re-compute the...
> Is this in the revault-compatibility HW features list somewhere? https://github.com/revault/practical-revault/pull/83#issuecomment-829274349 : > I wonder if it's possible to do on the HW and asked stepansnigirev by mail some time...
My last approach is clearly not going to work for HWs (they can't bear storing an infinite amount of descriptors..). I'm now thinking of stuffing a [short-channel-id](https://github.com/lightningnetwork/lightning-rfc/blob/master/07-routing-gossip.md#definition-of-short_channel_id) in `nLockTime` and...
We should be able to assume that it is a non-issue thanks to Miniscript.
It includes checking the Miniscript s in the PSBT inputs too ...
Part of this was implemented in #70 and #67
This would include checking for duplicated inputs (found by the fuzzer in the Cosigning Server) and all sort of insane transaction in general.
We need to refuse insane amounts as well, working on it.
https://github.com/llogiq/mutagen