Mirroristas/bigchaindb
2
0
Fork 0
mirror of https://github.com/bigchaindb/bigchaindb.git synced 2024-10-13 13:34:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

PR review docs

Browse Source
This commit is contained in:
diminator 2016-08-17 15:44:32 +02:00
parent 7df49b068a
commit afc661d360
No known key found for this signature in database
GPG Key ID: C3D8590E6D0D439A
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/source/drivers-clients/http-client-server-api.rst
View File

@ -199,16 +199,16 @@ The HTTP API currently exposes two endpoints, one to get information about a spe
**Disclaimer**
``CREATE`` transactions are treated differently from ``TRANSFER`` assets.
The reason is that a ``CREATE`` transaction needs to be signed by the federation nodes and not by the client.
The reason is that a ``CREATE`` transaction needs to be signed by a federation node and not by the client.
The following python snippet at the client can be used to generate ``CREATE`` transactions before they can be pushed to the API server:
The following python snippet in a client can be used to generate ``CREATE`` transactions before they can be pushed to the API server:
.. code-block:: python
from bigchaindb import util
tx = util.create_and_sign_tx(my_privkey, my_pubkey, my_pubkey, None, 'CREATE')
When POSTing ``tx`` to the API, the ``CREATE`` transaction will be signed by the federation nodes.
When POSTing ``tx`` to the API, the ``CREATE`` transaction will be signed by a federation node.
A ``TRANSFER`` transaction, that takes an existing input transaction to change ownership can be generated in multiple ways: