foundry-rs / foundry-rs/foundry

meta(precompiles): tracking issue for non-Ethereum precompiles

Open
#7,262 5 comments 0 reactions 0 assignees View on GitHub
T-meta T-post-V1
Dominant language
Rust
Stars
10.6k
Forks
2.6k
Avg merge
16h 38m
Merged PRs (30d)
511

Description

### Component

Forge, Cast, Anvil

### Describe the feature you would like

with #7125 we can now configure chain specific precompiles more easily.

though only if they're self-contained and don't require additional input from the chain itself.
It would be possible however to fetch that from RPC, if available.

This is a tracking issue to gather precompiles we can implement as functions

## BSC

## Arbitrum

https://docs.arbitrum.io/for-devs/dev-tools-and-resources/precompiles#arbsys

## OP

## Blast

### Additional context

Please leave docs to precompiles as comments

Contributor guide

Open the contributing guide

Research direction

Start by reviewing #7125 and the Arbitrum precompiles documentation linked in the issue. Then determine the intended scope for BSC, Arbitrum, OP, and Blast; the issue names no files, tests, or implementation entry points, and considers documentation in comments part of the work.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
blockchain, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.