Document reading on-chain events via the Platform API#37
Open
EtayM wants to merge 1 commit into
Open
Conversation
Events shipped on the v3 API: Transaction now exposes an extrinsic
object (id, hash, success, signer, block, events) instead of the
removed extrinsicHash field.
- Rewrite Working with Events: replace the coming-soon callout and
Subscan workflow with the GetTransaction -> extrinsic.events flow,
Event field reference, and a verified create-collection example.
- Update GetTransaction/GetTransactions/GetBlock/GetExtrinsic
reference: extrinsic { hash } selections, events sub-fields, drop
the three outage warnings (verified fixed), Block.validator is now
a plain hex string, GetBlocks requires ids or hashes.
- Swap stale extrinsicHash selections in getting-started and
mutation examples for extrinsic { hash }.
- WebSocket Events page: point the interim workflow at the API
events flow instead of Subscan (streaming itself still planned).
All shapes and payloads verified against the live canary network.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Events are now readable on the v3 API through the
Transaction.extrinsicobject (which replaced the removed extrinsicHash field). Rewrites Working with Events around the GetTransaction → extrinsic.events flow with live-verified examples, replacing the Subscan workaround. Also fixes the now-brokenextrinsicHashselections across getting-started/reference snippets, and removes the stale GetBlock/GetExtrinsic outage warnings (verified fixed). WebSocket streaming is still unshipped — that page stays "coming soon", now pointing at the API flow in the interim.