chore: pc20-documentation - #1233
Open
mohammeds1992 wants to merge 7 commits into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
mohammeds1992
requested review from
HarshRajat and
riyanshu-patro
and removed request for
HarshRajat
August 3, 2026 12:33
Contributor
|
…flows Add 26 new tool permissions covering git operations (fetch, checkout, worktree, commit, push), GitHub CLI (auth, API, PR creation), browser automation (chrome MCP), Notion fetch, and diagnostic commands used in recent lfpush refresh work. Also clarify PC20 funds.token docs: emphasize PC20 tokens are Push Chain-native, note funds are external-origin only, and remove redundant export example.
…lution docs Add Token Types section to Important Concepts explaining PRC20 (foreign tokens mirrored inward) vs PC20 (Push-native tokens mirrored outward). Update Address Book to clarify PRC20s are Push Chain representations of external tokens, note PC20 wrappers live in on-chain registry, and link to new concept section. Expand Recommended Practices with token movement guidance: resolve decimals instead of hardcoding, name the
… with $UNICORN Replace fragmented PC20 import/export examples that required manual pre-funding and wrapper address lookups with complete round-trip scripts. New flows mint $UNICORN (from the ERC-20 tutorial) on Push Chain, export it to Sepolia, wait for settlement, then burn the wrapper back home—all in one execution. Key changes: remove hardcoded `rain` token and wrapper addresses, add mint step with public mint() ABI, capture wrapper address from export receipt instead of hardcoding, add settlement polling loop, consolid
Move PC20 funds documentation into dedicated subsections under "Moving PRC-20 Tokens" and "Moving PC-20 Tokens". Add link to new Token Types concept section. Simplify parameter descriptions, remove verbose route coverage and error-handling tables, and clarify that `funds.chain` indicates where the token currently sits (not destination). Add anchor for parameter reference linking.
…mentation Replace inconsistent "PC20" and "PRC20" with hyphenated "PC-20" and "PRC-20" throughout docs, utility functions, examples, and changelog. Update table headers, function names, code comments, and inline references to match the hyphenated style established in the Important Concepts section.
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
2 participants
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.
No description provided.