Configuration Files
The configuration is handled via the config file: walt.yaml, which overwrites the default config that is packaged within the jar file: src/main/resources/walt-default.yaml
hikariDataSource:
jdbcUrl: jdbc:sqlite:data/walt.db
maximumPoolSize: 5
autoCommit: false
dataSource:
journalMode: WAL
fullColumnNames: false
azureKeyVaultConfig:
baseURL:
id:
secret:
providers:
ethereum: "ethereum"
rinkeby: "https://rinkeby.infura.io/v3/0184192d0f2942c3b0322d79eca162b2"
ropsten: "https://ropsten.infura.io/v3/0184192d0f2942c3b0322d79eca162b2"
polygon: "https://polygon-mainnet.g.alchemy.com/v2/yjbYhlaH3U_vfnTiRQ3miGQS0cKwQMkB"
mumbai: "https://polygon-mumbai.g.alchemy.com/v2/yjbYhlaH3U_vfnTiRQ3miGQS0cKwQMkB"
privateKey: "YOUR_PRIV_ETH_KEY"
keys:
address: "PRIVATE_ETH_KEY"
address: "PRIVATE_ETH_KEY"
address: "PRIVATE_ETH_KEY"
apiKeys:
alchemy: "YOUR_KEY"
nft.storage: "YOUR_KEY"
tezosBackendServer: "http://localhost:3000"
privateKey:
it will be used to sign the transactions. By default, transactions are signed by that private key.The keys are in the format that is exported from MetaMask. e.g.: 51ada6337f405cd61f27aa0f604e0ea97c8bdecfd156a646b4cc20554cfb662fkeys:
a mapping of address and their private keys that are exported from MetaMask. In some use cases, you can choose which private key is used to sign the transaction.alchemy:
an API key from Alchemy.nft.storage:
an API key from nft.storage.tezosBackendServer:
a URL of the NFT Kit JS running instance.
There is another configuration file under the path: js/.env
Tezos configuration :
MAINNET_RPC_URL=""
GHOSTNET_RPC_URL="https://uoi3x99n7c.ghostnet.tezosrpc.midl.dev/"
PRIVATE_KEY=""
MAINNET_RPC_URL
: a URL to RPC node provider for the main Tezos network.GHOSTNET_RPC_URL
: a URL to RPC node provider for the testnet Tezos network "GHOSTNET".PRIVATE_KEY
: It will be used to sign the transactions.
Near Protocol configuration :
NEAR_NODE_URL="https://rpc.testnet.near.org"
NEAR_PRIVATE_KEY=""
NEAR_NODE_URL
: a URL to RPC node provider for the Near Protocol network.PRIVATE_KEY
: It will be used to sign the transactions.
Last updated
Was this helpful?