commit b981558c685503b50e26b295fa51dc43b917dd53 parent 13b2205836d1d91e58d973648b2a47870ad7f76d Author: Christian Grothoff <christian@grothoff.org> Date: Thu, 26 May 2016 15:06:22 +0200 remove dead /hash-contract API logic Diffstat:
| M | impl-merchant.rst | | | 14 | -------------- |
1 file changed, 0 insertions(+), 14 deletions(-)
diff --git a/impl-merchant.rst b/impl-merchant.rst @@ -65,20 +65,6 @@ The Merchant Backend HTTP API The following API are made available by the merchant's `backend` to the merchant's `frontend`. -.. http:post:: /hash-contract - - Ask the backend to compute the hash of the `contract` given in the POST's body (the full contract - should be the value of a JSON field named `contract`). This feature allows frontends to verify - that names of resources which are going to be sold are actually `in` the paid cotnract. Without - this feature, a malicious wallet can request resource A and pay for resource B without the frontend - being aware of that. - - **Response** - - :status 200 OK: - hash succesfully computed. The returned value is a JSON having one field called `hash` containing - the hashed contract - .. http:post:: /contract Ask the backend to add some missing (mostly related to cryptography) information to the contract.