pull down to refresh
First there needs to be a coordination servers all parties use as a mailbox, a protocol for that... group invite flows...
Doesn't have to be a server per se. PSBT can be exchanged p2p and combined; isn't serial, so there doesn't have to be coordination. identity sig + prefilled owner tx sigs enough safety?
Then you want different clients built with different stacks for different device hardware... basically a native android, native ios, native x64 for various OS's, native ARM for the same OS's... each leveraging hardware at the lowest possible level
Can be a common rust lib where you implement the interface to store, encrypt, sign, validate in the platform binding. I've seen this becoming the defacto standard the past 2 years for most things that touch android/ios, and it is also often how flutter cross-platform apps do it.
Then you still need out-of-band coordination to prove a signing request is actually coming from the person its allegedly coming from
Should in all cases separate identity keys from money keys. Can derive from a single BDK (but ffs get entropy right, lol), but you'll want to use something that is resistant to "capture now" mechanisms... i.e. x-wing.
Need hooks into each of the signing apps to tie in any external polices people want
Policy is the hardest, but in a co-signer scenario, these only need to be implemented against the requester key though?
Probably need 4-5 people that know this shit very well to make something usable
Perhaps. Maybe some part time contributions to a specific platform.
The coordinator would mostly be a UX win so that people might actually use it, manually pasting QRs and strings out of band is potentially a privacy shit-show and cumbersome
I'd intentionally not want to use the same lib across platforms specifically for entropy, just to dodge any mines it may introduce upstream like MicroPython did :RIP: ... just as Bitcoin Core taps RDRAND / RDSEED and a bunch of environment data directly
ShockWallet uses a keyring so your identity key just holds encrypted copies of each of the source keys, mainly for privacy from the Pub where desired... I'd think similar for something like this, each group you're part of has its own signing key and that's encrypted and unlocked by say a passkey etc
Policy I think just needs a primitive endpoint for a POC since who knows what policies people might implement, if you and I are in a group maybe one of us needs to make a withdrawal every week at the same time to the same address and a bot approves specifically those signing request (here I go talking about policy engines again)
People who can get low level on each platform for starters, but also cross-functionally make sure the protocol and flows are sane.
That's good there's at least a starting point, wonder if @Wizardsardine is interested in incorporating anything further to this end
Actually I do believe that was one of Bitmex's considerations, executives in different countries
Just ruminating on the scope the pieces add up, would need to be a working group thing
First there needs to be a coordination servers all parties use as a mailbox, a protocol for that... group invite flows...
Then you want different clients built with different stacks for different device hardware... basically a native android, native ios, native x64 for various OS's, native ARM for the same OS's... each leveraging hardware at the lowest possible level
Then you still need out-of-band coordination to prove a signing request is actually coming from the person its allegedly coming from, or to get hold of your co-signees
Need hooks into each of the signing apps to tie in any external polices people want
Probably need 4-5 people that know this shit very well to make something usable and it'll take months just to get it to a point where you start beating on it a bit