Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

offchain multisig account support #867

Open
MinwooJ opened this issue Feb 15, 2022 · 1 comment
Open

offchain multisig account support #867

MinwooJ opened this issue Feb 15, 2022 · 1 comment

Comments

@MinwooJ
Copy link

MinwooJ commented Feb 15, 2022

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.
@burdges
Copy link

burdges commented Feb 15, 2022 •
edited
Loading

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.

@Sophia-Gold Sophia-Gold transferred this issue from paritytech/polkadot Aug 24, 2023
claravanstaden pushed a commit to Snowfork/polkadot-sdk that referenced this issue Dec 8, 2023
@doubledup
SNO-521: Check single validator signature in testSubmit* (paritytech#867
267c159 
)

* 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@burdges @MinwooJ