Abstract the TEE policy verification logic into a library useable by external contracts

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
solidity
Domain
authorization, security

Research direction

Start by locating the BlockBuilderPolicy caching logic and compare it with the copied sections in the FlashblockNumber contract referenced in the issue. Define the reusable library boundary and verify that external policy contracts can outsource builder-role verification without duplicating the caching logic.

Written by the indexing model from the issue text.

Description

v2

Problem

Recently in the FlashblockNumber contract we had to copy-paste sections of the BlockBuilderPolicy's caching logic into the FlashblockNumber contract in order for it to be able to outsource verifying the builder role to the BlockBuilderPolicy. This was error-prone and caused duplicative code

Solution

Refactor this caching logic into a Solidity library that can be easily re-used by external contracts. This will make it so that a policy contract can outsource its auth logic to another policy with as little code duplication as possible.

Dominant language
Solidity
Stars
4
Forks
4
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 flashbots/flashtestations

All issues in flashbots/flashtestations

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.