Developers Forum for XinFin XDC Network: Raghuram Dharanipathy

[WIP] Apothem RPC link unstable

Raghuram Dharanipathy — Mon, 18 Dec 2023 06:56:01 +0000

We are facing issue in our Plugin nodes with Apothem RPC links. Tried using the RPC links provided in https://chainlist.org/?chain=50&search=apothe. For the past 4 days we are getting this issue in our servers. One or the other RPC link from chainlist page used to work, now all the links are unresponsive.

Is this a known issue? Is someone working on this ?

[WIP]XDC Private Blockchain Setup - Known Issues

Raghuram Dharanipathy — Mon, 19 Jun 2023 08:08:38 +0000

The Plugin Development Team is actively considering the implementation of a Private Blockchain for certain use cases. Although we found the process of setting up the XDC Private Blockchain to be straightforward, we encountered some issues that we brought to the attention of the XDC Core Team for resolution.

The following issues were identified during the implementation of the Private Blockchain, and we reported them to the XDC Core Team for fixing:

The error "panic: runtime error: invalid memory address or nil pointer dereference" (Issue: PR-271 - Pending)
The XDC Private chain was halted, and no new blocks were being created (Issue: PR-264 - Pending)
The errors "list M1 not found" and "nonce too low" (Issue: PR-238 - Fixed)

We also discovered that the Apothem explorer only accepts Solidity version 0.4.26 for verifying and publishing contracts (Issue: smart-contract-verifypublish-errored-out-in-apothem - Pending ), and a fix was provided for one version.

To bring attention to these issues, we published posts on XDC.dev, which you can find here:

We also shared the logs with the core team to assist in debugging.

If you are a developer or blockchain enthusiast attempting to set up an XDC Private Blockchain, we hope that this article proves useful in keeping you updated. Please feel free to reach out if you have any questions, as we are happy to provide support.

[WIP]Private Subnet halted, stopped creating blocks.

Raghuram Dharanipathy — Tue, 16 May 2023 12:36:22 +0000

We started private blockchain using XDPoSChain. The private chain halted creating blocks today(16th May 2023), there is no error in /var/log/syslog file and the chain's log file.

The private chain stopped at approx 467165 blocks. Could someone let me know the root cause for sudden halt in creating blocks.

Raised a PR in XDPoSChain git. Documents are attached in the PR.

Enable secure websocket(WSS)&(https) for full node using Nginx

Raghuram Dharanipathy — Tue, 09 May 2023 17:46:30 +0000

This article gives you the concise information about setting up of secured websocket(WSS) for your full node.

Setting up of Nginx and the configuration tweaking needed for https is clearly mentioned in "How to configure SSL for XDC private chain on server with Nginx".

Tweaking needed for enabling WSS in Nginx configuration file is given below.

Now you need to edit the NGINX configuration file /etc/nginx/sites-enabled/default:

map $http_upgrade $connection_upgrade {
    default upgrade;
    '' close;
}

upstream websocket {
   server 127.0.0.1:8888;
}
server {


        root /var/www/html;

        # Add index.php to the list if you are using PHP
        index index.html index.htm index.nginx-debian.html;
    server_name <domainName>; # managed by Certbot


        location / {
                # First attempt to serve request as file, then
                # as directory, then fall back to displaying a 404.
                try_files $uri $uri/ =404;
                proxy_pass http://localhost:8989;
        }

       location /websocket {
            proxy_pass http://websocket;
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection $connection_upgrade;
            proxy_set_header Host $host;
        }


    listen [::]:443 ssl ipv6only=on; # managed by Certbot
    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/xdcprivate.goplugin.co/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/xdcprivate.goplugin.co/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
    if ($host = <domainName>) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


        listen 80 ;
        listen [::]:80 ;
    server_name <domainName>;
    return 404; # managed by Certbot


}

We use a proxy_pass directive to proxy traffic from an encrypted 443 HTTPS port to node port 8989 on our server instance without exposing it publicly.

Now verify that the config is correct:
sudo nginx -t

and restart the NGINX process to apply changes:

sudo service nginx restart

You can check if your full node is available via a secure HTTPS & WSS connection.

How to configure SSL for XDC private chain on server with Nginx

Raghuram Dharanipathy — Thu, 04 May 2023 16:49:16 +0000

This article gives step by step method to implement SSL for xdc node RPC.

We will see how we can safely expose the API to public by adding by proxing JSON-RPC traffic with NGINX.

You’ll need a domain to implement this solution. It can be a root domain or a subdomain. You have to add an A DNS record pointing to the IP of your EC2 instance. It is recommended to use an Elastic IP address so that the address would not change if you have to change the instance configuration.

Next, inside the instance, you have to install the necessary packages:

sudo apt-get install nginx apache2-utils sudo apt-get install python3-certbot-nginx

You can now generate an SSL certificate and initial NGINX configuration by running:

sudo certbot --nginx -d <domainName>

To automatically renew your certificate add this line to /etc/crontab file:

@monthly root certbot -q renew

Once you complete these steps, you should see an NGINX welcome screen on your domain:

Now you need to edit the NGINX configuration file /etc/nginx/sites-enabled/default:

server {


        root /var/www/html;

        # Add index.php to the list if you are using PHP
        index index.html index.htm index.nginx-debian.html;
    server_name <domainName>; # managed by Certbot


        location / {
                # First attempt to serve request as file, then
                # as directory, then fall back to displaying a 404.
                try_files $uri $uri/ =404;
                proxy_pass http://localhost:8546;
        }


    listen [::]:443 ssl ipv6only=on; # managed by Certbot
    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/xdcprivate.goplugin.co/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/xdcprivate.goplugin.co/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
    if ($host = <domainName>) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


        listen 80 ;
        listen [::]:80 ;
    server_name <domainName>;
    return 404; # managed by Certbot


}

The SSL certificate files are automatically generated by the certbot command

We use a proxy_pass directive to proxy traffic from an encrypted 443 HTTPS port to Geth node port 8545 on our server instance without exposing it publicly.

Now verify that the config is correct:

sudo nginx -t

and restart the NGINX process to apply changes:

sudo service nginx restart

The default welcome page should no longer be accessible. You can check if your full node is available via a secure HTTPS connection.

You can use this RPC link https://<domainName> in your XDCPay wallet to create a new profile as "private chain" and fill other details like your chainID etc., as mentioned below.

Once your new Network profile is saved, then using the Network profile deploy a simple contract using remix and check for the successfull deployment.

XDC Private Blockchain Setup - Guide

Raghuram Dharanipathy — Wed, 29 Mar 2023 13:47:16 +0000

This information will guide individuals in setting up XDC private blockchain. The steps mentioned in this writeup are executed and tested on Ubuntu Linux 20.04 LTS version.

XDC Private Blockchain setup steps

1. Server Requirement

OS version: Ubuntu 20.04
RAM : Minimum 16Gb, Better 32Gb
STORAGE : 50Gb

2. Install golang

Please refer to the install page. Go Version used in setting up XDC private blockchain is go1.20.2.
Remember to set environment variables:
GOPATH=/home/ubuntu/go
GOROOT=/usr/local/go

3. Prepare XinFin client

Untill "pr 238" is merged in XinFinOrg github, you can use this Repo.

cd ${HOME}
git clone https://github.com/GoPlugin/PLI_XDC_Private_Blockchain.git
cd ${HOME}/PLI_XDC_Private_Blockchain/XDPoSChain
make all

4. Create genesis

cd ${HOME}/PLI_XDC_Private_Blockchain/XDPoSChain/build/bin
./puppeth

4.1 Input XDPoS as network name

Please specify a network name to administer (no spaces or hyphens, please)
> XDPoS

4.2 Input 2 to configure new genesis

What would you like to do? (default = stats)
 1. Show network stats
 2. Configure new genesis
 3. Track new remote server
 4. Deploy network components
> 2

4.3 Input 3 to select XDPoS

Which consensus engine to use? (default = XDPoS)
 1. Ethash - proof-of-work
 2. Clique - proof-of-authority
 3. XDPoS - delegated-proof-of-stake
> 3

4.4 Input 2 as block time

How many seconds should blocks take? (default = 2)
> 2

4.5 Input 2000 as reward

How many Ethers should be rewarded to masternode? (default = 10)
> 2000

4.6 Input an address for first masternode

Who own the first masternodes? (mandatory)
> xdc85f33E1242d87a875301312BD4EbaEe8876517BZ

4.7 Input three addresses for signers

Which accounts are allowed to seal (signers)? (mandatory at least one)
> xdc757f225273eba574196ef04f6c22bcc3ec623adc
> xdc09c1a2b3c620665ebda5aefcf51b775073b3be60
> xdccfb27876e117bcee77085c984f9042f4d43ada13
> xdc

Mention 3 addresses: (These addresses should be from your XDCPay Wallet Account, without xdc prefix.)

757f225273eba574196ef04f6c22bcc3ec623adc
09c1a2b3c620665ebda5aefcf51b775073b3be60
cfb27876e117bcee77085c984f9042f4d43ada13

4.8 Input 900 as blocks per epoch

How many blocks per epoch? (default = 900)
> 900

4.9 Input 5 as gap

How many blocks before checkpoint need to prepare new set of masternodes? (default = 450)
> 5

4.10 Input foundation address

What is foundation wallet address? (default = xdc0000000000000000000000000000000000000068)
> xdc50a1c6bc2156499cfda614a0e9855ba1758bf321

Mention an address: 50a1c6bc2156499cfda614a0e9855ba1758bf321 without xdc prefix. (This address is from your XDCPay Wallet Account)

4.11 Input three addresses for foudation MultiSignWallet

Which accounts are allowed to confirm in Foundation MultiSignWallet?
> xdcd9ac740163cc633c05b00c589eb7c9997925511b
> xdc4fe0fb8578841584a3693c010c455fd8a056b7d2
> xdc90597dbfdef58819fae19af21d40c03e4315bb9d
> xdc

4.12 Input 2 as require number

How many require for confirm tx in Foundation MultiSignWallet? (default = 2)
> 2

4.13 Input addresses for Team MultiSignWallet

Which accounts are allowed to confirm in Team MultiSignWallet?
> xdcd9ac740163cc633c05b00c589eb7c9997925511b
> xdc4fe0fb8578841584a3693c010c455fd8a056b7d2
> xdc90597dbfdef58819fae19af21d40c03e4315bb9d
> xdc

Mention 3 addresses: (These addresses are from your XDCPay Wallet Account, without xdc prefix.) NOTE: These are the same addresses used in step 4.11

d9ac740163cc633c05b00c589eb7c9997925511c
4fe0fb8578841584a3693c010c455fd8a056b7d3
90597dbfdef58819fae19af21d40c03e4315bb9e

4.14 Input 2 as require number

How many require for confirm tx in Team MultiSignWallet? (default = 2)
> 2

4.15 Input address for swap wallet

What is swap wallet address for fund 55m XDC?
> xdc90597dbfdef58819fae19af21d40c03e4315bb9e

Mention an address: 90597dbfdef58819fae19af21d40c03e4315bb9e without xdc prefix.(This address is from your XDCPay Wallet Account)

4.16 Input some addresses to prefund

Which accounts should be pre-funded? (advisable at least one)
> xdcd756f8cd4083c86497622c0c6193bdfe860f04ez
> xdc0801590680024aa5b4499226947276f5e327b72a
> xdc

Mention some addresses: (These addresses are from your XDCPay Wallet Account, without xdc prefix)

d756f8cd4083c86497622c0c6193bdfe860f04ez
0801590680024aa5b4499226947276f5e327b72a

4.17 Input network ID

Specify your chain/network ID if you want an explicit one (default = random)
> 111

4.18 Export the genesis file

What would you like to do? (default = stats)
 1. Show network stats
 2. Manage existing genesis
 3. Track new remote server
 4. Deploy network components
> 2

 1. Modify existing fork rules
 2. Export genesis configuration
 3. Remove genesis configuration
> 2

Which file to save the genesis into? (default = XDPoS.json)
> XDPoS.json

Select 2 to manage existing genesis.
Select 2 to export genesis configuration
Enter genesis filename: XDPOS.json
Press CtrL + C to exit

The gensis file is saved to: ${HOME}/XDPoSChain/build/bin/XDPoS.json.

4.19 Modify the genesis file

Edit the genesis file ${HOME}/XDPoSChain/build/bin/XDPoS.json, add the below line:
"constantinopleBlock": 4,
under the line which has "eip155Block": 3

5. Setup bootnode

cd ${HOME}/XDPoSChain/build/bin
./bootnode -genkey bootnode.key
./bootnode -nodekey ./bootnode.key

Copy bootnode information from the output of above mentioned command.
enode://enode://fa88a0faf3f57a5911e287c12326f5a50adf960f4e8e0cc8ce2287ac04b49873c6bb7c144113d9fcae15f40be9c281a3404ea3cc72c29fd4556fe2e3e4ebfa8f@[127.0.0.1]:30301

Then press Ctrl+C to stop bootnode program.

6. Start the masternodes

6.1 Setup Local_DPoS_Setup

cd ${HOME}/Local_DPoS_Setup

6.2 Copy genesis and bootkey files

cp ${HOME}/XDPoSChain/build/bin/XDPoS.json ${HOME}/Local_DPoS_Setup/genesis/
cp ${HOME}/XDPoSChain/build/bin/bootnode.key ${HOME}/Local_DPoS_Setup

6.3 Setup ENODE and private keys

Edit file ${HOME}/Local_DPoS_Setup/.env, add 4 private keys(of 1 master node, 3signer nodes as given in step 4.6, 4.7) without 0x prefix:

ENODE=<ENODE_VALUE>
PRIVATE_KEY_0=<KEY_0>
PRIVATE_KEY_1=<KEY_1>
PRIVATE_KEY_2=<KEY_2>
PRIVATE_KEY_3=<KEY_3>

6.4 Start private networks

Edit file ${HOME}/Local_DPoS_Setup/start-3-signers-networks.sh, edit line number 21 to include your XDPoS.json file
./start-3-signers-networks.sh

6.5 Verify private networks

Once the node starts, wait for the block number * 4 times the blocks per epoch as given under the topic 4.8.
If, the node persists beyond this threshold then the private blockchain is ready for performing transactions.

7. Configure XDCPay

7.1 Configure the RPC, chain ID

Add a new Network under "Network Settings"
Network Name => Private Blockchain
New RPC URL => http://:
Chain ID => As given in topic 4.17

IMPORTANT: XDC Private Blockchain need to have 3 or 5 signer as mentioned under "4.7" topic. If we try to set it up using 2 or 4 signer node then we will have brain split as mentioned in this link.

[Solved]Smart contract Verify&Publish errored out in Apothem explorer

Raghuram Dharanipathy — Wed, 15 Mar 2023 12:27:30 +0000

Hello Members,

While doing verification of smart contract, the API(https://explorer.apothem.network/api/contracts) of Apothem explorer has failed, due to that we are unable to Verify&publish and the page is loading forever.

Could someone fix this issue in "https://explorer.apothem.network/"? So, I can verify & publish the contract.

[WIP]XDC private blockchain Fail to create tx sign for signer error

Raghuram Dharanipathy — Mon, 20 Feb 2023 09:20:37 +0000

Hello Fellow Members,

I am getting the below mentioned error while running XDC private masternode.

ERROR[02-20|03:51:49] Fail to add tx sign to local pool. error="nonce too low" number=120 hash=0x9382c04e84120118b80511fe5919005232c6e9853df37d1793d1c22dcaf4d8bb from=xdc757f225273eBA574196EF04f6c22bCC3Ec623aDB nonce=117 ERROR[02-20|03:51:49] Fail to create tx sign for signer error=err

Could someone throw some light on resolving this issue.

Proof of Reserve in Plugin

Raghuram Dharanipathy — Fri, 27 Jan 2023 05:38:15 +0000

Plugin is working on to provide the PoR as a service to crypto based centralized exchange and other crypto backed businesses. PoR in Plugin provides cryptographical attestation to the audit result of the reserve. The hash generated out of the audit result is checked periodically with the latest state of the audit from the audit firm.

Plugin has implemented the PoR in Staking for yield farming use case. In yield farming our node operators staking & re-staking assets were aggregated and provided in a transparent manner. Through this approach we gained the confidence of our stakeholders and also our transparency in publishing the reserve has got laurels across our community.

Having said that, similar approach will be applied on other crypto backed and fiat backed stable coins. There are many crypto backed assets in the market , which requires Proof of Reserve to bring transparency and entrust to their stakeholders. In implementing this service the fintech institutions which guard the reserve and provide the audit service will be part of the ecosystem, to bring real time data for periodical verification.

Let’s get into the intricacies of “Proof of Reserve”, to understand what Plugin is trying to offer!!

What is Proof of Reserve?

Decentralized finance, or "DeFi", is a rapidly growing sector of the cryptocurrency industry that enables financial transactions to occur on a decentralized, blockchain-based network. One of the key features of DeFi is the concept of "proof of reserve", which is a mechanism used to ensure that a decentralized platform has the assets it claims to have in order to back its operations.

Proof of reserve is a way for a DeFi platform to demonstrate to its users that it holds a certain amount of assets, such as cryptocurrencies, in reserve. This is important because it gives users confidence that their investments or transactions will be backed by real assets, rather than just being a promise on a whitepaper.

There are several different ways that a DeFi platform can prove its reserve. One common method is through transparency and publicly accessible smart contract. By making its reserve holdings transparent, a platform can demonstrate that it has the assets it claims to have and that they are being properly secured.

Proof of Assets (PoA)

The simplest form of proving asset ownership is for an exchange to claim a wallet, and then make a transaction with the crypto inside of it.
By digitally signing a transaction, the exchange proves it controls the private keys and thus owns the wallet.

Proof of Liabilities (PoL) and Merkle Trees

Proof of Liabilities in simpler terms, funds an organization owes its customers.
Publishing Proof of Liabilities for any organization in crypto space has a significant risk of exposing the user name and user deposits.
To mitigate the risk, Proof of Liabilities is carried out with the help of Merkle Trees.
In a Merkle tree, data about each individual depositor (name + balance of deposits) is recorded as “leaves.” Usernames are cryptographically converted into data called hashes to provide a layer of protection.

Proof Of Reserve

Proof of Reserves is simply the audit of a firm’s funds by a third party. During the process of PoR, an exchange provides information to demonstrate its ability to cover user withdrawals with assets held in its reserves. The auditor then publishes its findings for the public.

How does Proof of Reserve works

If a crypto entity can show it owns a specific wallet, this would provide the requisite Proof of Assets (PoA).
If it can also attest to the sum of user deposits, this would fulfill a Proof of Liabilities (PoL).
Together, these confirm what the community really hopes to ensure: Proof of Reserve. Thus PoR = PoA + PoL

Limitations of Proof of Reserves:

First, PoR only provides a snapshot in time of current holdings. This does not prevent institutions from moving assets around before and after the PoR audit.
Another limitation of PoR is scope since PoR only assures a company's holdings and liabilities (if done right) at a moment in time, and not other risks. Companies can still be vulnerable to other factors such as bad economic environment, poor internal management, or even hacks.
Finally, audits do rely on a third party to verify that everything is in order. That means that, in a space where decentralization and trustlessness are prized, a little trust in third parties is necessary when conducting PoR.

In conclusion, proof of reserve is a crucial aspect of decentralized finance. It gives users confidence in the platform's ability to meet its obligations, and helps to maintain the stability of the platform. Platforms can prove their reserves through transparency and publicly accessible smart contract, or by using third-party auditors to verify their reserve holdings. As the DeFi space continues to grow and evolve, proof of reserve will likely become an even more important consideration for users and platforms alike.

[Resolved]xinfin remix not responding

Raghuram Dharanipathy — Thu, 22 Dec 2022 08:35:04 +0000

Hi,

I am unable to open up https://remix.xinfin.network/, it is giving "Connection timed out Error".