-
Notifications
You must be signed in to change notification settings - Fork 5
Expand file tree
/
Copy path.env.sample
More file actions
63 lines (51 loc) · 3.04 KB
/
Copy path.env.sample
File metadata and controls
63 lines (51 loc) · 3.04 KB
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
DATABASE_URL=postgresql://postgres:postgres@localhost:5432/postgres
OBJECT_MAPPING_ARCHIVER_URL=wss://indexer.mainnet.autonomys.xyz/ # update to your if you want
FILES_GATEWAY_URL=http://changeme.com # change to your own (or it'll fail when fetching archived files)
FILES_GATEWAY_TOKEN=changeme # change to your own (or it'll fail when fetching archived files)
AUTH_SERVICE_API_KEY=1234567890 # change to your own if updated in auth
RABBITMQ_URL=amqp://guest:guest@localhost:5672
# ---------------------------------------------------------------------------
# Pay-with-AI3 / purchased credits feature
# ---------------------------------------------------------------------------
# Feature flags — set BUY_CREDITS_ACTIVE=true to enable the purchase flow.
# BUY_CREDITS_STAFF_ONLY=true restricts it to admin/staff accounts only,
# useful for a staged rollout before opening to all users.
BUY_CREDITS_ACTIVE=false
BUY_CREDITS_STAFF_ONLY=false
# EVM endpoint for the AutoDriveCreditsReceiver contract.
# Point this at the Auto-EVM RPC for the target network (mainnet or Taurus
# testnet). The payment manager watches this chain for deposit events.
EVM_CHAIN_ENDPOINT=http://localhost:8545
# Address of the deployed AutoDriveCreditsReceiver contract.
# Must match the chain pointed to by EVM_CHAIN_ENDPOINT.
EVM_CHAIN_CONTRACT_ADDRESS=0x0000000000000000000000000000000000000000
# Number of block confirmations to wait before treating a payment as final.
# Higher values reduce the risk of processing a payment that is later
# reversed by a chain reorganisation. Default: 6.
EVM_CHAIN_CONFIRMATIONS=6
# How often (in milliseconds) the payment manager polls for CONFIRMED intents
# that have not yet had credits applied. This is a fallback for cases where
# the event watcher misses a log. Default: 30000 (30 seconds).
EVM_CHAIN_CHECK_INTERVAL=30000
# Price multiplier applied on top of the raw Autonomys consensus fee to
# determine the AI3 cost per byte. A value of 5.0 means users pay 5× the
# current on-chain transaction byte fee. Default: 5.00.
CREDITS_PRICE_MULTIPLIER=5.00
# ---------------------------------------------------------------------------
# Credit lifecycle
# ---------------------------------------------------------------------------
# Number of days after purchase before a credit batch expires.
# Users see this value on the purchase confirmation screen and in their credit
# history. Default: 90.
CREDIT_EXPIRY_DAYS=90
# Maximum total purchased upload bytes allowed per user across all active
# (non-expired) credit rows. Attempts to purchase beyond this cap result in
# an OVER_CAP intent requiring admin review. Default: 107374182400 (100 GiB).
MAX_CREDITS_PER_USER=107374182400
# How often (in milliseconds) the background job runs to mark expired credit
# rows and clean up stale PENDING intents. Default: 3600000 (1 hour).
CREDIT_EXPIRY_CHECK_INTERVAL=3600000
# How many minutes a PENDING intent remains valid before it is treated as
# expired. Users must submit their on-chain transaction within this window
# after creating an intent. Default: 10.
INTENT_EXPIRY_MINUTES=10