First Steps

Let's get started! Before diving in, identify two key things:

• The overall environment where your dApp will operate.
• The specific blockchain(s) your dApp will interact with.

Different blockchains require different tools. Find the right one for your target blockchain. For more details on these tools, explore the example targets provided.

---

Access a multiple Production Blockchains

Accessing multiple blockchains in a single project can be challenging, since there is currently no generic wrapper, to access basic functionalities, like transfer balances, or accessing account information. This is due to the nature of the individual blockchains, defining on their own which version of a pallet they run. As an example, a Parachain can run a very old version of the frame system account pallet, leading to a different structure of AccountInfo, and with C# being a typed language, we do face here a challenge. Of course, there are solutions, and workarounds that allow to use of multiple blockchains in a single project, for example, please check out the Explorer Demo project.

Example:

[Account](system.account: FrameSystemAccountInfo)

{
  nonce: 0
  consumers: 1
  providers: 1
  sufficients: 0
  data: {
    free: 1,817,782,297,000,000
    reserved: 2,613,650,000,000
    frozen: 0
    flags: 170,141,183,460,469,231,731,687,303,715,884,105,728
  }
}

---

Local Target Connection

When running a node, the default local target is ws://127.0.0.1:9944. This WebSocket connection is exposed in the node's startup logs.

To test and execute reference calls, connect via Polkadot.JS Interface. This interface provides a user-friendly way to interact with the node.