-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy path.env.example
60 lines (48 loc) · 3.15 KB
/
.env.example
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
VITE_PROJECT_ID=ef3aae15-28ca-4585-a6fd-43382424181c
VITE_GOOGLE_CLIENT_ID=679052511930-8dqur4mmg8egbttgos5pmr4ljtf3etbb.apps.googleusercontent.com
VITE_RECAPTCHA_SITE_KEY=6LfFd_8gAAAAAOCVrZQ_aF2CN5b7s91NEYIu5GxL
VITE_SOULBOUND_NFT_CONTRACT_ADDRESS=0x50F49A3B09BD7597ff588686843d9b03070EdCbe
# For deployer of SoulBoundNFT contract
VITE_DEPLOYER_PK=
# Biconomy
VITE_PAYMASTER_KEY=
# Magic
VITE_PUBLIC_MAGIC_API_KEY=
# Alchemy RPC
VITE_ALCHEMY_API_KEY=
# This file contains environment variables that can be used to configure the Onyx SSI examples repository.
# The following variables are needed for examples that use the did-ethr (Ethereum DID Resolver).
# NETWORK_RPC_URL: The URL of the RPC network. This is typically a URL that points to your Ethereum node or Ethereum gateway.
# CHAIN_ID: The ID of the Ethereum chain you're connecting to. This helps to ensure the correct network is used. For example, Ethereum mainnet is '1' etc...
# NETWORK_NAME: The name of the network you're using.
# REGISTRY_CONTRACT_ADDRESS: The registry contract address you're interacting with.
NETWORK_RPC_URL=https://rpc-mumbai.maticvigil.com
CHAIN_ID=80001
NETWORK_NAME=mumbai
REGISTRY_CONTRACT_ADDRESS=0x33C695F89ab8F8f169fa652AD9a896C4e4AD34eb
# The following variables are used as keys for the issuer. You can either use your own keys or generate new ones using the /src/create-keypair.ts script.
# If no value is provided, the program will automatically generate a key pair for you and store it in a file called keys.json in the root directory.
# ISSUER_EDDSA_PRIVATE_KEY: The issuer's EdDSA (Elliptic Curve Digital Signature Algorithm) private key.
# ISSUER_ES256K_PRIVATE_KEY: The issuer's ES256K (Elliptic Curve Digital Signature Algorithm with SHA-256) private key.
ISSUER_EDDSA_PRIVATE_KEY=
ISSUER_ES256K_PRIVATE_KEY=
# The following variables are used as keys for the holder. You can either use your own keys or generate new ones using the /src/create-keypair.ts script.
# If no value is provided, the program will automatically generate a key pair for you and store it in a file called keys.json in the root directory.
# HOLDER_EDDSA_PRIVATE_KEY: The holder's EdDSA private key.
# HOLDER_ES256K_PRIVATE_KEY: The holder's ES256K private key.
HOLDER_EDDSA_PRIVATE_KEY=
HOLDER_ES256K_PRIVATE_KEY=
# VC (Verification Credentials)
# VC_DIR_PATH: The directory where your verification credentials are stored. If no value is provided, it defaults to '/src/verification_credentials'.
# VC: The name of the verification credential you're using.
# VC_ES256K_PRIVATE_KEY: The private key used for revocation of this verification credential. Remember, keep this secure!
# VC_SCHEMA_URL: This is the remote URL where the schema for your verification credential is hosted.
VC_DIR_PATH="../../src/pages/verifiable-credentials/vc_store"
VC=
VC_ES256K_PRIVATE_KEY=
VC_SCHEMA_URL=http://json-schema.org/draft-06/schema#
# VP (Verification Presentation)
# VP_DIR_PATH: The directory where your verification presentations are stored. If no value is provided, it defaults to '/src/verification_presentation'.
# VP: The name of the verification presentation you're using.
VP_DIR_PATH="../../src/pages/verifiable-credentials/vc_store"
VP=