Separate roles for contract owner and workload ID permissioner
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
- solidity
- Domain
- blockchain
Research direction
Start by reading the BlockBuilderPolicy and FlashtestationRegistry contract definitions, focusing on the owner-controlled workload-ID permissioning and upgrade paths. Done means permissioning can use a separate permissioner role while the owner retains control of upgrades and adding or removing that role.
Written by the indexing model from the issue text.
Description
Currently there is only one admin role on the BlockBuilderPolicy and FlashtestationRegistry contract, and that is the owner which is a multisignature wallet. It is able to add and remove permissioned workload IDs, as well as upgrade the contract. This means permissioning a new workload ID requires the operationally burdensome process of getting a signature from the multisig wallet owner.
It would be much simpler to have a separate "permissioner" role which would be an EOA hot wallet, or 1-of-N multisig (so that either flashbots or unichain can sign the transaction). That would allow the permissioning process to be automated, and thus much easier/simpler. The owner role would then be in charge of upgrading and adding/removing the permissioner role.
- Dominant language
- Solidity
- Stars
- 4
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from flashbots/flashtestations
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
flashbots/flashtestations#58 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
flashbots/flashtestations#57 ·
-
v2
Difficulty 4/5 3-5 days Newbie friendliness 38/100
flashbots/flashtestations#52 ·
-
v2
Difficulty 5/5 Over a week Newbie friendliness 25/100
flashbots/flashtestations#48 ·
-
v2
Difficulty 5/5 Over a week Newbie friendliness 30/100
flashbots/flashtestations#47 ·
All issues in flashbots/flashtestations
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
lidofinance/core#1984 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
anza-xyz/kit#2098 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Merit-Systems/x402scan#1262 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Uniswap/hooklist#10503 · 1 comment ·
Maintainers usually reply within 1 day
-
help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
lumio-network/lumio-contracts#99 ·
Maintainers usually reply within 1 day