From 3c17db41dcf6b7261661e5b96e1ce68c9a3ed0a1 Mon Sep 17 00:00:00 2001 From: Justin Starry Date: Fri, 24 Jan 2020 10:50:25 +0800 Subject: [PATCH] Add note to book about drone throughput limitations (#7953) automerge --- book/src/programs/drones.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/book/src/programs/drones.md b/book/src/programs/drones.md index 40a1fee3af..941d6f2015 100644 --- a/book/src/programs/drones.md +++ b/book/src/programs/drones.md @@ -16,6 +16,8 @@ Creator of on-chain game tic-tac-toe hosts a drone that responds to airdrop requ Creator of a new on-chain token \(ERC-20 interface\), may wish to do a worldwide airdrop to distribute its tokens to millions of users over just a few seconds. That drone cannot spend resources interacting with the Solana cluster. Instead, the drone should only verify the client is unique and human, and then return the signature. It may also want to listen to the Solana cluster for recent entry IDs to support client retries and to ensure the airdrop is targeting the desired cluster. +Note: the Solana cluster will not parallelize transactions funded by the same fee-paying account. This means that the max throughput of a single fee-paying account is limited to the number of _ticks_ processed per second by the current leader. Add additional fee-paying accounts to improve throughput. + ## Attack vectors ### Invalid recent\_blockhash