From ccb7f791304d0bd9ff4938eb1d5b7bc3f7d7f857 Mon Sep 17 00:00:00 2001 From: troymc Date: Fri, 10 Jun 2016 09:52:08 +0200 Subject: [PATCH] Fixed some broken image links in docs --- docs/source/servers/python-server-api-examples.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/source/servers/python-server-api-examples.md b/docs/source/servers/python-server-api-examples.md index 76b80e20..9c2e7593 100644 --- a/docs/source/servers/python-server-api-examples.md +++ b/docs/source/servers/python-server-api-examples.md @@ -128,7 +128,7 @@ 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`.

- +

@@ -380,7 +380,7 @@ 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.

- +

```python @@ -1015,7 +1015,7 @@ 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.

- +

The logic for switching between `execute` and `abort` conditions is conceptually simple: @@ -1032,7 +1032,7 @@ else: The above switch can be implemented as follows using threshold cryptoconditions:

- +

The small circle (⚪) at an input of a threshold condition denotes an inversion of the fulfillment: