docs(examples/cbdc): fix successful minting on chaincode results in balance 0

[Anusha-Padmanabhan]

Describe the bug

Started the app of CBDC example and front end using the commands as per the given readme.
https://github.com/hyperledger/cacti/tree/main/examples/cactus-example-cbdc-bridging-backend
I am getting the below UI,

I can able to mint and see the transaction logs but after minting where I can view those tokens and what is the next step to do transfer, escrow, bridge out and in.

To Reproduce

clone the repository
cd cactus
from the root of the repository run the below commands:
npm run enable-corepack
npm run configure
npm run start:example-cbdc-bridging-app

Expected behavior

Minted token should reflect somewhere or enable the other buttons of transfer, escrow
Steps to understand the workflow of CBDC example is missing

Logs/Stack traces

Can help maintainers identify root causes

Screenshots

docker run -p 2000:2000 aaugusto11/cactus-example-cbdc-bridging-frontend

npm run start:example-cbdc-bridging-app

Hyperledger Cactus release version or commit (git rev-parse --short HEAD):

Either a semantic version of the release you are using such as 1.0.0 or a git
commit hash if you are directly working with code from the git repository.

Hyperledger Cactus Plugins/Connectors Used

• Which DLT connectors are you using (Fabric, Quorum, Corda, Besu, etc.)

Additional context

Add any other context about the problem here.

[petermetz]

@Anusha-Padmanabhan I'll try to answer, but @RafaelAPB and @AndreAugusto11 might have a more up to date picture on this.

I can able to mint and see the transaction logs but after minting where I can view those tokens

If you've set up the example as per the steps, then the ledgers are running on your machine, so you could observe the ledger state by querying those containers in your preferred way.

and what is the next step to do transfer, escrow, bridge out and in.

If I remember correctly you unlock those options on the UI by putting the tokes into escrow first. Let me know if this helps, in the meantime I'm closing the question as answered, but of course feel free to re-open as needed.

[Anusha-Padmanabhan]

@petermetz Thanks for the response, But the escrow button is not enabled after minting and token balance is also not reflecting in the screen.
Attaching the screenshot after minting.

I believe, once after minting escrow and transfer buttons should get enabled and minted token balance also should be visible in the screen.

[petermetz]

@Anusha-Padmanabhan I went ahead and re-did the steps as well, it won't re-enable.
The minting seems to succeed but then as the UI calls the balanceOf method of the contract, that returns 0 after the successful minting anyway. Looks like this got broken somewhere along the way so I'm re-opening this as a bug.

cc: @RafaelAPB @AndreAugusto11

Also closing the other one you opened as a duplicate.

[AndreAugusto11]

Hi @petermetz and @Anusha-Padmanabhan thank you for your feedback. I will have a look at this asap, and ping you here

[petermetz]

Hi @petermetz and @Anusha-Padmanabhan thank you for your feedback. I will have a look at this asap, and ping you here

@AndreAugusto11 Nice, thank you very much for helping!!!

[AndreAugusto11]

@petermetz this is definitely a strange one. I checked the chaincode container logs, and the tokens are being minted correctly. So, the problem is in the GET request, which is always returning 0. I haven't changed anything in the code, have there been any breaking changes that might be causing this (also in the Fabric all in one image)?

[petermetz]

@petermetz this is definitely a strange one. I checked the chaincode container logs, and the tokens are being minted correctly. So, the problem is in the GET request, which is always returning 0. I haven't changed anything in the code, have there been any breaking changes that might be causing this (also in the Fabric all in one image)?

@AndreAugusto11 I also checked the chaincode container logs and the computed state keys are inconsistent so something is off with the minting configuration IMO.
If you log the keys in the contract then you'll see that the Mint and the BalanceOf methods generate different state keys such as shown below (observe the first 2 components being swapped)
They are technically identical identities, but the contract uses plain strings for the state keys so they end up being different anyway and that's why the BalanceOf can't find the tokens of the identity that were minted.

x509::/OU=org1/OU=client/OU=department1/CN=userA::/C=US/ST=North Carolina/L=Durham/O=org1.example.com/CN=ca.org1.example.com
x509::/OU=client/OU=org1/OU=department1/CN=userA::/C=US/ST=North Carolina/L=Durham/O=org1.example.com/CN=ca.org1.example.com

[AndreAugusto11]

@petermetz thanks for providing those logs.

So, the Mint function calculates the clientID dynamically based on the request, and the BalanceOf function receives as an argument the clientID provided by the front end. For some reason, those identities got mismatched. I have updated the code such that the Mint function receives the identity just like the Balance function does.

I haven't tested because I'm having some issues with my GCP VM (and can't do it in my M1), can you do it @Anusha-Padmanabhan?

[Anusha-Padmanabhan]

Sure @AndreAugusto11, I will test and let you know..

[Anusha-Padmanabhan]

Hi @petermetz @AndreAugusto11
Could you please share the node and npm version you have used to test the cbdc app, Since I am getting the following error once after starting the app using the command "npm run start:example-cbdc-bridging-app".