diff --git a/docs/source/_static/cc_escrow_execute_abort.png b/docs/source/_static/cc_escrow_execute_abort.png index 2d4a98e1..54800943 100644 Binary files a/docs/source/_static/cc_escrow_execute_abort.png and b/docs/source/_static/cc_escrow_execute_abort.png differ diff --git a/docs/source/python-server-api-examples.md b/docs/source/python-server-api-examples.md index 36f9716b..d2534bb2 100644 --- a/docs/source/python-server-api-examples.md +++ b/docs/source/python-server-api-examples.md @@ -129,7 +129,9 @@ The locking script is refered to as a `condition` and a corresponding `fulfillme Since a transaction can have multiple outputs with each its own (crypto)condition, each transaction input should also refer to the condition index `cid`. -![BigchainDB transactions connecting fulfillments with conditions](./_static/tx_single_condition_single_fulfillment_v1.png) +

+ +

```python @@ -379,7 +381,9 @@ With BigchainDB it is possible to send multiple assets to someone in a single tr The transaction will create a `fulfillment` - `condition` pair for each input, which can be refered to by `fid` and `cid` respectively. -![BigchainDB transactions connecting multiple fulfillments with multiple conditions](./_static/tx_multi_condition_multi_fulfillment_v1.png) +

+ +

```python # Create some assets for bulk transfer @@ -1011,7 +1015,9 @@ BigchainDB and cryptoconditions provides escrow out-of-the-box, without the need A threshold condition is used to represent the escrow, since BigchainDB transactions cannot have a _pending_ state. -![BigchainDB escrow conditions and fulfillments](./_static/tx_escrow_execute_abort.png) +

+ +

The logic for switching between `execute` and `abort` conditions is conceptually simple: @@ -1026,7 +1032,9 @@ else: The above switch can be implemented as follows using threshold cryptoconditions: -![Cryptoconditions escrow conditions and fulfillments](./_static/cc_escrow_execute_abort.png) +

+ +

The small circle on the threshold conditions denotes an inversion of the fulfillment: