Developers Forum for XinFin XDC Network: Phill Menezes

[Informative] Importing XDC Wallet to Metamask

Phill Menezes — Fri, 09 Feb 2024 17:37:06 +0000

This short tutorial shows how to import our browser-based XDC Wallet to Metamask, giving users more flexibility on where they want to hold their assets.

1️⃣ Backing up our Seed Phrase from XDC Wallet.

It would help if you backed up the keys you created for XDC Wallet using the Mnemonic Phrase or Private Key options. It is not impossible to import a Keystore File to Metamask, but converting a Keystore File into a usable Private Key is rather complicated.

When you created your XDC Wallet, you will be able to see your Mnemonic Phrase, like the one showed below:

This is the Phrase Key we will use later to import your address to Metamask.

2️⃣ Configuring Metamask Network.

To be completely compatible with XDC, our Metamask must be configurated to point to the XinFin EVM-Complatible RPC URLs. To do that, open your metamask and:

I. Click on the three dots (top-right)
II. Click on Settings

III. Go to Networks

IV. Click on Add Network

A new window will open. Here he have to choose the option Networks again and click on Add a network

And then choose the options Add a network manually

In the Add a network manually window, fill the new network form with the following info:

Network Name: XinFin XDC Network
New RPC URL: https://erpc.xdcrpc.com
Chain ID: 50
Currency Symbol: XDC
Block Explorer URL: https://xdcscan.io

And Save!

3️⃣ Importing wallet to Metamask:

Method 01 - Private Key

If you own a Private Key, the process is pretty straight forward: Your need to:

Click on your Account Name -> Choose Add account or hardware wallet -> Import Account

And finally hit Import!

Method 02 - Mnemonic Phrase from XDC Wallet

To import our wallets from a Mnemonic Phrase we need to recover the private key from the Mnemonic, to do that, we are going to use the tool Mnemonic Code Converter by All private Keys:

https://allprivatekeys.com/mnemonic-code-converter?#english

You will need two things:

Your Mnemonic Phrase
The password used to create your XDC Wallet Accout

Fill the fields highlighted with your info (Choose Ethereum for Coin and BIP44 for Derivation Path):

Scroll down to Derived Addresses and check if the address you see is the address you want to import:

If this is the right address, slide to the end of the row, where you are going to find the associated Private Key:

Now head to Method 1 and continue importing your XDC Wallet to Metamask! 🎉

Feature Request: Make "Verify and Publish" feature available via API

Phill Menezes — Fri, 07 Oct 2022 23:34:18 +0000

Summary of the request: Other block scanner services have successfully provided a verification tool available via API (i.e., Etherscan). It allowed the community to develop tools and plugins like truffle-verify-plugin, which makes the verification process a much less time-consuming task for developers, thus, improving the development experience.

Following this reasoning, I believe it would be a great addition to the Blockscan API, an endpoint that allows users to use the verification feature through an API call.

This issue is also being tracked on GitHub

@blocksscanio @blocksscan @walterblueu

Unwanted behavior while using standard XDCPay RPC endpoints and web3 library

Phill Menezes — Wed, 28 Sep 2022 19:01:47 +0000

Summary: While using XDCPay standard RPC endpoints to connect to decentralized apps using the web3 npm package, dApps are unable to check for transactions receipt due to incompatibility with the Ethereum Standard RPC.

Reproducing the error

It is possible to use XDCPay injected provider to create a web3modal that can be used for ReactJS/Next.js dapps using web3 npm package. This would be the natural pathway to interact with decentralized apps in EVM-based networks, this is the case for XDC Network too.

By using XDCPay HttpProvider, however, we are using the XDC compatible endpoints:

  50: 'https://xdcpayrpc.blocksscan.io/',
  51: 'https://apothemxdcpayrpc.blocksscan.io/'

Which, at first glance, is not a problem since it does not prevent us from accessing web3 methods. We can still send and fetch blockchain data using a Web3 object created using XDCPay injected provider.

However, the problem is when we expect a transaction receipt to update our front-end information or compute transaction outcomes. We get the following message error:

Uncaught (in promise) Error: Failed to check for transaction receipt:
{}
    at Object._fireError (web3.min.js?2efa:9:16886)
    at eval (web3.min.js?2efa:10:25360)

Fix

To check if this behavior only occurred with RPC endpoints that are not fully compatible with the Ethereum standard, I have configured XDCPay to use the Ethereum-compatible alternative RPCs:

  50: 'https://erpc.xinfin.network/',
  51: 'https://erpc.apothem.network/'

Fortunately, using these endpoints is enough to avoid the compatibility error with the web3 library.

Sugestion

My suggestion would be to make Ethereum Compatible endpoints a native feature on XDCPay:

This issue is also being tracked on Github
@blocksscanio @blocksscan @walterblueu

Ethereum Compatible RPC Endpoint on Apothem rejecting remote calls

Phill Menezes — Mon, 19 Sep 2022 18:36:47 +0000

Summary: Currently, tools like Truffle Suit and Hardhat don't fully support the official XDC RPC endpoints due to the xdc prefix. An issue has been raised both with Truffle and Hardhat by @gzliudan but in both cases, each team responded that making addresses with the xdc prefix compatible to their tools would imply in breaking changes and suggested working on making XDC RPC endpoints compatible to Ethereum standards.

Fortunately, XDC already provides Ethereum Compatible RPC Endpoints:

https://erpc.xinfin.network - for XDC Mainnet
https://erpc.apothem.network - for Apothem Testnet

Although the Ethereum Compatible Endpoint for XDC Mainnet (https://erpc.xinfin.network) works perfectly with Truffle and Hardhat, the Apothem Testnet endpoint is showing an unwanted behavior.

Rejected Calls on Truffle:

/home/taurinos/xdc_comm/docs/how-to/Pizza/node_modules/eth-block-tracker/src/polling.js:51
        const newErr = new Error(`PollingBlockTracker - encountered an error while attempting to update latest block:\n${err.stack}`)
                       ^
Error: PollingBlockTracker - encountered an error while attempting to update latest block:
undefined
    at PollingBlockTracker._performSync (/home/taurinos/xdc_comm/docs/how-to/Pizza/node_modules/eth-block-tracker/src/polling.js:51:24)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
UnhandledRejections detected
Promise {
  <rejected> {
    code: -32603,
    message: 'Unknown Error: ',
    data: { originalError: {} }
  }
} {
  code: -32603,
  message: 'Unknown Error: ',
  data: { originalError: {} }
}

Same Behavior when trying to access RPC methods via HTTP:

By accessing https://erpc.apothem.network/x/eth_blockNumber, for example, it returns:

Post "http://0.0.0.0:8989": dial tcp 0.0.0.0:8989: connect: connection refused

While, accessing https://rpc.apothem.network/x/eth_blockNumber will return:

This is an example call for eth_blockNumber.

Request
{
  "jsonrpc": "2.0",
  "id": "1",
  "method": "eth_blockNumber",
  "params": [
    "latest"
  ]
}
Response
{
  "jsonrpc": "2.0",
  "id": "1",
  "result": "0x2530daf"
}