From 2c77e05c1304f166916bf86992b3010511b27895 Mon Sep 17 00:00:00 2001 From: Quentin Le Sceller Date: Tue, 16 Jul 2019 17:07:09 +0200 Subject: [PATCH] Fix typo and unecessary word --- api/src/handlers/transactions_api.rs | 4 ++-- doc/coinbase_maturity.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/api/src/handlers/transactions_api.rs b/api/src/handlers/transactions_api.rs index 9d8a827031..878db7f1a2 100644 --- a/api/src/handlers/transactions_api.rs +++ b/api/src/handlers/transactions_api.rs @@ -54,7 +54,7 @@ impl TxHashSetHandler { Ok(TxHashSetNode::get_last_n_output(w(&self.chain)?, distance)) } - // gets last n outputs inserted in to the tree + // gets last n rangeproofs inserted in to the tree fn get_last_n_rangeproof(&self, distance: u64) -> Result, Error> { Ok(TxHashSetNode::get_last_n_rangeproof( w(&self.chain)?, @@ -62,7 +62,7 @@ impl TxHashSetHandler { )) } - // gets last n outputs inserted in to the tree + // gets last n kernels inserted in to the tree fn get_last_n_kernel(&self, distance: u64) -> Result, Error> { Ok(TxHashSetNode::get_last_n_kernel(w(&self.chain)?, distance)) } diff --git a/doc/coinbase_maturity.md b/doc/coinbase_maturity.md index 3b16bc4508..1f3e1c071d 100644 --- a/doc/coinbase_maturity.md +++ b/doc/coinbase_maturity.md @@ -110,7 +110,7 @@ If the hash stored in the output MMR covers both the commitment and the output f With this additional step we know if the output was a coinbase output or a regular transaction output based on the provided features. The hash will not match unless the features in the input match the original output features. -For a regular non-coinbase output we are finished to explain. We know the output is currently spendable and we do not need to check the lock height. +For a regular non-coinbase output we are finished. We know the output is currently spendable and we do not need to check the lock height. For a coinbase output we can proceed to verify the lock height and maturity. For this we need to identify the block where the output originated. We cannot determine the block itself, but we can require the input to specify the block (hash) and we can then prove this is actually correct based on the merkle roots in the block header (without needing full block data).