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

change messy code

Browse Source
This commit is contained in:
utarl 2017-01-04 10:11:00 +08:00
parent 96432ce0be
commit 4de0bb4c8c
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/server/source/data-models/inputs-outputs.rst
View File

@ -7,7 +7,7 @@ Amounts of an asset are encoded in the outputs of a transaction, and each output
.. note::
This document (and various places in the BigchainDB documentation and code) talks about control of an asset in terms of *owners* and *ownership*. The language is chosen to represent the most common use cases, but in some more complex scenarios, it may not be accurate to say that the output is owned by the controllers of those public keys鈥搃t would only be correct to say that those public keys are associated with the ability to fulfill the output. Also, depending on the use case, the entity controlling an output via a private key may not be the legal owner of the asset in the corresponding legal domain. However, since we aim to use language that is simple to understand and covers the majority of use cases, we talk in terms of *owners* of an output that have the ability to *spend* that output.
This document (and various places in the BigchainDB documentation and code) talks about control of an asset in terms of *owners* and *ownership*. The language is chosen to represent the most common use cases, but in some more complex scenarios, it may not be accurate to say that the output is owned by the controllers of those public keys-it would only be correct to say that those public keys are associated with the ability to fulfill the output. Also, depending on the use case, the entity controlling an output via a private key may not be the legal owner of the asset in the corresponding legal domain. However, since we aim to use language that is simple to understand and covers the majority of use cases, we talk in terms of *owners* of an output that have the ability to *spend* that output.
In the most basic case, an output may define a **simple signature condition**, which gives control of the output to the entity controlling a corresponding private key.
@ -24,7 +24,7 @@ The (single) output of a threshold condition can be used as one of the inputs of
When one creates a condition, one can calculate its fulfillment length (e.g. 96). The more complex the condition, the larger its fulfillment length will be. A BigchainDB federation can put an upper limit on the allowed fulfillment length, as a way of capping the complexity of conditions (and the computing time required to validate them).
If someone tries to make a condition where the output of a threshold condition feeds into the input of another 鈥渆arlier鈥<EFBFBD> threshold condition (i.e. in a closed logical circuit), then their computer will take forever to calculate the (infinite) 鈥渃ondition URI鈥<49>, at least in theory. In practice, their computer will run out of memory or their client software will timeout after a while.
If someone tries to make a condition where the output of a threshold condition feeds into the input of another "earlier" threshold condition (i.e. in a closed logical circuit), then their computer will take forever to calculate the (infinite) "condition URI", at least in theory. In practice, their computer will run out of memory or their client software will timeout after a while.
Outputs
-------