Single approved signer registry

Open
#284 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
blockchain

Research direction

Start by locating the orchestrator and broadcaster contracts, then find every contract that validates off-chain signatures or supports approved signers. Trace the existing approval and signature paths first; the work is done when those contracts consistently fall back to the shared registry only when the recovered signer differs from the provided main-account address.

Written by the indexing model from the issue text.

Description

Orchestrators and broadcaster can use a single registry to approve/revoke signers that sign off-chain data on behalf of their main ETH account. Any contract that supports approved signers should be aware of this registry and during signature validation should:

  • Check if the recovered address from a signature matches the provided address
  • If not, check if the recovered address is an approved signer in the registry for the provided address
Dominant language
JavaScript
Stars
155
Forks
50
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from livepeer/protocol

All issues in livepeer/protocol

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.