From 4c855e5bb82cdc470d8dd915121a2e033324d5b1 Mon Sep 17 00:00:00 2001 From: Yigit Sever Date: Sun, 18 Apr 2021 21:53:17 +0300 Subject: Transaction hashing should be easier --- site/public/transaction-docs/index.html | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'site/public/transaction-docs/index.html') diff --git a/site/public/transaction-docs/index.html b/site/public/transaction-docs/index.html index 4f8ef9c..593bcfe 100644 --- a/site/public/transaction-docs/index.html +++ b/site/public/transaction-docs/index.html @@ -126,7 +126,11 @@ target: Fingerprint amount: unsigned 16 bit integer timestamp: ISO 8601 <date>T<time>

Hash

-

tha field in jwt documentation 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.

+

tha field in jwt documentation 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;

+
+{"by":"foo","source":"bar","target":"baz","amount":2,"timestamp":"2021-04-18T21:49:00"}
+
+

Or; without any whitespace, separated with : and ,.

Bank

There is a bank account with Fingerprint 31415926535897932384626433832795028841971693993751058209749445923

-- cgit v1.2.3-70-g09d2