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

QN: Validator profile #4823

Closed
thesan opened this issue Aug 2, 2023 · 0 comments · Fixed by #4849
Closed

QN: Validator profile #4823

thesan opened this issue Aug 2, 2023 · 0 comments · Fixed by #4849

Comments

@thesan
Copy link
Member

thesan commented Aug 2, 2023

As described in Joystream/pioneer#4330: validators should be given the ability to bind a membership profile to their validator accounts. This will be done by calling the members.updateProfile(memberId, handle, metadata) extrinsic with the validator account in the metadata.

The membership entity schema and mappings should be changed so that the validators profile can easily be accessed with one query e.g:

memberMetadata(where: {
  validatorAccount: {
    isVerified_eq: true
    address_in: [
      "5GNJqTPyNqANBkUVMN1LPPrxXnFouWXoe2wNSmmEoLctxiZY",
      "5HpG9w8EBLe5XCrbczpwq5TSXvedjrBGCwqxK1iQ7qUsSWFc"
    ]
  }
}) {
  member { handle }
  validatorAccount { address  }
}

isVerified is always reset to false whenever a validator account is set (it will be set to true by a different extrinsic).

Also in order for members.updateProfile(memberId, handle, metadata) to pass a validator account: a field should be added to MembershipMetadata in metadata-protobuf/proto/Membership.proto.

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