I have currently used SignRequest in the past to have other parties sign documents and then not only have a hash of those documents emailed to all parties (well to me who would forward the hash) .
I would also take the extra step via SR to store that hash on the blockchain they used. At first this wasn't that useful to me, as I was the one with the original document until a customer edited a document and hash and I could show them the record on the chain and that was proof that the Statement of Work had been edited.
Anchoring the hash on the chain also, gave the signees comfort that the hash and document couldn't be edited by me in the future and it would easily solve any future disputes about originality of the signed document (as mentioned in my above example)
I now wish to use Box Sign going forward to carry out the same business process and have checked the API's and I can see that hashes are still supported which is great.
However I can't see anything in the api or support docs, about anchoring the hash on a chain.
I can do this myself with any chain that has smart contracts Eth for example , or even chains without smart contracts and just use a memo code for a nominal network transaction
however I'd much rather prefer that the solution is all in one, built in the signing process like previously.
By the way I'm not sure if the dev community is the right place to ask. However I figured that it would be an item built into the API's if it wasn't in the UI.
It used to be in the UI under a label/tickbox = "show blockchain proof in signing log"
Thanks in advance.
Please sign in to leave a comment.