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

Switch to recent_block_hash

Browse Source
This commit is contained in:
Michael Vines
2019-03-02 10:02:19 -08:00
committed by Greg Fitzgerald
parent ce1b72809a
commit 95cbb8a5c0
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
book/src/drones.md
View File

@ -46,7 +46,7 @@ desired cluster.
## Attack vectors ## Attack vectors
### Invalid last_id ### Invalid recent_block_hash
The drone may prefer its airdrops only target a particular Solana cluster. To The drone may prefer its airdrops only target a particular Solana cluster. To
do that, it listens to the cluster for new entry IDs and ensure any requests do that, it listens to the cluster for new entry IDs and ensure any requests
@ -68,8 +68,8 @@ A client may request multiple airdrops before the first has been submitted to
the ledger. The client may do this maliciously or simply because it thinks the the ledger. The client may do this maliciously or simply because it thinks the
first request was dropped. The drone should not simply query the cluster to first request was dropped. The drone should not simply query the cluster to
ensure the client has not already received an airdrop. Instead, it should use ensure the client has not already received an airdrop. Instead, it should use
`last_id` to ensure the previous request is expired before signing another. `recent_block_hash` to ensure the previous request is expired before signing another.
Note that the Solana cluster will reject any transaction with a `last_id` Note that the Solana cluster will reject any transaction with a `recent_block_hash`
beyond a certain *age*. beyond a certain *age*.
### Denial of Service ### Denial of Service