fuel-block-committer icon indicating copy to clipboard operation
fuel-block-committer copied to clipboard

A standalone service that commits Fuel block data to L1 / DA

Results 37 fuel-block-committer issues
Sort by recently updated
recently updated
newest added

The top level errors don't have context. Difficult to tell what failed. The runners are fine, they are given context by the runnable.

We will soon experiment using AWS KMS (and HSM) to manage our signing keys. That means using AWS KMS' API for signing. Since we already use `ethers-rs`, [we can use...

enhancement
P0

Currently we're loading `trusted_setup.txt` into our binary's RO only to write it out to a file again during runtime so that it may again be read. We should rewrite this...

We should add an e2e test that creates blocks with transactions that can be used for blob content. Currently even if we enable blob support on the committer it has...

Some deploy scripts are going to be removed as part of a clean up on the bridge repository, they might brick current tests here. As soon as https://github.com/FuelLabs/fuel-bridge/pull/204 is merged,...

- **chore(fuel-core): bump to v0.38** - **feat(compression): include da compressed blocks into the block importer** Incrementally fetches blocks instead of fetching by range, if a da compressed block exists, it...

Bumps fuel-core-* deps to latest

It seems that if the committer experiences networking issues towards eth alloy will just log them and reattempt connection in the background. not sure what happens with our network requests...

So that we may get ahead of any unoptimized queries.