Most processes, especially once we start looking at use in a production level environment, won't be quite so simple. So let's take a look at a more advanced case.
(and if you are running Windows, be sure that you don't already have CB open. This is a known bug, and we will fix it soon, but we wanted to be able to share circuits with you as soon as we could!!)
This is 2 separate workflows, contained in the same circuit.
The first one (top), labeled "Download-Hash-Anchor", does the following:
The next workflow is a pretty straight line. This one is doing something a little more advanced, but more "real life". It is RE-hashing the original file to be compared against the hashed data that was stored on the blockchain. Since we (effectively) can't reverse-engineer hashed data, we have to start from the original data again.
In your production environment, you may want to store the verification in a database or file somewhere, and/or possibly send some kind of alert on a verification failure. This may be an email, SMS, or http request to POST data to a web server, for example.
We are looking forward to seeing what circuits YOU build, and also to continue sharing circuits with you that we have built.
What do YOU want to see us build next?? Join the CircuitBuilder Chat Telegram channel and join in the discussion!
We just sent you an email. Please click the link in the email to confirm your subscription!