howardkitto opened a new issue #53: Counterparty Endpoint URL: https://github.com/apache/incubator-milagro-dta/issues/53 I propose that we create a new feature that enables a DTA to store a list of "approved counterparties". A counterparty is any actor (represented by an account ID) who participates in creating, storing, or revealing a secretkey. Such as the beneficiary, or any entity that is required to give approval. The default service should simply accept a post that a new id is added to a DTA counterparty list. (Plugins may add additional approval criteria) The list is stored locally (in bolt by default) The default service should implement the following endpoints: ``` POST /counterparty {accountID string, timeStamp int, reference string} <- unique string to provide user friendly lookup eg "Name" RETURNS 200 Get /counterparty?perPage=n&page=n&sortBy=dateAsc||dateDesc RETURNS {...IDDoc} Get /counterparty/accountID/{accountID}||/reference/{reference} RETURNS {...IDDoc} ``` In this version the DTA should simply check that the accountid exists (ie just looik it up on IPFS / Tendermint) In future we may add additional verification steps (such as verifying a signature posted with the request)
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@milagro.apache.org For additional commands, e-mail: issues-h...@milagro.apache.org
