1.9 KiB
ledger_accept
The ledger_accept method forces the server to close the current-working ledger and move to the next ledger number. This method is intended for testing purposes only, and is only available when the rippled server is running stand-alone mode.
The ledger_accept method is an admin method that cannot be run by unprivileged users!
Request Format
An example of the request format:
WebSocket
{
"id": "Accept my ledger!",
"command": "ledger_accept"
}
Commandline
#Syntax: ledger_accept
rippled ledger_accept
The request accepts no parameters.
Response Format
An example of a successful response:
{
"id": "Accept my ledger!",
"status": "success",
"type": "response",
"result": {
"ledger_current_index": 6643240
}
}
The response follows the [standard format][], with a successful result containing the following field:
Field |
Type | Description |
|---|---|---|
ledger_current_index |
Unsigned Integer - [Ledger Index][] | Ledger index of the newly created 'current' ledger |
Note: When you close a ledger, rippled determines the canonical order of transactions in that ledger and replays them. This can change the outcome of transactions that were provisionally applied to the current ledger.
Possible Errors
- Any of the [universal error types][].
notStandAlone- If therippledserver is not currently running in stand-alone mode.
{% include '_snippets/rippled-api-links.md' %} {% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %}