Mustafa Al-Bassam

Tree sharding to process updates in parallel

5

At the moment, the tree can only safely handle one update at a time. It would be desirable to shard the tree into multiple subtrees and allow parallel updates to...

Add optimistic rollup support for Cosmos SDK

16

The purpose of this issue is to start a discussion about adding support for optimistic rollups to the Cosmos SDK, and what exactly this means and entails. There are two...

Investigate the implications of the client choosing whether to sample from row or column

1

In the [fraud proofs paper](https://arxiv.org/abs/1809.09044), the client picks the (x, y) co-ordinates, but the node decides whether to return a response from the row or column root. In the [current...

We should pull @roysc's rewrite of smt.go upstream here (https://github.com/vulcanize/smt), as it provides a substantial and well-written performance improvement by not recomputing the root on every update, that also produces...

Tree-based approach for partial storage nodes network sharding and peer discovery

9

[Partial storage nodes](https://github.com/celestiaorg/celestia-specs/blob/master/src/specs/node_types.md#node-type-definitions) are nodes that only store some of the blocks in the blockchain, and can be queried by any other nodes (including light clients and other partial nodes)...

Add claw back to vesting module

5

## Summary Add the ability for an admin key to claw back unvested tokens to a treasury account. ## Problem Definition It is standard practice in token vesting contracts, that...

"Delete" data in non-reserved namespaces after X days (where X is some network-wide parameter that is TBD)

1

See e.g. https://notes.ethereum.org/@vbuterin/proto_danksharding_faq#If-data-is-deleted-after-30-days-how-would-users-access-older-blobs This means that in the block validity rule, we would not verify data availability of non-reserved namespaces blocks older than X days, instead we rely on a...

Implement discoverability of archival nodes with historical block data vs nodes without historical block data?

1

It may be harder to sync from genesis if nodes can't differentiate between nodes that do or don't have the historical block data.

Implement syncing from genesis without downloading data blobs

3

We should implement the ability for celestia-core nodes to sync the chain from genesis by only downloading the sdk.Txes (so that they can recompute the state root) but not the...

Don't store min+max namespace IDs in badger inverted index keys

2

This should save around 50% of the storage used by the inverted index. We don't need to put min+max namespace IDs in the inverted index, as they don't contribute to...