From ee2c32c39d0d73c633db5ccf67afacb392f58a57 Mon Sep 17 00:00:00 2001 From: james Date: Sat, 4 Aug 2018 18:24:32 -0500 Subject: [PATCH] Small change in createTransaction API doc #17 --- docs/index.md | 4 ++-- src/exported-helpers.js | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/index.md b/docs/index.md index 221535c..d33a6b3 100644 --- a/docs/index.md +++ b/docs/index.md @@ -6,7 +6,7 @@ For Transaction as Proof of Stake (TaPOS), 32 bits of a recent block Id is included. Because all transactions use TaPOS, this solves the nothing at stake attack.

This is usually called for every transaction or maybe cached per block. Although - longer caching may be possible, a longer cache time increases the risk of a + longer caching is possible, a longer cache time increases the risk of a transaction replay attack.

processArgs(args, defParams, methodName, [optionsFormatter(extraParam)]) ⇒ processedArgs
@@ -36,7 +36,7 @@ Consult the blockchain and gather information for use in a new signed transactio Because all transactions use TaPOS, this solves the nothing at stake attack. This is usually called for every transaction or maybe cached per block. Although - longer caching may be possible, a longer cache time increases the risk of a + longer caching is possible, a longer cache time increases the risk of a transaction replay attack. **Kind**: global function diff --git a/src/exported-helpers.js b/src/exported-helpers.js index 8777f95..b9f97c7 100644 --- a/src/exported-helpers.js +++ b/src/exported-helpers.js @@ -29,7 +29,7 @@ module.exports = { Because all transactions use TaPOS, this solves the nothing at stake attack. This is usually called for every transaction or maybe cached per block. Although - longer caching may be possible, a longer cache time increases the risk of a + longer caching is possible, a longer cache time increases the risk of a transaction replay attack. @arg {number} expireInSeconds - How many seconds until expiration