Rootul P

I've tried a few times to create a Go module from `x/blob` but the gopls in VSCode messes up the import paths. Currently hitting: ``` $ make build-node --> Building...

I thought the issue might be because v1.x has an `x/blob` that isn't a Go module yet so I repeated the steps above on the v1.x branch and hit this...

The original error message ``` panic: concrete type *types.MsgPayForBlobs has already been registered under typeURL /, cannot register *types.MsgRegisterEVMAddress under same typeURL. This usually means that there are conflicting modules...

It looks like all the other Cosmos SDK message types have distinct type URLs but then when we get to registering blob or blostream types, the typeURL goes empty. Update:...

This issue only repros when I try try to create a v1 application. If I only create a v2 applications, types are registered fine. At the time when v1 is...

One way to resolve is on the v2.x branch, modify the package name for all Celestia state machine packages from v1 to v2. E.g. ```diff -package celestia.blob.v1; +package celestia.blob.v2; ```...

My CometBFT node isn't advancing to the next block height after 0. It looks like it never invokes InitChain either.

The CometBFT node suddenly calls "Stopping Node service" before progressing to block height 1 ```log I[2024-08-06|11:10:34.375] service start module=proxy msg="Starting multiAppConn service" impl=multiAppConn I[2024-08-06|11:10:34.375] service start module=abci-client connection=query msg="Starting localClient...

I think these 3 errors are red herrings because they also appear in the logs for a successful integration test that uses testnode. ``` E[2024-08-06|11:10:34.483] Error serving server err="accept tcp...

Even though the block height is 0, it looks like the v1 state machine is getting passed [these lines](https://github.com/celestiaorg/celestia-app/blob/d118a62f90f0ec42e7049ba01301921affcbec52/app/square_size.go#L17-L19) and trying to query a param which panics. Need to add...