👨‍💻🌉 1H25 planning

Build the capability > test it out > figure out L2 use cases (get funding + find PMF)
Deployed and maintained by FIL-B
Pluggable deal engines by lighthouse.storage, CID gravity etc.
First example in December is with lighthouse, with db on filecoin (V0)

Components

Filecoin

Contracts

X-chain

Buffer - IPFS

Client

Bridge/Oracle

Other Chains

Contracts

SDK & Library

Docs

Demo dApp

Milestone-1
- Timeline: March 7th
- Goals:
  - the cross-chain data bridge works end-to-end with deal aggregation & deal making.
  - Token payment integrated.
  - better documentations on intro, instruction and tutorial.
  - deploy and test it on Avalanche, Linea, etc.
Milestone-2
- Timeline: end of April
- Goals:
  - build a SDK/Library to bring better DX to other L1
  - run a IPFS cluster for storage buffer
  - adding an option for the xChain client to be able to make storage deals via smart contract
  - Improve onrampContract for better storage proof and monitoring
  - build an fun multi-chain demoApp
Milestone-3
- Timeline: end of June
- Goals:
  - Supporting delegate deal engine.
  - …

Priority	Milestone	Component	Feature description
P0	M1	All	Deploy a working version of MVP on a L2, Linea or Arbitrum.
P0	M1	All	Improve the deployment process for multi-chain. Parasail repo as reference
P0	M1	onramp.sol	Implement token payment function, accepting any ERC20 tokens.
P0	M1	Prover.sol	Make sure the process of getting deal notification and sending cross-chain proof works.
P0	M1	oracle.sol	Verify the proofing process via the Axelar bridge works.
P0	M1	oracle.sol	Properly handle the gas service from the Axelar for transaction fees.
P1	M2	onramp.sol	Provide better functions to read different status in the smart contract

pending storage request
list of storage request for a client
check status of a storage request | | P1 | M2 | Prover.sol | xChain client can make storage deals via clientContract on Filecoin. | | P1 | M3 | onramp.sol | PoDSI proof failed with LHDE, pieceCID(commP) generated by LH is different as deal preparation. | | P1 | M1 | All | upgradable contracts | | P1 | M1 | All | deterministic deployment on different chains |

Priority	Milestone	Component	Feature description
P0	M1	Config	Configurable procedures: event listener, aggregation, deal making.
P0	M1	Config	Using a better way to import and open the wallet for any xChain client operation.
P0	M2	Aggregation	Make it configurable, users can choose to run aggregation or not.
P0	M1	Aggregation	Ensure the aggregation of xChain client work - run it end to end for making deal. Most important, accepting commP, aggregate it and sending Proof.
P0	M1	Deal Making	X-Chain client should be able to make storage deals directly with SP (Piknik or Magic). Need to set Prover contract as Client-ID so contract will be notified once the deal is make on Filecoin.
P0	M1	Deal monitor	sending PoDSI proof to onramp contracts
P0	M2	Deal monitor	Improve the process of checking the pending storage requests from onramp contract, and request dealStatus & podsi for those requests.
P1	M2	Buffer	Depends on Pinata for IPFS storage is not a long term solution. FILB should maintain a IPFS node for this service.
P1	M1	Event listener	Be able to listen to multiple chains for the `DataReady()` event.
P1	M1	Event listener	Be able to process deal request separately for each chain it is listening.
P1	M2 ?	Deal Making	X-Chain client should be able to make storage deal request via smart contract on Filecoin.
P1	M2 ?	Deal Making	Ensure piknik process the storage deal requests through smart contract.

Priority	Milestone	Component	Feature
P0	M1	Docs	Architecture explainer of the whole data bridge projects.
P0	M1	Docs	How to set up and run xChain clients.
P0	M1	Docs	How to deploy contracts on multiple chains, and interact with them.
P1	M1	Tutorial	Before we build SDK, we need to write tutorial for builders in different blockchain ecosystem to learn how to use cross-chain data bridge
P1	M2	SDK	Design the SDK, and planning.
P1	M2	SDK	Implementation & Docs

| --- | --- | --- | --- |