aboutsummaryrefslogtreecommitdiffstats
path: root/site/content
diff options
context:
space:
mode:
authorYigit Sever2021-04-18 21:53:17 +0300
committerYigit Sever2021-04-18 21:53:17 +0300
commit4c855e5bb82cdc470d8dd915121a2e033324d5b1 (patch)
treed8700627e6618079aa8fa9486c9d99fbfd1e0f9a /site/content
parent5f066ada307881e08e61ee9a94a9fc65440bc64f (diff)
downloadgradecoin-4c855e5bb82cdc470d8dd915121a2e033324d5b1.tar.gz
gradecoin-4c855e5bb82cdc470d8dd915121a2e033324d5b1.tar.bz2
gradecoin-4c855e5bb82cdc470d8dd915121a2e033324d5b1.zip
Transaction hashing should be easier
Diffstat (limited to 'site/content')
-rw-r--r--site/content/transaction_docs.md9
1 files changed, 7 insertions, 2 deletions
diff --git a/site/content/transaction_docs.md b/site/content/transaction_docs.md
index 4a6264b..05c1534 100644
--- a/site/content/transaction_docs.md
+++ b/site/content/transaction_docs.md
@@ -26,7 +26,13 @@ timestamp: ISO 8601 <date>T<time>
26 26
27# Hash 27# Hash
28 28
29`tha` field in [jwt documentation](@/JWT.md) in fact stands for "The Hash", in the case of a post request for a transaction, you need the Md5 hash of the serialized JSON representation of transaction. 29`tha` field in [jwt documentation](@/JWT.md) in fact stands for "The Hash", in the case of a post request for a transaction, you need the Md5 hash of the serialized JSON representation of transaction. The resulting JSON string should look something like;
30
31```
32{"by":"foo","source":"bar","target":"baz","amount":2,"timestamp":"2021-04-18T21:49:00"}
33```
34
35Or; without any whitespace, separated with `:` and `,`.
30 36
31# Bank 37# Bank
32 38
@@ -44,4 +50,3 @@ source: this can be either you or the bank
44target: this can be a valid fingerprint or yourself if source is the bank 50target: this can be a valid fingerprint or yourself if source is the bank
45... 51...
46``` 52```
47