.env.example

# API Configuration
ALLOWED_ORIGINS=http://localhost:3000,http://localhost:5173

# Database Configuration
DATABASE_URL=postgresql://user:password@host:5432/database?sslmode=require

# Blockchain Configuration (Citrea)
RPC_URL=https://rpc.citreascan.com
DEPLOYMENT_BLOCK=2650850
BLOCKCHAIN_ID=4114

# Monitoring Configuration
MAX_BLOCKS_PER_BATCH=1000
RPC_BATCH_SIZE=25

# Price Cache Configuration (in milliseconds)
PRICE_CACHE_TTL_MS=120000
PG_MAX_CLIENTS=10

# CoinGecko Configuration.
#
# COINGECKO_BASE_URL: required. The origin the service calls. Recommended is
# the in-cluster pricing-proxy (https://github.com/DFXswiss/pricing-proxy),
# which holds the upstream Pro key and serves a 60 s shared cache. Anything
# CoinGecko-compatible works (pro-api.coingecko.com, api.coingecko.com, …).
COINGECKO_BASE_URL=http://pricing-proxy:8080/coingecko
#
# COINGECKO_API_KEY: optional. If set, attached as `x-cg-pro-api-key` to every
# request. Leave unset when talking to the pricing-proxy (proxy injects its
# own key) or to the public host anonymously.
# COINGECKO_API_KEY=

# GeckoTerminal Configuration.
#
# GECKOTERMINAL_BASE_URL: required. The origin used for GeckoTerminal token
# price calls. Recommended is the in-cluster pricing-proxy
# (https://github.com/DFXswiss/pricing-proxy), which gives cache, coalescing
# and validation on top of the shared free-tier 30 req/min quota. Anything
# GeckoTerminal-compatible works (api.geckoterminal.com directly is fine for
# single-consumer setups, but the free-tier quota is shared across the whole
# host IP).
GECKOTERMINAL_BASE_URL=http://pricing-proxy:8080/geckoterminal

# Telegram Bot Configuration (optional)
# TELEGRAM_BOT_TOKEN=5123456789:ABCdefGHIjklMNOpqrsTUVwxyz
# Path to the persisted subscribers file. Each operator subscribes themselves by
# sending /start (or /subscribe) to the bot — chat-ids are appended here and survive
# container restarts. Mount /app/.monitoring as a docker volume in production.
# TELEGRAM_GROUPS_JSON=/app/.monitoring/telegram.groups.json
# TELEGRAM_ALERTS_ENABLED=false
# ALERT_TIMEFRAME_HOURS=12

# Tier tag prepended to telegram alert headers (e.g. [DEV], [PRD]).
# Identifies the server tier; deploy convention is dfxprd -> prd, dfxdev -> dev.
# ENVIRONMENT=dev

# Optional chain name prepended to telegram alert headers after the tier tag
# (e.g. [PRD] [MAINNET]). Identifies which chain a multi-chain monitoring stack
# observes when the same chat receives alerts from several chains. Leave
# unset on single-chain stacks. Free-form value, rendered upper-cased.
# CHAIN=Mainnet

# Minter-guard auto-deny watcher.
#
# When enabled, the watcher iterates PROPOSED minters at the end of every
# monitoring cycle and submits denyMinter() for any address not on the
# committed whitelist (src/monitoringV2/config/whitelist.{testnet,mainnet}.json).
# Bridge proposals are not exempted: the bridge type is inferred from a trivial
# usd() view call and is therefore unsafe to exclude.
#
# GUARD_ENABLED          true/false. Disables the watcher entirely if false.
# GUARD_PRIVATE_KEY      Hex private key (0x...) of the signer. Must hold or be
#                        delegated enough voting power to pass checkQualified()
#                        on the JUSD reserve.
# GUARD_HELPER_ADDRESS   Address passed as the single helper to denyMinter().
#                        Use the equity holder that delegated to the signer.
# GUARD_WHITELIST_FILE   Absolute path to the whitelist JSON inside the
#                        container (e.g. /app/src/monitoringV2/config/whitelist.mainnet.json).
# GUARD_ENABLED=false
# GUARD_PRIVATE_KEY=0x0000000000000000000000000000000000000000000000000000000000000000
# GUARD_HELPER_ADDRESS=0x0000000000000000000000000000000000000000
# GUARD_WHITELIST_FILE=/app/src/monitoringV2/config/whitelist.mainnet.json