Mar 15 2017
- last edited on
May 26 2021
I have seen the Bletchly Azure template and how to spin up a private Ethereum Blockchain in Azure... In the examples, you show how to transmit Ether between accounts. Are there any tutorials on how to write docs (i.e. PDF, Text Blocks, etc...) to the blockchain?
Mar 15 2017 09:53 AM
Good question. There is a demo that we have built around real estate transactions, which allow buyers and sellers to transfer home titles. We haven't released the code for the demo, but we are working on it. That said, at a high level there are several ways to accomplish your scenario. The easiest way is to represent the document as a hash and store the hash on the blockchain.
Mar 15 2017 09:59 AM
So, the hash of the data/doc is saved on the block-chain... Is it important to note/persist the block in which the hash was written in order to go back and validate(at a later time)? Or, is the hash searchable against the entire blockchain.
Also, in the Bletchly example (private blockchain), when we spin it up and the miners are mining, we can see the block count increasing even though no activity is happening. What is processing those blocks in the background and what is going on? Is it just a handshake between miners saying we are in consensus (even though nothing may have happened)?
Mar 15 2017 10:02 AM
The document does not have to be stored on the blockchain itself. You can essentially store the document elsewhere and represent the hash of the document on the chain. You can also ensure the representation of the document on the blockchain uses checksum to validate whether the document (outside the chain) gets updated or not.
With respect to block counts increasing, essentially miners are always doing work and pushing blocks to the chain, albeit, blocks with no transactions.
Mar 15 2017 10:07 AM
Can you provide any guindance/example/tutorial on how to write a hash to the Ethereum blockchain? I can transmit Ether in the Bletchly examples... that's it.
Different topic... When spinning up the Resources in Azure for the Ethereum blockchain, a minimum of 5 VM (?) are created to support the service. Not being a VM expert (supporting the OS, upgrading the OS, etc...), how do you propose the servicing of the blockchain infrastructure in the future. (i.e OS patch, Ethereum software upgrade).... That makes me nervous.
Also, the default setup is to use Azure Classic Storage, can the blockchain be setup to use SQL Server Tables?