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
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
: 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
: a URL to RPC node provider for the Near Protocol network.PRIVATE_KEY
: It will be used to sign the transactions.
Last updated