From cab3f8fbd03fca6ec5b0ee4bedf0f305ffb019bf Mon Sep 17 00:00:00 2001 From: Alex Grintsvayg Date: Fri, 9 Nov 2018 17:17:54 -0500 Subject: [PATCH] start the transition to stakes --- index.html | 46 ++++++++++++++++++++++++++++++++-------------- index.md | 47 +++++++++++++++++++++++++++++++++-------------- 2 files changed, 65 insertions(+), 28 deletions(-) diff --git a/index.html b/index.html index bdf87ae..1055538 100644 --- a/index.html +++ b/index.html @@ -90,7 +90,8 @@ * [Assumptions](#assumptions) * [Conventions and Terminology](#conventions-and-terminology) * [Blockchain](#blockchain) - * [Claims](#claims) + * [Stakes](#stakes) + * [Claims](#claims) * [Properties](#claim-properties) * [Example Claim](#example-claim) * [Operations](#claim-operations) @@ -236,11 +237,17 @@ fixme final polish checklist:
metadata
Information about the contents of a stream (e.g. creator, description, stream descriptor hash, etc). Metadata is stored in the blockchain.
-
claim
-
A single metadata entry in the blockchain.
-
name
-
A human-readable UTF8 string that is associated with a published claim.
+
A human-readable UTF8 string that is associated with a stream.
+ +
stake
+
An entry in the blockchain that commits credits toward a name.
+ +
claim
+
A stake that contains metadata about a stream or channel.
+ +
support
+
A stake that lends its credits to bolster an existing claim.
channel
The unit of pseudonymous publisher identity. Claims may be part of a channel.
@@ -261,9 +268,22 @@ fixme final polish checklist:

The LBRY blockchain is a fork of the Bitcoin blockchain, with substantial modifications. This document will not cover or specify any aspects of LBRY that are identical to Bitcoin, and will instead focus on the differences.

-

Claims

+

Stakes

-

A claim is a single entry in the blockchain that stores metadata. There are two types of claims:

+

A stake is a a single entry in the blockchain that commits credits toward a name. The two types of stakes are claims and supports.

+ +

All stakes have these properties:

+ +
+
id
+
A 20-byte hash unique among all stakes. See Stake Identifier Generation.
+
amount
+
A quantity of tokens used to back the stake. See Controlling.
+
+ +

Claims

+ +

A claim is a stake that stores metadata. There are two types of claims:

stream
@@ -274,15 +294,11 @@ fixme final polish checklist:

Properties

-

Claims have four properties:

+

In addition to the properties that all stakes have, claims have two more properties:

-
claim_id
-
A 20-byte hash unique among all claims. See Claim Identifier Generation.
name
A normalized UTF-8 string of up to 255 bytes used to address the claim. See URLs and Normalization.
-
amount
-
A quantity of tokens used to stake the claim. See Controlling.
value
Metadata about a stream or a channel. See Metadata.
@@ -329,9 +345,11 @@ fixme final polish checklist:

Supports

-

A support is an additional transaction type that lends its amount to an existing claim.

+

A support is a stake that lends its amount to an existing claim.

-

A support contains only a claimID and an amount, no other properties. Supports function analogously to claims in terms of Claim Operations and Claim Statuses, with the exception that they cannot be updated or themselves supported.

+

Supports have one extra property on top of the basic stake properties: a claim_id. This is the ID of the claim that the support is bolstering.

+ +

Supports function analogously to claims in terms of Claim Operations and Claim Statuses, with the exception that they cannot be updated or themselves supported.

Claimtrie

diff --git a/index.md b/index.md index 1708343..053f930 100644 --- a/index.md +++ b/index.md @@ -25,7 +25,8 @@ * [Assumptions](#assumptions) * [Conventions and Terminology](#conventions-and-terminology) * [Blockchain](#blockchain) - * [Claims](#claims) + * [Stakes](#stakes) + * [Claims](#claims) * [Properties](#claim-properties) * [Example Claim](#example-claim) * [Operations](#claim-operations) @@ -170,11 +171,17 @@ This document assumes that the reader is familiar with Bitcoin and blockchain te
metadata
Information about the contents of a stream (e.g. creator, description, stream descriptor hash, etc). Metadata is stored in the blockchain.
-
claim
-
A single metadata entry in the blockchain.
-
name
-
A human-readable UTF8 string that is associated with a published claim.
+
A human-readable UTF8 string that is associated with a stream.
+ +
stake
+
An entry in the blockchain that commits credits toward a name.
+ +
claim
+
A stake that contains metadata about a stream or channel.
+ +
support
+
A stake that lends its credits to bolster an existing claim.
channel
The unit of pseudonymous publisher identity. Claims may be part of a channel.
@@ -195,9 +202,23 @@ The LBRY blockchain is a public, proof-of-work blockchain. It serves three key p The LBRY blockchain is a fork of the [Bitcoin](https://bitcoin.org/bitcoin.pdf) blockchain, with substantial modifications. This document will not cover or specify any aspects of LBRY that are identical to Bitcoin, and will instead focus on the differences. -### Claims +### Stakes -A _claim_ is a single entry in the blockchain that stores metadata. There are two types of claims: +A _stake_ is a a single entry in the blockchain that commits credits toward a name. The two types of stakes are [_claims_](#claims) and [_supports_](#supports). + +All stakes have these properties: + +
+
id
+
A 20-byte hash unique among all stakes. See Stake Identifier Generation.
+
amount
+
A quantity of tokens used to back the stake. See Controlling.
+
+ + +#### Claims + +A _claim_ is a stake that stores metadata. There are two types of claims:
stream
@@ -208,15 +229,11 @@ A _claim_ is a single entry in the blockchain that stores metadata. There are tw #### Properties {#claim-properties} -Claims have four properties: +In addition to the properties that all stakes have, claims have two more properties:
-
claim_id
-
A 20-byte hash unique among all claims. See Claim Identifier Generation.
name
A normalized UTF-8 string of up to 255 bytes used to address the claim. See URLs and Normalization.
-
amount
-
A quantity of tokens used to stake the claim. See Controlling.
value
Metadata about a stream or a channel. See Metadata.
@@ -261,9 +278,11 @@ There are three claim operations: _create_, _update_, and _abandon_. #### Supports -A _support_ is an additional transaction type that lends its _amount_ to an existing claim. +A _support_ is a stake that lends its _amount_ to an existing claim. -A support contains only a `claimID` and an `amount`, no other properties. Supports function analogously to claims in terms of [Claim Operations](#claim-operations) and [Claim Statuses](#claim-statuses), with the exception that they cannot be updated or themselves supported. +Supports have one extra property on top of the basic stake properties: a `claim_id`. This is the ID of the claim that the support is bolstering. + +Supports function analogously to claims in terms of [Claim Operations](#claim-operations) and [Claim Statuses](#claim-statuses), with the exception that they cannot be updated or themselves supported. #### Claimtrie