external
account
GET /accounts/{pubkey}/next-nonce
Changed onGet an account's next nonce; This is computed according to whatever is the current account nonce and what transactions are currently present in the transaction pool
Request
- Base URL/v2 (relative, and the document was published on a file host, not at the API’s origin)
- URL/v2/accounts/{pubkey}/next-nonce
- Authnone declared
Path parameters
pubkeystring required
The public key of the account
Query parameters
strategy'max' | 'continuity'
What strategy to use in order to determine the next nonce: shall it check for continuity or return the largest nonce seen + 1. If you choose strategy max, then the greatest nonce seen in the account or currently in the transaction pool is incremented with 1 and returned. If you choose the strategy continuity, then transactions in the mempool are checked if there are gaps - missing nonces that prevent transactions with greater nonces to get included.
Response
Successful operation
Changes
- info
added the non-success response with the status
- info
- info
endpoint added
- info