Jun 20 2018
- last edited on
May 26 2021
Hi. I've successfully set up one application on Azure Blockchain Workbench following the documents.
However, when I edit data in the SQL database, the DLT watcher of the Web app shows the changed records. I suppose that the SQL database is a copy of the Ledger, and the web simply reads from the database.
So how can I get the actual info, which is stored on the Ethereum Ledger, using corresponding BlockHash or TransactionHash? I'm concerned about the safe and unchangeable characteristics of data, which seems not clarified in the public preview documents.
Jun 21 2018 08:12 AM
Hi Cheng. The database is meant to be a duplicate of the data stored in the attached blockchain. The database makes it easy to visualize and analyze data on the blockchain. We have a backlog item to add additional information in the database to allow customers to verify whether the data in the database has been modified.
Jun 21 2018 07:55 PM
Thanks a lot for your helpful reply. Since neither administrators nor members of the application have access to data stored in the blockchain, does it mean that data are absolutely safe? In other words, how could Azure Blockchain Workbench guarantee that the distributed ledger residing on VMs cannot be changed?
Jun 23 2018 09:43 PM
Jun 25 2018 02:15 AM - edited Jun 25 2018 02:26 AM
Thanks. I think the real data of workbenches are stored in a public blockchain, instead of private ones for each. I can see from the DB that the blockchain numbers of my several contract actions vary from 183 to 28441. If so, it is safe just like Bitcoin so far.
However, I still have two questions. Since Azure Blockchain Workbench utilizes the proof-of-work strategy, who actually mines the blocks?
Besides, I wonder if Azure Blockchain Workbench has a blockchain explorer to query the real data stored in the blockchain, which is just like that of Ethereum (the Log Analytics shows only Highest Reported Block and Avg Block Time).
Jun 25 2018 10:56 AM
Workbench actually uses Ethereum PoA (Parity) and not PoW. In terms of exploring the blockchain, you can open up the RPC endpoint and connect an explorer directly to the blockchain.
Jun 25 2018 02:53 PM
Jun 25 2018 04:09 PM
Jun 25 2018 07:11 PM
Thanks for your reply. I have the same problem to directly connect the ethereum-rpc-endpoint (it shows ERR_CONNECTION_TIMED_OUT). Is there any settings to do before this? I appreciate it if there's any document.
Jun 30 2018 02:20 AM - edited Jun 30 2018 02:27 AM
Edit : Rather than open the eth VMSS publically, it would probably be more secure to SSH to the Worker node with Putty and then create tunnel into the Eth VM:
Re : How to open up the private network with the Ethereum VMSS is described here and confirmed works well:
Obviously for dev + debugging purposes only, not for your production private chain!
You can also SSH into the ABW worker node VMSS directly using the worker load balancer public IP (xxx-lb-public-ip) using the username / password or cert you configured during the deploy. The worker node seems to house ~7 docker containers running various DLT and SQL interaction microservices.
Dec 05 2018 06:57 AM
I use Putty and Pageant to make the SSH hop easy. The process is defined in the link below.