TestNetSetup

[ashi31]

This is to update the test tokens structure to faucetName + token_level + token_number. This token structure is to be used to create test RBTs in the faucet node.

CLI Command
./rubixgoplatform generatefaucetrbt -numTokens 2 -did bafybmif2cnmxooupsefy2rdy3vf3yt7xoojess4zedmoqvh3neezhi6uyq -port 20000

API request
curl --header "Content-Type: application/json" --request POST 'http://localhost:20000/api/generate-faucettest-token' --data '{"did": "bafybmif2cnmxooupsefy2rdy3vf3yt7xoojess4zedmoqvh3neezhi6uyq", "number_of_tokens":1 }'

Once we input the token level, all the tokens of that level will be generated within the faucet. The faucetName const FaucetName can be updated in tokenmapping.go file.

To check the content of token and validate the faucet token and its corresponding genesys block to verify the owner and signature of the token as being the same as the faucetDID:
CLI command
./rubixgoplatform faucettokencheck -token QmcE8pm9p1ZUP7PGkFR5CrZsZzQkNoXB9Szy1Ns2DFQraw -port 20000

API request
curl -X GET "http://localhost:20000/api/faucet-token-check?token=QmcE8pm9p1ZUP7PGkFR5CrZsZzQkNoXB9Szy1Ns2DFQraw"

Sample output :
Token owner validated successfully. Token details = Faucet Name : faucet1, Token Level : 3, Token Number : 2

[thewebchap]

Do we need to merge this to development branch? Some of the code is specific to only faucet node , questionable whether it needs to be merged and accessible to all nodes.
As I see , some additions are needed for nodes to interact with faucet (this can be merged to development) , the faucet server specific lines can be skipped.
@gklps @arnabghose997 thoughts?

[arnabghose997]

Do we need to merge this to development branch? Some of the code is specific to only faucet node , questionable whether it needs to be merged and accessible to all nodes. As I see , some additions are needed for nodes to interact with faucet (this can be merged to development) , the faucet server specific lines can be skipped. @gklps @arnabghose997 thoughts?

I believe there isn't any issue with merging the PR dev, since Faucet interaction is centered around Testnet tokens only

[gklps]

Let's maintain the faucet as its own distinct branch, encompassing all faucet-related additions