From ad65115b48c0353bfb0259f7c6ebb3a729a5e12d Mon Sep 17 00:00:00 2001 From: troymc Date: Tue, 1 Nov 2016 13:50:17 +0100 Subject: [PATCH] Fixed three broken links in page about the transaction model --- docs/root/source/data-models/transaction-model.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/root/source/data-models/transaction-model.md b/docs/root/source/data-models/transaction-model.md index 881ab8b4..f8cb5929 100644 --- a/docs/root/source/data-models/transaction-model.md +++ b/docs/root/source/data-models/transaction-model.md @@ -28,11 +28,11 @@ Here's some explanation of the contents of a transaction: - `fulfillments`: List of fulfillments. Each _fulfillment_ contains a pointer to an unspent asset and a _crypto fulfillment_ that satisfies a spending condition set on the unspent asset. A _fulfillment_ is usually a signature proving the ownership of the asset. - See [Conditions and Fulfillments](#conditions-and-fulfillments) below. + See the page about [Crypto-Conditions and Fulfillments](crypto-conditions.html). - `conditions`: List of conditions. Each _condition_ is a _crypto-condition_ that needs to be fulfilled by a transfer transaction in order to transfer ownership to new owners. - See [Conditions and Fulfillments](#conditions-and-fulfillments) below. + See the page about [Crypto-Conditions and Fulfillments](crypto-conditions.html). - `operation`: String representation of the operation being performed (currently either "CREATE", "TRANSFER" or "GENESIS"). It determines how the transaction should be validated. - - `timestamp`: The Unix time when the transaction was created. It's provided by the client. See [the section on timestamps](timestamps.html). + - `timestamp`: The Unix time when the transaction was created. It's provided by the client. See the page about [timestamps in BigchainDB](../timestamps.html). - `asset`: Definition of the digital asset. See next section. - `metadata`: - `id`: UUID version 4 (random) converted to a string of hex digits in standard form.