gaspersic/solana
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Book: Drop since-fixed nonce known issue (#7789)

Browse Source 
automerge
This commit is contained in:
Trent Nelson
2020-01-14 11:13:09 -07:00
committed by Grimes
parent 699ca5fec1
commit 564cd4e09d
1 changed files with 0 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
book/src/offline-signing/durable-nonce.md
View File

@ -5,32 +5,6 @@ short lifetime of a transaction's [`recent_blockhash`](../transaction.md#recent-
They are implemented as a Solana Program, the mechanics of which can be read
about in the [proposal](../implemented-proposals/durable-tx-nonces.md).
## Known Issues
### Fee Theft Opportunity
The durable nonce implementation contains a vulernability which allows for fees
to be stolen by a transaction using the feature under certain conditions. If the
transaction fails with an instruction error, the runtime rolls back the step
that advanced the stored nonce, allowing it to be replayed and fees charged.
This can be repeated until the stored nonce is successfully advanced.
- Mitigation
To minimize loss of funds, use a low-balance account to pay fees on a durable
nonce transaction.
If a transaction using the durable nonce feature fails with an instruction error,
immediately submit a new transaction that advances the nonce and will certainly
succeed. The simplest way to do this is with a single-instruction
`NonceInstruction::Nonce` transaction, which can be sent using the CLI
[`new-nonce`](#advancing-the-stored-nonce-value) command.
- Issue Tracking
This issue is being actively addressed, progress can be followed on
[Github](https://github.com/solana-labs/solana/issues/7443).
## Usage Examples
Full usage details for durable nonce CLI commands can be found in the