Delta is a deal-making service that enables users to make deals with Storage Providers. It is an application that allows users to upload files to the Filecoin network and get them stored by Storage Providers.
Note that these requirements may vary depending on the specific needs of your application.
A delta node is a light ipfs node that can run on set of machines and architectures. It’s written in go and can be run on any machine that can run go.
To run a delta node, you need to have the following pre-reqs installed on your machine:
Alternatively, if using Ubuntu, you can run the following commands to install the pre-reqs
apt-get update && \
apt-get install -y wget jq hwloc ocl-icd-opencl-dev git libhwloc-dev pkg-config make && \
apt-get install -y cargo
Delta repoClone the repo to your machine
git clone github.com/application-research/delta
Copy the .env.example file to .env and update the values as needed.
# Node info
NODE_NAME=delta-node
NODE_DESCRIPTION=Experimental Deal Maker
NODE_TYPE=delta-main
# Database configuration
MODE=standalone
DB_DSN=delta.db
DELTA_AUTH=[NODE_API_KEY_HERE]
# Frequencies
MAX_CLEANUP_WORKERS=1500
Here are the fields in the .env file:
NODE_NAME is the name of the node.NODE_DESCRIPTION is the description of the node.NODE_TYPE is the type of the node.MODE can be standalone or cluster. If standalone, the node will run as a single node. If cluster, the node will run as a cluster node.
standalone mode is primarily for those who want to run delta in an isolated environment. This mode will create a local database and a local static API key for all requests. To get a static key, run https://auth.estuary.tech/register-new-token. Copy the generated key and paste it in the DELTA_AUTH field.cluster mode is for those who want to run delta as a cluster. This mode will connect to a remote database. In this mode, you don’t need to specify the DELTA_AUTH field. The node will use the API key provided by Estuary.DB_DSN is the database connection string. If standalone, the node will create a local database. If cluster, the node will connect to a remote database.DELTA_AUTH is the API key used to authenticate requests to the node.MAX_CLEANUP_WORKERS is the maximum number of workers that can be used to clean up the blockstore. This is an optional field. If not specified, the default value is 1500.Put the .env file in the same location as the binary/executable.
make langmake all
./delta daemon --repo=/path/to/blockstore --wallet-dir=<walletdir>
./delta daemon --repo=/path/to/blockstore
A delta node being a deal-making service, needs a wallet to make deals. You can specify a custom wallet location using the --wallet-dir flag.
Note that this is a directory and not a file. The wallet file(s) is expected to be in this directory.
./delta daemon --wallet-dir=/path/to/wallet
Note: You can register a new wallet later using the /admin/wallet/register endpoint.
You can also build and run the delta node using docker. To do so, you need to have docker installed on your machine.
docker build -t delta .
docker run -it --rm -p 1414:1414 delta --repo=/path/to/blockstore --wallet-dir=<walletdir>
cluster mode if mode is not specified.The console output will look something like this:
Delta version: v0.0.1
OS: darwin
Architecture: arm64
Hostname: Alvins-MacBook-Pro.local
2023/03/21 13:49:59 INF 1 (145.40.77.207:4150) connecting to nsqd
Starting Delta daemon...
Setting up the whypfs node...
repo: .whypfs
walletDir: ./wallet_estuary
mode: cluster
enableWebsocket: false
statsCollection: true
Wallet address is: f1jxx7uendecy62l2m7w7tyo5d7wszysp467xztfy
Setting up the whypfs node... DONE
Computing the OS resources to use
Total memory: 151526048 bytes
Total system memory: 219757864 bytes
Total heap memory: 173735936 bytes
Heap in use: 165814272 bytes
Stack in use: 27590656 bytes
Total number of CPUs: 10
Number of CPUs that this Delta will use: 10
Note: Delta instance proactively recalculate resources to use based on the current load.
Computing the OS resources to use... DONE
Running pre-start clean up
Number of rows cleaned up: 0
Running pre-start clean up... DONE
Subscribing the event listeners
Subscribing to transfer channel states...
Subscribing to transfer channel events...
Subscribing the event listeners... DONE
Running the atomatic cron jobs
Scheduling dispatchers and scanners...
Running the atomatic cron jobs... DONE
Starting Delta.
%%%%%%%%/ %%%%%%%%%%%%%%% %%%%% %%%%%%%%%%%%%%%%% %%%%%%
@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@ @@@@@ @@@@@@@@@@@@@@@@@ @@@@@@@@
@@@@@ @@@@@@@ @@@@@@ @@@@@ @@@@@ @@@@@@@@@@
@@@@@@ @@@@@ @@@@@ @@@@@ @@@@@ @@@@@ @@@@@
@@@@@ @@@@@ @@@@@@@@@@@@@@ (@@@@@ @@@@@ @@@@@ @@@@@
@@@@@@ @@@@@@ @@@@@@@@@@@@@ @@@@@ /@@@@@ @@@@@ #@@@@,
@@@@@ @@@@@@ @@@@@* @@@@@@ @@@@@ @@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@ @@@@@@@@@@@@@@ @@@@@@ @@@@@ @@@@@
@@@@@@@@@@@@@@ @@@@@@@@@@@@@@ @@@@@@@@@@@@@@@ @@@@@ @@@@@ @@@@@
(ᵔᴥᵔ)(ᵔᴥᵔ)(ᵔᴥᵔ)(ᵔᴥᵔ)(ᵔᴥᵔ)(ᵔᴥᵔ)(ᵔᴥᵔ)(ᵔᴥᵔ)(ᵔᴥᵔ)(ᵔᴥᵔ)(ᵔᴥᵔ)(ᵔᴥᵔ)(ᵔᴥᵔ)(ᵔᴥᵔ)(ᵔᴥᵔ)(ᵔᴥᵔ)
By: Protocol Labs - Outercore Engineering
version: v0.0.1
----------------------------------
Welcome! Delta daemon is running...
----------------------------------
____ __
/ __/___/ / ___
/ _// __/ _ \/ _ \
/___/\__/_//_/\___/ v4.9.0
High performance, minimalist Go web framework
https://echo.labstack.com
____________________________________O/_______
O\
⇨ http server started on [::]:1414
Now that you have the node running, you can start making deals.
If you to use an existing live Delta node, go to getting started using a live delta node.