Skip to content
This repository has been archived by the owner on Dec 15, 2023. It is now read-only.

Commit

Permalink
Fix blocks-on-demand docs [skip ci]
Browse files Browse the repository at this point in the history
  • Loading branch information
@FabijanC
FabijanC committed Jul 4, 2023
1 parent 5b66058 commit 3da399e
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion page/docs/guide/blocks.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,8 @@ Response:

### Create a block on demand

If you start Devnet with `--blocks-on-demand` CLI option, all transactions will be pending and stored in a pending block (targetable via block ID `"pending"`).
If you start Devnet with the `--blocks-on-demand` CLI option, all valid transactions will be stored in a pending block (targetable via block ID `"pending"`). Since Devnet v0.5.5, the status of these transactions is no longer pending, but accepted. The status of the block is pending.

To create a block on demand, send a `POST` request to `/create_block`. This will convert the pending block to the latest block (targetable via block ID `"latest"`), giving it a block hash and a block number. All subsequent transactions will be stored to a new pending block.

In case of demanding block creation with no pending transactions, a new empty block will be generated.
Expand Down

0 comments on commit 3da399e

Please sign in to comment.