Mustekala Roadmap
Requirements
Ethereum storage requierements
- Facilitating account and token balance
- Identify the slice associated with the token address
- Get the slice
- figure out if the slice is complete
- we'll know if this is a final slice or not and download the remainder when we run the contract(s)
- Run the contract
- intercept the storage calls and download the slices that contain that storage (this is done already)
Kitsunet requirements
- Nodes need to figure out which slices they are serving
- We can use some sort of consistent hashing to map slices onto peers
- The node also keeps the slices that it needs, for example for the accounts it's interested in
- as a possible optiomization, we might also want to have a notion of topologicaly close nodes that collaborate with
- block source
- slice source
- ideas:
-
- slice producing geth forks joins kitsunet
- cons: more complexity, deploy frequently, ensure browser + node coverage
-
- slice producing geth fork exposes http/ws accessed by "activated" node
- pro: simple, lets us focus on gossip/topo
MVP
As a first step, we want to have a few slices that we subscribe to and get the accounts balances and token balances.
- multiple slice feeds
- block header feed
- passive nodes track header and 1 slice
- active nodes change their slice subscription
Mustekala Roadmap
Requirements
Ethereum storage requierements
Kitsunet requirements
MVP
As a first step, we want to have a few slices that we subscribe to and get the accounts balances and token balances.