Developers Forum for XinFin XDC Network: ncode

WSS Alternatives RPC?

ncode — Tue, 06 Aug 2024 12:33:29 +0000

Hi, I am using subquery to index some of the contract events,
Subquery requires a wss rpc, I could only find one for apothem which is wss://eaws.apothem.network, are there any other rpc because this one keeps going down frequently , and is down while I am writing this post.

[WIP] multicall3 not working

ncode — Fri, 21 Jun 2024 05:58:18 +0000

Hi,
I am using web3onboard with wagmi to interact with smart contracts on the XDC Apothem Network.

I am using a readContract Method from wagmi.
https://wagmi.sh/core/api/actions/readContract

It seems to use multicall under the hood, which is giving error.

This is the rpc call happening:

This is my code:
https://github.com/nitishpatel/random/blob/b5e1886ac510ade292a2120df62423bcf0d850cb/react/web3onboard-example/src/store/hooks/useTransaction.ts#L37

[WIP] CORS Issue on erpc.apothem.network

ncode — Mon, 18 Dec 2023 05:24:45 +0000

Hi, We are currently experiencing a CORS policy issue that has disrupted access to 'https://erpc.apothem.network/' from our origin 'https://auth.magic.link'. This problem emerged after Saturday, and we urgently need your assistance in resolving it.

The error message is as follows:

Access to XMLHttpRequest at 'https://erpc.apothem.network/' from origin 'https://auth.magic.link' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Could you please investigate and adjust the CORS policy for 'https://erpc.apothem.network/' to include the 'Access-Control-Allow-Origin' header for 'https://auth.magic.link'?

[WIP] EIP 1559 Not Available

ncode — Mon, 30 Oct 2023 06:29:46 +0000

Hi, I was trying to integrate a social sign in provider i.e magic.link for one of the products on xdc chain to allow seam less onboarding. the magic link sdk allows passing custom rpc. However on initiating a transaction , getting the EIP 1559 error.

Is there any RPC which has a work around for this method?
RPC being used: https://erpc.apothem.network

Blockssan for XDC Private Subnet

ncode — Mon, 03 Apr 2023 04:45:41 +0000

Hi,
I have deployed an XDC Subnet and wanted to know if there is any Blocksscan opensource repo using which I can have a blockexplorer for the xdc private subnet
Thanks

Hosting XDC Private Network Problems

ncode — Wed, 22 Mar 2023 05:26:15 +0000

Hello devs, I was trying to run this following guide on hosting the private XDC Subnet.
https://medium.com/xinfin/how-to-set-up-a-private-blockchain-network-with-xdc-network-codebase-b2ee82368e83

I have few doubts I have followed the steps has asked in the blog on my laptop.

Question-1
After I get the bootnode information, How do I put it in the run.sh file? There is no clear instruction about this?

I just replaced all the self:enode I found with the same bootnode information which I think is incorrect.

This is my BootNode Information:

INFO [03-22|10:47:45] UDP listener up                          self=enode://f7ee4ec9f4c7434ba4d04f3afa47d881d83e4f1774ccdbcc2509d50728dc5936210f7ba00c8c990556926dda67de4da98b49be7d2210e0983d433a7f026c18d4@[::]:30301

This is how I have placed it in run.sh

echo Starting the nodes ...
${PROJECT_DIR}/build/bin/$Bin_NAME --bootnodes "self=enode://f7ee4ec9f4c7434ba4d04f3afa47d881d83e4f1774ccdbcc2509d50728dc5936210f7ba00c8c990556926dda67de4da98b49be7d2210e0983d433a7f026c18d4@[::]:30301" --syncmode "full" --datadir ./nodes/1 --networkid "${networkid}" --port 30303 --rpc --rpccorsdomain "*" --ws --wsaddr="0.0.0.0" --wsorigins "*" --wsport 8555 --rpcaddr 0.0.0.0 --rpcport 8545 --rpcvhosts "*" --unlock "${wallet1}" --password ./.pwd --mine --gasprice "${GASPRICE}" --targetgaslimit "420000000" --verbosity ${VERBOSITY} --rpcapi admin,db,eth,debug,miner,net,shh,txpool,personal,web3,XDPoS --ethstats "XinFin-MasterNode-01:xinfin_xdpos_hybrid_network_stats@stats.xinfin.network:3000" &
child_proc="$child_proc $!"
${PROJECT_DIR}/build/bin/$Bin_NAME --bootnodes "self=enode://f7ee4ec9f4c7434ba4d04f3afa47d881d83e4f1774ccdbcc2509d50728dc5936210f7ba00c8c990556926dda67de4da98b49be7d2210e0983d433a7f026c18d4@[::]:30301" --syncmode "full" --datadir ./nodes/2 --networkid "${networkid}" --port 30304 --rpc --rpccorsdomain "*" --ws --wsaddr="0.0.0.0" --wsorigins "*" --wsport 8556 --rpcaddr 0.0.0.0 --rpcport 8546 --rpcvhosts "*" --unlock "${wallet2}" --password ./.pwd --mine --gasprice "${GASPRICE}" --targetgaslimit "420000000" --verbosity ${VERBOSITY} --rpcapi admin,db,eth,debug,miner,net,shh,txpool,personal,web3,XDPoS --ethstats "XinFin-MasterNode-02:xinfin_xdpos_hybrid_network_stats@stats.xinfin.network:3000" &
child_proc="$child_proc $!"
${PROJECT_DIR}/build/bin/$Bin_NAME --bootnodes "self=enode://f7ee4ec9f4c7434ba4d04f3afa47d881d83e4f1774ccdbcc2509d50728dc5936210f7ba00c8c990556926dda67de4da98b49be7d2210e0983d433a7f026c18d4@[::]:30301" --syncmode "full" --datadir ./nodes/3 --networkid "${networkid}" --port 30305 --rpc --rpccorsdomain "*" --ws --wsaddr="0.0.0.0" --wsorigins "*" --wsport 8557 --rpcaddr 0.0.0.0 --rpcport 8547 --rpcvhosts "*" --unlock "${wallet3}" --password ./.pwd --mine --gasprice "${GASPRICE}" --targetgaslimit "420000000" --verbosity ${VERBOSITY} --rpcapi admin,db,eth,debug,miner,net,shh,txpool,personal,web3,XDPoS --ethstats "XinFin-MasterNode-03:xinfin_xdpos_hybrid_network_stats@stats.xinfin.network:3000"

After which on running run.sh I get the following error:

Question - 2
The run.sh also throws "list M1 not found" error.

Ownership of a Master Node Using a Multisignature wallet or smart contract wallet

ncode — Sat, 04 Mar 2023 13:51:12 +0000

If I am interested in hosting a master node with a group of friends and want to ensure equal ownership of the node, using a MultiSignature wallet Is this possible on the network? While there are currently no masternode owners which are smart contract-based wallets, it is possible to use a MultiSignature wallet as the masternode owner.Considering MultiSignature wallets are also smart contracts.

If a smart contract-based wallet can be used as a masternode owner, it raises the question of what the KYC process will entail. However, the current mn.xinfin.network platform does not offer an option to connect a smart contract to upload KYC documents and proceed with staking.

If direct interaction is done with XDCValidator contract what should be the hash one can pass to the updateKYC(string hash) method to complete the KYC Process of a MultiSignature Wallet / Smart Contract?

The steps after the KYC is quite simple and should be easily executable by a multisignature wallet
1) propose(address coinbaseAddress) To stake the 10M
2) resign(address coinbaseAddress) to resign the node.
3) withdraw(uint256 blockNumber,uint256 index) to claim back the initial stake.

Additionally, it is worth noting whether the current consensus algorithm / evm has the ability to distribute rewards to a smart contract or a multisignature wallet.

[Closed]Error Revert statements not working consistently

ncode — Mon, 27 Feb 2023 17:02:40 +0000

Hi devs,
I would like to share a issue / bug on the XDC network which is related to the Revert / Require statements and how it behaves based on the RPC being used, wallets being used.

You can understand about this issue by reading the github issue created by another dev.
https://github.com/XinFinOrg/XDPoSChain/issues/173

Also look into this comment of how it behaves on Remix when an error occurs while using XDCPay vs Metamask.
https://github.com/XinFinOrg/XDPoSChain/issues/173#issuecomment-1446690292

You can also check about how All the wallets behave differently for an error in one of my previous xdc.dev post.
https://www.xdc.dev/ncode/error-strings-support-in-xdc-4bec

I think the goal should be to provide consistent error strings and handling revert / requires irrespective of RPC's or wallets being used.

[WIP]Account not managed by node

ncode — Thu, 26 Jan 2023 13:45:43 +0000

Hello fellow developers,

I am currently encountering an error when trying to test a contract using Hardhat. The error message states "HardhatError: HH103: Account 0x175530dfced40bbe17a22cff76c2b765f1b2f8f8 is not managed by the node you are connected to."
The error is coming as a part of the script I am running to simulate multiple wallet addresses on my contract. I have being using this account for more than a year , You can check the Blocksscan for the same.
Link to BlockSscan

I have tried resolving the issue by double-checking that the account being used is unlocked and has enough XDC to perform the action on the contract, but the error persists. I have also tried connecting to a different RPC, but the issue remains.

If anyone has encountered this error before or has any suggestions on how to resolve it, please let me know. Your help would be greatly appreciated.

[Solved]How to check masternode status?

ncode — Tue, 24 Jan 2023 05:47:54 +0000

Hello Developers,

I am working on a project that involves interacting with a blockchain network, specifically a Node. I am trying to determine if the Node is a core node, or a standby node.

Are there any particular commands or methods that can be used to check the status of a Node on the network? Are there any smart contract methods that tell us the type of the node, when the coinbase address is passed? Or any API which returns the status of the node, when the coinbase address is passed?

If anyone has experience with this and could share their knowledge or point me in the right direction, it would be greatly appreciated. Thank you in advance for your help!

[Closed]Error Strings Support in XDC

ncode — Tue, 24 Jan 2023 05:40:30 +0000

Recently Since last week, The RPC's seems to have changed, and the error message strings are no longer working properly.
For eg:
if there is an Ownable error intially it use to return

"Ownable Caller is not the owner"

How ever since the last week post XDCPay 2.0 beta release the error statements are not user friendly

EDIT
We are using 0x supported RPC's , however the error is coming irrespectively of the rpc under use, If we use XDCPay then the error strings are coming as blank as shown below.

The error string is different however when using MetaMask

And Finally this is how the error string looks when using XDCPay2.0

[Solved]Whats the maximum gas limit one can have in a transaction?

ncode — Sat, 21 Jan 2023 06:12:15 +0000

Hi, I am working on a project which has a few resource heavy transaction, I would like to what's the maximum gasLimit I can have on the XDC Network