Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add line about Primitive transaction hashes #42

Merged
merged 2 commits into from
May 17, 2024
Merged

Add line about Primitive transaction hashes #42

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d706dcf
Add line about Primitive transaction hashes
SpaceManiac May 17, 2024
5ccc52b
Tweak wording to read better
SpaceManiac May 17, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/home/300-react-to-events/2-primitive-catalogue/1-introduction.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,8 @@ The data collected and functions used to access it are specific to each type of

Scheduled inputs are triggered by events specific to each extension type, with the circumstances and the format of the scheduled input described in their respective sections. The inputs are always scheduled either for the current blockheight (which enables them to be processed immediately, as scheduled inputs are processed before the state transition function is called), or, if they are triggered before the overall `START_BLOCKHEIGHT` of the game node (specified in the `.env` file), in the so-called _pre-sync_ phase, they are scheduled for `START_BLOCKHEIGHT + 1` (which is the first blockheight for which the state transition function is called). The scheduled inputs will always start with the prefix specified in the config as `scheduledPrefix`.

The [state transition function](../../200-read-write-L2-state/10-read-data.md#stf-function) call triggered by a scheduled input originating from a Primitive can access the original transaction hash using `inputData.scheduledTxHash`.

To learn by example, please consult the NFT LvlUp game template – `./paima-engine-linux init template nft-lvlup` to learn more.

## Relation to funnels
Expand Down
Loading