-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathexample.env
94 lines (75 loc) · 3.39 KB
/
example.env
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
# Use `source .env` to load items, likely you actually want
# ```sh
# set -a # Automatically export variables
# source .env
# set +a # Stop auto-exporting
# <run some commands that need these vars>
# ```
#
# DO NOT wrap variables in quotes (THING=stuff is correct, not THING="stuff")
# Otherwise passing them to docker/podman may fail.
#
# ALL VARIABLES need to be \n terminated, no whitespace trimming happens
#
# ALL PATHS MUST BE A FULL PATH, used in scripts from different working directories,
# All relative paths will fail!
#### Cloud Host SSH
# (Optional) Only required for ssh and scp helpers in ./scripts/*
REMOTE_HOST="[email protected]"
REMOTE_IDENTITY="~/.ssh/your-ssh-private-key"
#### Service Settings
# ONLY for use in development testing OR if running a node on localhost where https isn't required.
# NOTE: data sent to celestia can be http as we have already encrypted it,
# but headers for the JWT to post to celestia are not encrypted without TLS!
UNSAFE_HTTP_UPSTREAM=true # comment this out or unset to force https
# More info on docker in README.md
# https://github.com/nuke-web3/pda-proxy/
DOCKER_CONTAINER_NAME="pda-proxy"
# 32 byte key used for ChaCha20 encryption
ENCRYPTION_KEY=
PDA_DB_PATH=/tmp/db-pda-service-testing
# Expects a socket with ip & port specified (not transport)
# NOTE: 0.0.0.0 binding will allow the service to be accessible to inbound
PDA_SOCKET=0.0.0.0:26657
# Explicit port for docker (can't compute with --env-file)
PDA_PORT=26657
#### ZK Proof Settings
# ELFs running in any zkVM should be deterministically / reproducible with Docker, see:
# https://docs.succinct.xyz/docs/sp1/writing-programs/compiling#production-builds
# IMPORTANT: the prover programs *embed the ELF* into their own bin,
# so this vat is only for development & compilation
# NOTE: MUST USE FULL PATH, used in scripts, so relative will fail.
ZK_PROGRAM_ELF_PATH=
# 'mock' for generating mock proofs locally, 'cpu', 'cuda', or 'network'
SP1_PROVER=cuda
# If using the proving network, set to your whitelisted private key. For more information, see:
# https://docs.succinct.xyz/docs/generating-proofs/prover-network/key-setup
# IMPORTANT: the prover will know the entire input, so you very likely do NOT want this!
# TODO: This feature is NOT fully implemented! We need a TEE wrapper around proving remote for this.
NETWORK_RPC_URL=https://rpc.production.succinct.xyz
NETWORK_PRIVATE_KEY=
#### Dependent & Provider Settings
# To get a new token, see https://docs.celestia.org/tutorials/node-tutorial#auth-token
# Locally running nodes can use:
# celestia <node-type> auth admin --p2p.network <network>
CELESTIA_NODE_WRITE_TOKEN=
CELESTIA_TRUSTED_HEIGHT=
CELESTIA_TRUSTED_HASH=
CELESTIA_DOCKER_IMAGE=ghcr.io/celestiaorg/celestia-node:v0.22.1-mocha
CELESTIA_NODE_CORE_IP=rpc-mocha.pops.one
CELESTIA_NODE_SOCKET=127.0.0.1:26658
CELESTIA_RPC_PORT=26658
CELESTIA_P2P_PORT=2121
CELESTIA_NETWORK=mocha
CELESTIA_NODE_TYPE=light
CELESTIA_NODE_NAME=celestia-light-mocha-4
CELESTIA_DATA_DIR=~/.celestia-light-mocha-4
# TLS - managed by Let's Encrypt `certbot`
# Registration email required for urgent renewal/security notifications
TLS_DOMAIN=your.domain.com
TLS_CERTS_PATH=
TLS_KEY_PATH=
# ONLY for development, you may use dummy TLS setup from source ./service/static
# TLS_CERTS_PATH=/full/path/to/pda-proxy/service/static/sample.pem
# TLS_KEY_PATH=/full/path/to/pda-proxy/service/static/sample.rsa