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.

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

Update anonymous proxy #1458

Closed
laboon opened this issue Dec 16, 2020 · 3 comments
Closed

Update anonymous proxy #1458

laboon opened this issue Dec 16, 2020 · 3 comments

Comments

@laboon
Copy link
Contributor

laboon commented Dec 16, 2020

https://wiki.polkadot.network/docs/en/learn-proxies#anonymous-proxies

paritytech/substrate#7735 (comment)

And maybe add alternative name "keyless proxy"?

@joepetrowski
Copy link
Collaborator

joepetrowski commented Dec 24, 2020

Please do no update in this way, for a few reasons.

One, we don't have a new name, or even know that there will be a new name. Changing the name in code means breaking the transaction version, so Ledger and other wallets need to release major versions to stay compatible. It could happen, but it's not a trivial change.

Two, we need to be careful about explaining what things are vs. "what you can do" with things. Examples should strictly contribute to fundamental understanding of a concept/tool and not prescribe use. Abstractions like anon proxies allow for creativity and new account architectures, let's not get it into readers' heads that they are "for" something in particular.

Three, almost everything in the referenced comment is incorrect. (cc @nukemandan )

image

No, because that graphic would be incorrect.

A "keyless account" is akin to a "shell company" that looks and acts like an individual / person on chain (keyed accounts), but in reality is controlled by a dynamic set of "real" keyed accounts.

Also incorrect. What is a "real" account?

MS do have a single master key (that you technically could find and use to make a MS -> single key control) this "user primary account" does not have a key.

No they do not.

@nuke-web3
Copy link
Contributor

@joepetrowski For clarification and for my reference, could you help set these straight?

  • A "real" account == is capable of signing, thus able to submit extrinsics (that almost all require in so capacity). Anon Proxies cannot sign, correct?
    • Are there ant other accounts and proxies in substrate or other blockchain project that do not have signing ability of any kind?
  • Multisigs construct a signature that, in theory, can be generated from a single key if you were able to find it. Is this a correct statement? If not, why exactly?

@joepetrowski
Copy link
Collaborator

  • Accounts have nothing to do with signing. They are anything that meets Substrate's trait bound of AccountId and have some means of authentication. Maybe you should read this blog post.
  • Not at all. Look at the multisig code in Substrate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants