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

Use integer, not string for block index in chainHead_follow events #84

Merged
merged 1 commit into from
Sep 12, 2023
Merged

Use integer, not string for block index in chainHead_follow events #84

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 4 additions & 4 deletions src/api/transaction_unstable_submitAndWatch.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ If multiple `broadcasted` events happen in a row, the JSON-RPC server is allowed
"event": "bestChainBlockIncluded",
"block": {
"hash": "...",
"index": "..."
"index": ...
}
}
```
Expand All @@ -87,7 +87,7 @@ The `bestChainBlockIncluded` event indicates which block of the best chain the t

`null` can be sent back in case the block is no longer in any block of the best chain. This is the state a transaction starts in.

`hash` is a string containing the hexadecimal-encoded hash of the header of the block. `index` is a string containing an integer indicating the 0-based index of this transaction within the body of this block.
`hash` is a string containing the hexadecimal-encoded hash of the header of the block. `index` is an integer indicating the 0-based index of this transaction within the body of this block.

If multiple `bestChainBlockIncluded` events happen in a row, the JSON-RPC server is allowed to skip all but the last.

Expand All @@ -100,14 +100,14 @@ If multiple `bestChainBlockIncluded` events happen in a row, the JSON-RPC server
"event": "finalized",
"block": {
"hash": "...",
"index": "..."
"index": ...
}
}
```

The `finalized` event indicates that this transaction is present in a block of the chain that is finalized.

`hash` is a string containing the hexadecimal-encoded hash of the header of the block. `index` is a string containing an integer indicating the 0-based index of this transaction within the body of this block.
`hash` is a string containing the hexadecimal-encoded hash of the header of the block. `index` is an integer indicating the 0-based index of this transaction within the body of this block.

No more event will be generated about this transaction.

Expand Down