Decentralized Durability Engine
Go to file
Slava 86257054ee
chore: update testnet marketplace address (#983) (#984)
Signed-off-by: Slava <20563034+veaceslavdoina@users.noreply.github.com>
2024-11-04 00:41:03 +00:00
.github
benchmarks
codex chore: update testnet marketplace address (#983) (#984) 2024-11-04 00:41:03 +00:00
docker Add ETH_PRIVATE_KEY to Docker entrypoint (#982) 2024-11-03 06:51:57 +00:00
metrics
tests chore: update dependencies, especially nim-ethers to chronos v4 compatible version (#968) 2024-10-30 10:40:17 +00:00
tools/cirdl chore: update dependencies, especially nim-ethers to chronos v4 compatible version (#968) 2024-10-30 10:40:17 +00:00
vendor fix: bumps ethers to fix missing nonce error (#980) 2024-11-01 17:23:43 +00:00
.dockerignore
.editorconfig
.gitignore
.gitmodules
LICENSE-APACHEv2
LICENSE-MIT
Makefile
README.md
build.nims
codecov.yml
codex.nim
codex.nimble
config.nims
env.sh
openapi.yaml Move the upload headers to the POST method (#978) 2024-10-29 14:40:43 +00:00

README.md

Codex Decentralized Durability Engine

The Codex project aims to create a decentralized durability engine that allows persisting data in p2p networks. In other words, it allows storing files and data with predictable durability guarantees for later retrieval.

WARNING: This project is under active development and is considered pre-alpha.

License: Apache License: MIT Stability: experimental CI Docker Codecov Discord Docker Pulls

Build and Run

For detailed instructions on preparing to build nim-codex see Build Codex.

To build the project, clone it and run:

make update && make

The executable will be placed under the build directory under the project root.

Run the client with:

build/codex

Configuration

It is possible to configure a Codex node in several ways:

  1. CLI options
  2. Environment variables
  3. Configuration file

The order of priority is the same as above: CLI options --> Environment variables --> Configuration file.

Please check documentation for more information.

Guides

To get acquainted with Codex, consider:

API

The client exposes a REST API that can be used to interact with the clients. Overview of the API can be found on api.codex.storage.