Skip to content

Commit

Permalink
collation on-demand
Browse files Browse the repository at this point in the history
  • Loading branch information
DrW3RK committed Apr 17, 2024
1 parent 7bcb4cb commit b0cbb7b
Show file tree
Hide file tree
Showing 4 changed files with 16 additions and 0 deletions.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
16 changes: 16 additions & 0 deletions docs/learn/learn-guides-coretime-parachains.md
Original file line number Diff line number Diff line change
Expand Up @@ -101,3 +101,19 @@ sync with the specified relaychain.
./target/release/adder-collator --parachain-id= $ParaID --chain=rococo --sync fast-unsafe
```

After the collator node is fully synced with the relay chain, navigate to Developer > Extrinsics and
issue `onDemandAssignmentProvider.placeOrderAllowDeath` extrinsic from the account that registered
the `ParaID` by specifying sufficient `maxAmount`for the transaction to go through successfully.

![coretime-ondemand-assignment](../assets/coretime/coretime-on-demand-assignment.png)

With each successful on-demand extrinsic, the parachain head changes (you may have to zoom out on
the browser for parachain head details to show up on Polkadot-JS UI).

![coretime-ondemand-parahead](../assets/coretime/coretime-on-demand-parahead.png)

The successful collation can also be verified in the logs of the parachain collator. It can be
noticed that with each parachain block, the state of `adder-collator` is incremented by `2`.

![coretime-new-collation](../assets/coretime/coretime-create-new-collation.png)

0 comments on commit b0cbb7b

Please sign in to comment.