diff options
| author | Christian Grothoff <christian@grothoff.org> | 2017-09-02 15:25:54 +0200 |
|---|---|---|
| committer | Christian Grothoff <christian@grothoff.org> | 2017-09-02 15:25:54 +0200 |
| commit | 34ceb09fb63518cf86bd6187fafeb4a3df0eb85e (patch) | |
| tree | fbe0deaa1fb7a0faa5ca9a8e11ca4a295b67625d | |
| parent | baff321b2bc9979c02a7d0a02e6440c3ee2403be (diff) | |
| download | merchant-34ceb09fb63518cf86bd6187fafeb4a3df0eb85e.tar.gz merchant-34ceb09fb63518cf86bd6187fafeb4a3df0eb85e.tar.bz2 merchant-34ceb09fb63518cf86bd6187fafeb4a3df0eb85e.zip | |
keep track of issues observed looking at /pay some more
| -rw-r--r-- | TODO | 10 |
1 files changed, 10 insertions, 0 deletions
@@ -0,0 +1,10 @@ +Major issues with /pay: + +1) Why is there a 'paid' field in merchant_contract_terms DB table? + +2) If we do have the row_id of merchant_contract_terms, why do we store + the full h_contract_terms/merchant_pub again and again in the other tables? + +3) What happens if we store in merchant_transactions some timestamp/exchange + and then the deposits (partially) fail? Do we undo the deposits? Do we + allow a 2nd round of /pay? What happens if the exchange differs the 2nd time? |