LogoLogo
ProductsCommunityGitHubShare Feedback
NFT Kit
NFT Kit
  • What is the NFT KIT?
    • Introduction
    • Non-Fungible Tokens (NFTs)
      • NFT | Basics
      • Technologies & Concepts
    • NFT Kit
      • NFT Kit | Basics
        • Overview
        • Functionality
      • NFT Flavors & Ecosystems
      • Architecture
        • Low-Level Service Abstraction
        • Ecosystem Abstraction
        • High-Level Interfaces / APIs
      • Use Cases
  • Getting started
    • Quick Start
  • Ecosystems
    • Ethereum | Polygon | Shimmer
      • Setup
      • NFT | Creation & Management
        • Smart Contract Deployment
        • Minting NFTs
        • Get NFT Metadata
        • Get Account Balance
        • Get Token Owner
        • Get Collection Info
        • Get NFTs by Account
      • NFT | Ownership Verification
        • Ownership Verification
        • Ownership Verification With Traits
      • Smart Contract | Extensions
        • Pausable
        • Burnable
      • Smart Contract | Access Control
        • Ownership
        • Role-Based Access Control
    • Ocean Protocol
      • Setup
      • NFT | Verification
      • NFT | Wallet
      • Architecture
    • Tezos
      • Architecture
      • NFT | Creation & Management
        • Smart Contract
        • Add Minter
        • NFT Minting
        • Fetch NFT metadata
        • Get account NFTs
        • Get contract metadata
      • NFT | Ownership Verification
        • NFT Ownership Verification
        • NFT Ownership Verification Within A Collection
        • NFT Ownership Verification With Traits
      • NFT | Wallet
      • Tutorials
        • Minting NFTs on Tezos
          • Setup
          • New Collection
          • First NFT
          • Verification
          • Wallet
    • Near Protocol
      • Architecture
        • Smart Contract
        • Blockchain NFTs operations
        • NFTs Queries
      • NFT | Creation & Management
        • NEAR Sub-Account
        • Deploy NFT Contract
        • NFT | Minting
      • Querying NFT information controller
        • Get NFTs for account
        • Get NFT By Token Id
        • Get NFT contract metadata
      • NFT | Wallet
      • Tutorials
        • Minting NFT on Near Protocol
          • Near Wallet Creation
          • Setup NFT-Kit
          • Create Sub-account
          • Smart Contract ( Collection )
          • Minting your first NFT
        • NFT Ownership Verification
        • Wallet
    • Polkadot
      • Architecture
      • Query NFTs
        • Unique network
          • Fetching Token id & Collection id
          • Fetching NFT metadata
        • Parachain Networks
          • Fetching Tokens by subscan
          • Fetching EVM ERC721 Collectibles by subscan
      • NFT | Ownership Verification
        • NFT ownership verification
        • NFT ownership verification within a collection
        • NFT ownership verification with traits
      • NFT | Wallet
        • Polkadot parachains
        • Polkadot EVM compatible parachains
    • Flow
      • Architecture
        • Cadence Scripts
        • NFT Operations (FCL)
      • Querying NFT information Controller
        • Get NFTs for an account
        • Get NFTs in Collection
        • Get NFT by Token Id
      • NFT | Ownership Verification
        • NFT ownership verification on Flow
        • NFT ownership verification in collection on Flow
      • NFT | Wallet
        • Flow Blockchain
    • Algorand
      • Architecture
        • Algorand Standard Assets (ASAs)
      • NFT | Creation & Management
        • Account Creation
        • NFT Creation (ARC3)
      • Querying Asset information
        • Get Assets for account
        • Get Asset Details
        • Get NFT Metadata by asset id
        • Get NFT by Asset id
      • NFT | Ownership Verification
        • NFT ownership verification
        • NFT ownership verification with traits
        • NFT ownership verification Based on Creator
        • NFT Metadata verification against a dynamic policy
      • NFT | Wallet
        • Algorand Blockchain
    • IPFS
  • Concepts
    • Soulbound Tokens (SBTs)
    • NFT verification with OPA
  • Configurations
    • Configuration Files
    • Gas Provider
  • Community
    • Discord
    • Twitter
    • Newsletter
    • GitHub Discussions
  • DEVELOPER RELATIONS
    • Roadmap
    • Contribute
    • Share Feedback
    • Contact
  • Product Editions
    • Open Source | Always Free
    • Enterprise | Self-Managed
    • Cloud Platform | Managed
Powered by GitBook
On this page
  • Tezos configuration :
  • Near Protocol configuration :

Was this helpful?

Export as PDF
  1. Configurations

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"
  • Examples:

    • https://rinkeby.infura.io/v3/0184192d0fd9423b52322d79eca162b2

    • https://polygon-mumbai.g.alchemy.com/v2/yjbYhlaH3U_vfnTiRQ3miGQS0cKwQMGh

  • 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.: 51ada6337f405cd61f27aa0f604e0ea97c8bdecfd156a646b4cc20554cfb662f

  • keys: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.

  • 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.

PreviousNFT verification with OPANextGas Provider

Last updated 1 month ago

Was this helpful?

providers: a list of URLs to RPC node provider for every network. You can get them either from or .

alchemy:an API key from .

nft.storage:an API key from .

Infura
Alchemy
Alchemy
nft.storage