A Working API Call for Notary TX Creation

I was able to repurpose the notary tx creation almost entirely and now we have a dpow ratified API call!

curl --url "http://127.0.0.1:7776" --data "{\"agent\":\"dpow\",\"method\":\"ratify\",\"minsigs\":2,\"timestamp\":1476711523,\"ratified\":[{\"handle\":\"testA\",\"pubkey\":\"03b7621b44118017a16043f19b30cc8a4cfe068ac4e42417bae16ba460c80f3828\"}, {\"handle\":\"testB\",\"pubkey\":\"02ebfc784a4ba768aad88d44d1045d240d47b26e248cafaf1c5169a42d7a61d344\"}]}"

With the above curl issued on two nodes, it automatically generated the following pair of transactions:

http://148.251.57.148:3001/tx/9e87060002b83a292a124576059df6ab06744ccea2905bd34d96fed9e4a92684

https://blockr.io/tx/info/4e70f6bd8da799062c71790f3f0bd5d6bc72aa9d0faf078020da8e4cb5f73943

The convention is that the crypto777 address is the initial address and each ratified pubkey gets an output. This way, only the crypto777 address needs to be monitored to update the state for active notaries and notarized height.

Now the iguana notary dapp has been enhanced to be able to issue election ratification tx, I think it pretty much goes into maintenance mode. Next up are the half dozen komodod items


Bitcointalk Topic Entry

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *

5 + 19 =