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

I've removed the commit_interval from our configuration. Instead, the committee will now use the interval set in the state contract directly. - Added `BLOCKS_PER_COMMIT_INTERVAL() external view returns (uint256)` function to...

Since the state contract already has an interval configured, the committee should just use whatever is set in the contract instead of using its own config setting for the interval...

P1

- [ ] https://github.com/FuelLabs/fuel-block-committer/issues/50 - [ ] https://github.com/FuelLabs/fuel-block-committer/issues/56 - [ ] https://github.com/FuelLabs/fuel-block-committer/issues/57 - [ ] https://github.com/FuelLabs/fuel-block-committer/issues/58 - [ ] https://github.com/FuelLabs/fuel-block-committer/issues/59 - [ ] https://github.com/FuelLabs/fuel-block-committer/issues/81 - [ ] https://github.com/FuelLabs/fuel-block-committer/issues/80 - [...

P0
epic

A new component that will continually commit fuel transactions to L1. To take into account: * compression (to reduce the size) * fragmentation (to split transactions across multiple blobs) *...

enhancement
P0

The database is about to store considerably more data. Consider a solution that will prune old data (transactions, batches, submittals, etc) when we are sure that they are not needed....

enhancement

The buffering between the block watcher and committer turned out to be unneeded in hindsight. Merge the two components into one that will: * check for new blocks * should...

enhancement

The commit listener should now, besides receiving contract events, also subscribe/poll for the status of all submitted transactions in which we try to store transactions into eth blobs.

enhancement

Right now the block committer only commits the block hash, but we should add for this commits also the block data, but considering the size of the block data to...

P0

While releasing `0.3.0` got the following failure for the `publish crates` step > Run curl -sSLf "$DASEL_VERSION" -L -o dasel && chmod +x dasel > curl -sSLf "$DASEL_VERSION" -L -o...

bug