Feat/celestia da client

[heemankv]

TL;DR : This PR includes code for utilising Celestia as a DA client || Resolves Issue #43.

celestia-node - Steps :

1. Run celestia-node, preferred impl here.
2. Ensure to safely note down the account information provided to use later on.
3. Ensure to manually fund the account, see here.
4. Ensure that the account is detected by celestia-node, see here.

Shortcut method to run Celestia as DA :

• define $NETWORK, $RPC_URL, $NODE_TYPE, see here.
• skips Auth, setup from here.
• exposes 26658 for RPC communication, binds it to 8000 of host.

docker run --expose 26658 -p 8000:26658 -e NODE_TYPE=$NODE_TYPE -e P2P_NETWORK=$NETWORK -v $HOME/Work/Karnot/docker-celestia-node:/home/celestia ghcr.io/celestiaorg/celestia-node:v0.14.0 celestia light start --core.ip $RPC_URL --p2p.network $NETWORK --rpc.port 26658 --rpc.addr 0.0.0.0 --rpc.skip-auth

• [only for testnet/devnet] Then copy paste all files from .celestia-light-<network_type>/keys to .celestia-light/keys, check if account is getting detected, see here.

Insomnia Json for RPC calls

Celestia Da Client :

Implements 4 methods from Da_Client_Interface.

• publish_state_diff : converts state_diff to blobs and publishes them to celestia, waits for height_id, sends height_id back as external_id. Uses blob.Submit.

  • Currently Fire and Forget implementation, we assume that Celestia will get it's blob validated on L1 automatically.

• verify_inclusion : picks up external_id and converts it to height_id, fetches inclusion status. Uses blob.GetAll.

  • Currently uses blob.GetAll since it doesn't need Commitment id.

• max_blob_per_txn : returns predefined value for max blobs to use per transaction. Defaults to 1, No Docs found.

• max_bytes_per_blob : returns predefined value for max bytes in a blob. Uses 1974272.

Tests :

Current Status :

• Ignored, because of manual intervention.
• verify_inclusion fails with un-synced Blocks. stuck at 1507551.
• rest all works as expected.

[heemankv]

Should we not have a Result<String,Error> as return value of publish_state_diff function, to let the worker know that the blob Submit call has failed ?
@apoorvsadana