roadmap/content/codex/updates/2024-03-25.md

4.4 KiB
Raw Blame History

title tags date lastmod draft description
2024-03-25 Codex Weekly
codex-updates
2024-03-25 2024-03-25 false Weekly update of Codex

Codex Update Mar 19th - Mar 25th

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:

  1. Client, Testing, and Infrastructure
  2. Marketplace
  3. Research

The different teams have actively moving on various fronts. The following are their team updates to various ongoing Epics.

Client, Testing and Infrastructure

Client

Completed

Ongoing

Testing

Completed

  • Fixed proof generation is dist-test environment
  • Fixed crash in dist-test env related to blockchain inspection
  • Bring up-to-date continuous tests (enable transient-node and marketplace test scenarios) Ongoing
  • Why do proofs with EC params 1-0 fail?
  • Node response to fill-slot call is unreliable in geth env
  • Wrap up discord-reward bot

Infrastructure

Completed

Ongoing

Marketplace

Completed

Ongoing

  • See previous week

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)
7. Encryption

Completed

Ongoing

  • working towards implementing a Plonkish prover with custom accelerator gadgets, so that we can test proof system ideas
  • realized that proof system idea has a botleneck; may still speed up Poseidon hashing, but the new botleneck is much worse for binary circuits like SHA256. To make the latter practical needs new ideas.