Shared sequencer integration about fuel-core

[MitchTurner]

Will staking and staking parameters need to be included in this feature?

[MitchTurner]

We need to figure out what data we will send from the block builder to the SS. This includes signatures and other data formatting stuff.

[xgreenx]

@Dentosal You should have access to the repository right now.

Bellow instruction which we received.

Hey @XGreenX99 the documentation on the Sequencer's README should be helpful for this. https://github.com/fuel-infrastructure/fuel-sequencer

I point you specifically to the make run-sequencer-no-sidecar command, which will require you to have Golang 1.21 installed and Ignite CLI (linked in the README).

This command will start up the Sequencer with a set of accounts (refer to config-no-sidecar.yml file for a full breakdown of accounts), and it will also install the fuelsequencerd binary for interacting with the network.

Maybe instead of building it manually we could try to use docker from https://github.com/FuelLabs/fuel-rollup/tree/main/docker.

For posting blobs, you will need to set up a client to the Sequencer. This is equivalent to setting up a client to a typical Cosmos SDK chain.

The Sequencer-specific thing will be the message itself - MsgPostBlob. You can find the definition of it here https://github.com/fuel-infrastructure/fuel-sequencer/blob/e60fd0bf9d1f47b87a19cf81668f9ba5ab5f6c84/proto/fuelsequencer/sequencing/v1/tx.proto#L44-L62

(Also described in the Sequencer Spec - https://github.com/fuel-infrastructure/notes/blob/main/spec/Spec.md#user-transactions)
I wish to point out is a possible issue you might run into 🚨 We've used the bytes type for the topic ID and the blob data. By default, Cosmos SDK will expect base64-encoded data for bytes. If we require support for hex topic IDs and hex-encoded blob data, then this will need to be tweaked from our side

Our goal is to use PostBlob transaction to post Fuel blocks into the shared sequencer. The From field is an address of the PoA node. Based on the protobuf transaction definition, we can generate a Rust version of it. We could try to use cosmos Rust SDK to sign transactions, but if we can do that without it, it would be awesome.

When we post data to the sequencer the corresponding PoA Ethereum address(that we can generate from a private key) should contain Fuel tokens to pay for it. I would suggest reading the specifications about the flow of the transaction for more clarification.

It would be nice if we could integrate testing of blob posting into our CI.

[Dentosal]

Design notes from my discussion with @xgreenx

• The PoA key will be used tio sign the blobs
• I'll create a script to read posted blobs from the sequencer