Tomasz Zdybał

Results 82 issues of Tomasz Zdybał

Under the hood Rollkit use libp2p, so multiaddr is native format for all addresses. Initially, to mimic normal Cosmos-SDK+Tendermint experience, some CLI parameters was reused (`--p2p.laddr` and `--p2p.seeds`), along with...

T:code-hygiene
T:dev-usability-and-ux

Currently block are retrieved from DA layer sequentially by a single goroutine. This should be parallelized to improve sync performance during catch-up phase.

T:enhancement
C:data-availability
C:block-sync
P:nice-to-have
C:feature-request

`mempoolIDs` struct was pulled from Tendermint's mempool into `node` package. It's a bit confusing right now. Tendermint mempool (which is reused in Optimint right now) use `IDs` internally, but this...

T:code-hygiene

### Implementation ideas Currently it's not clear if node is syncing only using DA or DA and P2P network and there is no explicit way of configuring this behavior. There...

C:p2p
C:data-availability
T:dev-usability-and-ux

- [ ] #571 - [ ] Execute query on top of minimal cosmos-sdk app - [ ] Integration tests trust-minimized queries

C:state-fraud-proofs
epic
blocked

Currently there are 2 loggers used in optimint: 1. [passed from cosmos-sdk](https://github.com/lazyledger/cosmos-sdk/blob/master-optimint/server/start.go#L265) 2. used by libp2p Ideally, only one logger should be used for better control and unification of logging....

T:enhancement
T:code-hygiene
P:nice-to-have

Experiments with Ignite CLI shows multiple issues with Optimint-Tendermint compatibility. This is a tracks progress of discovering and fixing issues. - [x] #436 - [x] #241 - especially `NodeInfo` needs...

T:code-hygiene
T:dev-usability-and-ux
C:rpc
epic

- [ ] Define new ABCI method (tendermint) - [ ] Implement query in cosmos-sdk - [ ] Implement query in rollkit - [ ] Execute trust-minimized query in cosmos-sdk...

C:light-client
blocked

This looks kinda insufficient: https://github.com/celestiaorg/optimint/blob/bfa0fa48319cefbc4c63c25e4655e862e5d3daa5/rpc/json/ws.go#L70-L73 Different message types should be handled properly. Possible message types are defined in [RFC 6455, section 11.8](https://www.rfc-editor.org/rfc/rfc6455.html#section-11.8).

T:enhancement
T:code-hygiene
C:rpc

T:code-hygiene
T:dev-usability-and-ux
C:rpc