fakebeacon: a fake beacon api server for op-stack. #2678
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
add a description of your changes here...
Rationale
tell us why we need these changes...
We want to deploy a new chain like OP Mainnet/Testnet with OP-Stack for BSC Mainnet/Testnet, but OP-Stack uses some APIs of the beacon chain to fetch blobs' info. The problem is that our BSC doesn't have a chain like the beacon chain, and blobs on the BSC are associated with the transaction itself.
add an example CLI or API response...
[FakeBeacon]
Enable = true
Addr = "0.0.0.0"
Port = 8686
OR
geth ....
--fake-beacon
--fake-beacon.addr="0.0.0.0"
--fake-beacon.port=8686
Notable changes: