General Improvements

[wilwade]

Some of these are just suggestions, and no prioritization currently.

• Suggestion: Hide signing address until after connected. Looks like you need to select something, but you cannot. It isn't really the connection with the node
• Allow Wallet Addresses that are for any network to show up on all networks
• Naming. It is confusing to call it is "signing key" when sometimes there are three and all are signing stuff.
  • Suggestion: Move the Top key and the submit extrinsic into a new block
  • Name the "signing key" the provider transaction key
  • Rename all the "Delegator Key" to "MSA Control Key."
• When there is a second key for "add_public_key_to_msa" add a second field for the "MSA Control Key." (For that extrinsic there should be three dropdowns: MSA Control Key, New MSA Control Key, and the Provider Transaction Key)

[shannonwells]

When there is a second key for "add_public_key_to_msa" add a second field for the "MSA Control Key." (For that extrinsic there should be three dropdowns: MSA Control Key, New MSA Control Key, and the Provider Transaction Key)

Yes, I realize you should be able to select them all; I was saving it for version 2. I should have made an issue for it.

[demisx]

Can someone please give a brief description of what the Provider Transaction Key is and how is it different from other keys? I would like to capture it for the mobile team. I have the definition of the control key, but this is the first time I come across of the "transaction key" term. Thank you.

[shannonwells]

@wilwade by 'Provider Transaction Key' do you mean the key that a Provider uses to sign transactions, especially for calls that require a payload? Not all of the transactions require one to be a provider. I think it should just be Transaction Signing Key, or maybe "Sign and Submit Transaction as..." might even be clearer

[wilwade]

Good point. Quick reference list:

• Tx: msa.create()
  • Tx Signer: MSA Creator
  • Additional Signatures: None
• Tx: claim_handle
  • Tx Signer: Capacity/Token Provider (No Delegation)
  • Additional Signatures: 1 (MSA Control Key)
• Tx: create_sponsored_account_with_delegation
  • Tx Signer: Capacity/Token Provider (No Prior Delegation)
  • Additional Signatures: 1 (MSA Control Key)
• Tx: grant_delegation
  • Tx Signer: Capacity/Token Provider (No Prior Delegation)
  • Additional Signatures: 1 (MSA Control Key)
• Tx: add_public_key_to_msa
  • Tx Signer: Capacity/Token Provider (No Delegation)
  • Additional Signatures: 2 (Original MSA Control Key AND New MSA Control Key)
• Tx: apply_item_actions_with_signature, upsert_page_with_signature, delete_page_with_signature
  • Tx Signer: Capacity/Token Provider (No Delegation)
  • Additional Signatures: 1 (MSA Control Key)

So from this, while delegations may be created, no prior delegation is required (this is due to the existence of the signature as it is an explicit one time delegation)

Always the Tx Signer/sender is the key that provides tokens or Capacity to pay for the transaction. The others are just MSA Control Keys of one form or another.

Usually this Tx Signer/sender (payee?) account is the provider account, but it is not a requirement unless paying in Capacity.

I like the "Sign and Submit Transaction as ..." phrasing, but it would be nice to have a name for the "provider" that isn't acting through a delegation.

[shannonwells]

Allow Wallet Addresses that are for any network to show up on all networks

This is working for me. I have 3 addresses that are allowed on any network that appear when I connect to Rococo, at least. Or do you mean locally too?