HCS20 Inscription API [Awaiting Documentation]#50
Merged
mattsmithies merged 2 commits intomasterfrom Jan 7, 2024
Merged
Conversation
…ansferring with validations on API level
Collaborator
Author
|
Will complete documentation before merge. |
|
This is absolutely amazing, great work! |
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
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.
Overview
This is the the first pass of a HCS20 compliant API which unlocked inscriptions for anyone building on Hedera.
This comprises of updated postman documentation for 4 new endpoints:
On mainnet the topic id for inscriptions will default to 0.0.4350190
API will validate payloads but will not validate if it is a proper HCS20 chain/sequence.
Testnet Output
You can see the output of these function on this topic.
https://hashscan.io/testnet/topic/0.0.7459744?p=1&k=1704558987.547089003
Validation Compared with Standard
The HCS20 standard describes shorthand fields that are inline with BRC20
https://patches-1.gitbook.io/hcs-20-auditable-points/standard-details
Within the API we have opted for more human-readable validation, but the messages issued to HCS are in the valid format as requested.
API Response
You receive your topic id, tx, and inscription payload.
Look at the postman file for documentation
Routes
The breakdown are as follows:
Deploy
Mint
Burn
Transfer