Filesharing Track: Testnet v0.1

Deliverables

1. Block Protocol Optimizations

The Codex block protocol is broken in many ways. This provisionally improves its performance and reliability until we can do a rewrite.

FURPS: Serving Frontends, Modules, and Files

  1. [F1-F4]: Covers all functional requirements for file sharing (see FURPS for more details).
  2. [U5]: Specs. The set of services, protocols and primitives making up the filesharing client are published as specifications.
  3. [R1]: Correctness. If the network is eventually stable and the content is available, then downloads should always complete.

2. C Bindings

C bindings serve as basis upon which specialized language bindings can be built. This includes the Logos core integration, as well as the Go bindings required by Status.

FURPS: Serving Frontends, Modules, and Files

  1. [U1]: C API. A C API with primitives for publishing and downloading files by address is published.