Codex Update Feb 20th - Feb 26th
The Codex team continues to make progress with various initiatives to wrap up the demo for the Q1/Q2 public testnet release. An internal testnet has been running for the past few weeks and has been used to test the latest version of Codex and can be accessed using the Codex Testnet Starter documentation.
Ongoing and new lines of research and development will soon begin in preparation for the next version of Codex that will be used for the mainnet release.. Here are the updates from different team members and their ongoing work. Development is currently broken into three distinct teams:
- Client, Testing, and Infrastructure
- Marketplace
- Research
The different teams have actively moving on various fronts. The following are their team updates to various ongoing Epics.
Client, Testing and Infrastructure
Completed: Ongoing:
- Codex team members heading to attend ETH Denver
Epic: Nim Improvements
Completed: Ongoing:
Epic: Wiring the Proving System
Completed: Ongoing:
Epic: Improve Client Stability
Completed: Ongoing:
Marketplace
Epic: End-to-end Testing
Completed:
- Finished PR for availabilities update endpoints
- Ran into very weird bug in one of these:
- Chronos server implementation, Presto or Nim’s HTTPClient
- Could not debug and decided to rather move from HTTP 204 response to 200 one
- Created reproduction repo
- Logged the issue in Presto repo
- Ran into very weird bug in one of these:
- Debugged non-working Dist. testing contracts
Ongoing:
Research
2024 R&D Goals
1. Proving system and aggregation improvements (folding or lookups)
2. Aggregator/validator design
3. DHT improvements
4. Tokenomics and incentive design
5. Bandwidth incentives
6. Dynamic data (appendable data)
Completed:
- helped with figuring out the Ethereum elliptic curve conventions
- gave an elliptic curve talk at the local university; slides for the interested
- found the second bug in the Nim Groth16 prover (in Constantine again)
Ongoing:
- started thinking about the small / dynamic data problem