shim/rollkit: go-da via gRPC

[pepyakin]

This changeset migrates the rollkit demo to go-da, the more modern version
of the DA interface for Rollkit.

One of the most important changes is that rollkit doesn't embed the adapters anymore.
Instead, it communicates with the adapter through gRPC protocol. Instead of yet another
adapter, this implements gRPC dock directly, which kind of challenges the current
architecture.

Notable changes:

1. demo/rollkit was regenerated from the tutorial once again. That turned out to be
   easier than manually porting changes. I ported init-local.sh though.
2. removed adapter/sugondat since it is not longer needed
3. since it looks like we are going away from the docker workflow, I did not port
   the Dockerfile to the new code. I left the docker-compose.yml though, just removed
   the gm service.
4. the JSON-RPC was pushed to the sovereign dock. Now serve subcommand will launch
   only the specified dock instead of all of them. Each dock has its own subcommand.
   ikura-shim serve rollkit is now used for running rollkit.
5. now dock subcommands get their own options. E.g. rollkit doc now can accept the default
   namespace in case requests from rollkit without namespace (they do atm).

There are some things that were left for follow ups:

1. shim/rollkit: downgrade proto/upgrade rollkit #258
2. shim: block submission is too slow #259

Closes #106

[pepyakin]

Current dependencies on/for this PR:

• shim/rollkit: go-da via gRPC #260 👈
• main

This stack of pull requests is managed by Graphite.

[pepyakin]

The CI is flaky.

[rphmeier]

Just noting: the biggest implication of this change, it seems, is that you can no longer run the shim for all docks at the same time. I am not sure why that would be useful & don't think this fundamentally impacts the product. I'm sure we could add it again later if needed, anyway.

[pepyakin]

Yes, that was my reasoning as well.

[rphmeier]

You mentioned in the PR description that rollkit doesn't submit blobs with a namespace. Also, when this is None we get a CLI warning.

Bu the SubmitBlob gRPC contains a namespace.

What I am understanding so far is that:

1. With any rollkit chain today, the namespace is omitted in the request and therefore must be configured in the shim.
2. Rollkit could be altered in the future to support sending namespaces without requiring any changes to the shim

correct?

[pepyakin]

Kind of.

I am not sure what is the reason of this interface and what is the ultimate game plan: maybe the namespace being phased out? Or maybe it got a hit during migration to go-da. Either way, right now it doesn't seem that Rollkit takes the namespace ID.

I just went to check to celestia-da (implementation of go-da that embeds the whole celestia-node) and it seems that they are also taking a mandatory namespace parameter.

https://github.com/rollkit/celestia-da/blob/b5b95ff2fd15eb45a6aa399540f6ee9f22f8202d/cmd/celestia-da/server.go#L25-L26

[gabriele-0201]

To avoid wrapping everything into an Ok(...) another approach could probably be:

        match supplied_ns {
            Some(pbda::Namespace {
                value: raw_namespace_bytes,
            }) => {
                let raw_namespace_bytes = raw_namespace_bytes.as_slice();
                if raw_namespace_bytes.len() != 16 {
                    return Err(Status::invalid_argument("namespace must be 16 bytes long"));
                }
                let mut namespace = [0u8; 16];
                namespace.copy_from_slice(raw_namespace_bytes);
                Ok(ikura_nmt::Namespace::from_raw_bytes(namespace))
            }
            None => self.namespace
                .and_then(|namespace| Ok(namespace.clone()))
                .ok_or(Status::invalid_argument("namespace must be provided"))
        }

[rphmeier]

Looks terser and like a good suggestion - @gabriele-0201 this is a good opportunity to practice on Graphite. Instead of pausing this PR and updating it, create a new PR based on this stack which applies that change as a refactor.

[pepyakin]

oh and yeah namespace.clone() is not necessary.