Developers Forum for XinFin XDC Network

Cover image for Request for test XDC via faucet.apothem.network/
Initiative Impactors
Initiative Impactors

Posted on • Updated on

Request for test XDC via faucet.apothem.network/

Hi!
I represent the Initiative Impactors https://www.weimpactors.com/ , which focuses on promoting environmentally responsible behavior through digital rewards and certificates. Our goal is to increase recycling rates and sustainable consumption. More details about our rewards program https://www.weimpactors.com/rewards .

As part of our project, we plan to use smart contracts on the XDC blockchain to create NFTs that will serve as digital certificates, incentivizing target actions within our community.

However, we have encountered an issue: we are unable to obtain test XDC tokens through the Apothem Faucet.

We are using a wallet in MetaMask, configured as follows:

Network Name: XDC Apothem Testnet
New RPC URL: https://rpc.apothem.network
Chain ID: 51
Currency Symbol: TXDC
Block Explorer URL: https://explorer.apothem.network
Wallet Address: 0xB8196BF2915891002873715C82c9F0738893cA54
When attempting to request test XDC through the Apothem Faucet, we receive a server error message. We would like to know if the function to obtain test XDC is currently operational and if there are any alternative methods to obtain test tokens for our project.

Our next step will be to implement a proof-of-recycle mechanism that verifies the recycling of useful materials by Impactors participants and tracks the impact of recycling efforts.

Thank you for your assistance!

Discussion (2)

Collapse
mitali_blocksscan profile image
Mitali_BlocksScan

Hello @initiative_impactors_d2ff
We hope that the above issue is resolved, if the issue still persists then please let us know about it so that the team can resolve it on priority. It will be grateful to get an update within 72 hours or else it will be considered resolved.
Thank You.

Collapse
0xbeny profile image
Beny

Pls use this: faucet.blocksscan.io
Note: XDC network has two address prefixes: xdc and 0x

xdc prefix RPC-compatible: rpc.apothem.network
0x prefix RPC-compatible: erpc.apothem.network