You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I read an article related to Multisig Account through documentation. I understood that Multisig supported by Polkadot is onchain multisig. I wonder if you are officially supporting or planning to support offchain mulsig.
The text was updated successfully, but these errors were encountered:
It's blocked on me doing w3f/schnorrkel#11 / w3f/schnorrkel#6 or conning someone else into doing it my way. I just succeeded in the latter but now that person is leaving.
It'll probably happen this year, but then it'll be blocked on parity signer figuring out how to deploy it, which shall likely take another year.
If anyone competent to implement crpyto wants this fast then we can work with them too.
This is not really a polkadot issue, imho. It's currently a schnorrkel issue and later a parity signer issue, so it can be closed here.
)
* Require a single proof in submitInitial* calls
* Skip handover when testing stale commitment
* s/_proofs/proofs/g
* Remove extra proof
* Remove explicit any
* Check that proof index is in bitfield
serban300
pushed a commit
to serban300/polkadot-sdk
that referenced
this issue
Mar 26, 2024
I read an article related to Multisig Account through documentation. I understood that Multisig supported by Polkadot is onchain multisig. I wonder if you are officially supporting or planning to support offchain mulsig.
The text was updated successfully, but these errors were encountered: