2022-06-23 21:45:42 +00:00
# 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.
2022-05-10 20:41:44 +00:00
[![License: Apache ](https://img.shields.io/badge/License-Apache%202.0-blue.svg )](https://opensource.org/licenses/Apache-2.0)
[![License: MIT ](https://img.shields.io/badge/License-MIT-blue.svg )](https://opensource.org/licenses/MIT)
[![Stability: experimental ](https://img.shields.io/badge/stability-experimental-orange.svg )](#stability)
[![CI ](https://github.com/status-im/nim-codex/actions/workflows/ci.yml/badge.svg?branch=main )](https://github.com/status-im/nim-codex/actions?query=workflow%3ACI+branch%3Amain)
[![Codecov ](https://codecov.io/gh/status-im/nim-codex/branch/main/graph/badge.svg?token=XFmCyPSNzW )](https://codecov.io/gh/status-im/nim-codex)
2022-06-23 21:45:42 +00:00
[![Discord ](https://img.shields.io/discord/895609329053474826 )](https://discord.gg/CaJTh24ddQ)
## Build and Run
2022-08-19 02:40:11 +00:00
For detailed instructions on preparing to build nim-codex see [*Building Codex* ](BUILDING.md ).
2022-06-23 21:45:42 +00:00
To build the project, clone it and run:
```bash
make update & & make exec
```
The executable will be placed under the `build` directory under the project root.
Run the client with:
```bash
2022-08-19 02:40:11 +00:00
build/codex
2022-06-23 21:45:42 +00:00
```
### CLI Options
```
2022-08-19 02:40:11 +00:00
build/codex --help
2022-06-23 21:45:42 +00:00
Usage:
codex [OPTIONS]... command
The following options are available:
2022-11-15 19:16:02 +00:00
--log-level Sets the log level [=INFO].
2022-06-23 21:45:42 +00:00
--metrics Enable the metrics server [=false].
--metrics-address Listening address of the metrics server [=127.0.0.1].
--metrics-port Listening HTTP port of the metrics server [=8008].
-d, --data-dir The directory where codex will store configuration and data..
2022-11-15 19:16:02 +00:00
-i, --listen-addrs Multi Addresses to listen on [=/ip4/0.0.0.0/tcp/0].
-a, --nat IP Addresses to announce behind a NAT [=127.0.0.1].
-e, --disc-ip Discovery listen address [=0.0.0.0].
-u, --disc-port Discovery (UDP) port [=8090].
--net-privkey Source of network (secp256k1) private key file path or name [=key].
2022-06-23 21:45:42 +00:00
-b, --bootstrap-node Specifies one or more bootstrap nodes to use when connecting to the network..
--max-peers The maximum number of peers to connect to [=160].
--agent-string Node agent string which is used as identifier in network [=Codex].
-p, --api-port The REST Api port [=8080].
2022-11-15 19:16:02 +00:00
-c, --cache-size The size in MiB of the block cache, 0 disables the cache - might help on slow
hardrives [=0].
2022-08-19 02:40:11 +00:00
--persistence Enables persistence mechanism, requires an Ethereum node [=false].
2022-06-23 21:45:42 +00:00
--eth-provider The URL of the JSON-RPC API of the Ethereum node [=ws://localhost:8545].
2022-08-19 02:40:11 +00:00
--eth-account The Ethereum account that is used for storage contracts [=EthAddress.none].
--eth-deployment The json file describing the contract deployment [=string.none].
2022-06-23 21:45:42 +00:00
Available sub-commands:
codex initNode
```
### Example: running two Codex clients
2023-02-09 09:56:01 +00:00
To get acquainted with Codex, consider running the manual two-client test described [HERE ](docs/TWOCLIENTTEST.md ).
2022-06-23 21:45:42 +00:00
## Interacting with the client
The client exposes a REST API that can be used to interact with the clients. These commands could be invoked with any HTTP client, however the following endpoints assume the use of the `curl` command.
### `/api/codex/v1/connect/{peerId}`
Connect to a peer identified by its peer id. Takes an optional `addrs` parameter with a list of valid [multiaddresses ](https://multiformats.io/multiaddr/ ). If `addrs` is absent, the peer will be discovered over the DHT.
Example:
```bash
curl "127.0.0.1:8080/api/codex/v1/connect/< peer id > ?addrs=< multiaddress > "
```
### `/api/codex/v1/download/{id}`
Download data identified by a `Cid` .
Example:
```bash
curl -vvv "127.0.0.1:8080/api/codex/v1/download/< Cid of the content > " --output < name of output file >
```
### `/api/codex/v1/upload`
Upload a file, upon success returns the `Cid` of the uploaded file.
Example:
```bash
2022-09-12 17:03:27 +00:00
curl -vvv -H "content-type: application/octet-stream" -H Expect: -T "< path to file > " "127.0.0.1:8080/api/codex/v1/upload" -X POST
2022-06-23 21:45:42 +00:00
```
2022-11-15 19:16:02 +00:00
### `/api/codex/v1/debug/info`
2022-06-23 21:45:42 +00:00
Get useful node info such as its peer id, address and SPR.
Example:
```bash
curl -vvv "127.0.0.1:8080/api/codex/v1/info"
```
2022-11-15 19:16:02 +00:00
### `/api/codex/v1/debug/chronicles/loglevel`
Set [chronicles ](https://github.com/status-im/nim-chronicles ) log level and topic filtering at runtime. The request format is `?level=<MAIN LEVEL>;<FILTER LEVEL>:<TOPIC>` - e.g. `?level=DEBUG;TRACE:codex`
Example:
```bash
curl -X POST -H 'Content-Type: text/plain' -vvv "127.0.0.1:8080/api/codex/v1/debug/chronicles/loglevel?level=DEBUG;TRACE:codex" -d ""
```