View Revisions: Issue #4877

Summary 0004877: migrate to new contract-related terminology
Revision 2017-02-02 08:42 by Florian Dold
Description In the new terminology, the frontend creates an "order", the HTTP PUTs it to the backends /propopsal endpoint, which returns the proposal corresponding to the order (with the merchant signature and missing fields in the order filled out.

With a HTTP GET on /proposal, the frontend can query proposals by transaction ID or proposal hash.

The wallet stores as a "contract" the proposal together with signed coins.

Also, "transaction_id" becomes "order_id", since it's used by the frontend to uniquely identify an order.

The transaction_id name might be reused in the future for negotiating instances of payments for the *same* proposal between the exchange and merchant. It's not part of the contract anymore.
Revision 2017-02-01 15:18 by Florian Dold
Description In the new terminology, the frontend creates an "order", the HTTP PUTs it to the backends /propopsal endpoint, which returns the proposal corresponding to the order (with the merchant signature and missing fields in the order filled out.

With a HTTP GET on /proposal, the frontend can query proposals by transaction ID or proposal hash.

The wallet stores as a "contract" the proposal together with signed coins.