docs(near): add NEAR chain page, changelog stream, and intents-flows guide - #431
Open
shahan-khatchadourian-anchorage wants to merge 1 commit into
Conversation
shahan-khatchadourian-anchorage
changed the title
shahan-khatchadourian-anchorage
force-pushed
the
shahankhatchadourian/near-c-docs
branch
from
July 31, 2026 10:48
7b543f0 to
244a62e
Compare
…guide Adds the docs.json-wired pages for NEAR: - docs/chains/near.mdx: mirrors chains/tron.mdx's structure -- the two input formats under one CHAIN_NEAR identity, the intent-type table, signature standards, visualization strategy, and parser_cli examples for both a transaction and an intents envelope. - docs/changelog/near.mdx: a new changelog stream (page shell only, no fabricated release version -- the actual <Update> block is added by a maintainer at curation time per the existing drafts workflow). changelog.mdx's stream index and docs/changelog/_drafts/README.md's category list gain a near entry. - docs/changelog/_drafts/2026-07-30-near-chain-launch.md: the draft fragment for this migration's own user-facing change. - docs/wallet-integration/dapps/near-intents.mdx: the three flows a NEAR Intents user signs -- deposit and withdraw (ordinary NEAR transactions) and the pre-signature intent envelope in between -- with real, parser_cli-verified request/response examples for each, plus the shared envelope format and implicit-account model. Framed for wallet integrators rather than third-party dApp authors, since NEAR Intents is a single fixed protocol this parser already fully decodes, unlike Ethereum's arbitrary-contract ecosystem. - docs/wallet-integration/core-concepts/how-parsing-works.mdx: NEAR added to the chain-agnostic input-format table. All parser_cli output in these pages was generated and copied from real runs, not hand-typed. make -C docs broken-links passes with the same 7 pre-existing rss.xml false positives every existing chain page already has (dynamically-generated feeds the local checker can't resolve), zero new broken links. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
shahan-khatchadourian-anchorage
force-pushed
the
shahankhatchadourian/near-c-docs
branch
from
July 31, 2026 10:53
244a62e to
d7f238b
Compare
shahan-khatchadourian-anchorage
marked this pull request as ready for review
July 31, 2026 10:58
Copilot started reviewing on behalf of
shahan-khatchadourian-anchorage
July 31, 2026 10:59
View session
Contributor
There was a problem hiding this comment.
Pull request overview
Adds NEAR documentation to the Mintlify docs site (visualsign.dev) to complete the NEAR-consolidation stack, covering NEAR chain decoding, NEAR Intents signing flows, and a dedicated NEAR changelog stream aligned with the existing draft-fragment workflow.
Changes:
- Introduces a new NEAR chain page describing input formats, intent types, signature standards, and
parser_cliusage. - Adds a NEAR Intents flows guide for wallet/dApp integrations with real
parser_cli-verified examples. - Adds a NEAR changelog stream (index + stream page) and a corresponding draft changelog fragment/category wiring.
Reviewed changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| docs/wallet-integration/dapps/near-intents.mdx | New guide describing the three NEAR Intents user-signing flows with example inputs/outputs. |
| docs/wallet-integration/core-concepts/how-parsing-works.mdx | Adds NEAR to the input-format/encoding overview table. |
| docs/docs.json | Adds NEAR pages to navigation (dApps section, Chains section, Changelog streams). |
| docs/changelog/near.mdx | New NEAR changelog stream shell with RSS link and tag filter line. |
| docs/changelog/_drafts/README.md | Updates the draft workflow docs to include the new near category and stream page. |
| docs/changelog/_drafts/2026-07-30-near-chain-launch.md | Draft fragment announcing NEAR chain + NEAR Intents preset support. |
| docs/changelog.mdx | Adds NEAR to the changelog stream index cards. |
| docs/chains/near.mdx | New NEAR chain documentation page (formats, intent table, standards, visualization strategy, CLI examples). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| description: NEAR transactions and NEAR Intents (Defuse Protocol) signing | ||
| --- | ||
|
|
||
| The NEAR module decodes raw NEAR transactions into VisualSign payloads, and renders both halves of the [NEAR Intents](https://docs.near-intents.org) protocol: the pre-signature intent a user is about to sign, and the signed batch a `execute_intents` call submits on-chain. |
|
|
||
| NEAR carries two distinct payload shapes under a single `CHAIN_NEAR` identity, discriminated purely by input format: | ||
|
|
||
| - **A borsh-encoded transaction** (`near::sign_transaction`) — the standard NEAR wire format (`near-primitives::Transaction`, signed or unsigned), hex or base64 encoded. |
| | Solana | Serialized transaction | Base64 | | ||
| | Sui | BCS-encoded transaction | Base64 | | ||
| | Tron | Protobuf-encoded transaction | Hex | | ||
| | NEAR | Borsh-encoded transaction, or a pre-signature intents envelope (JSON) | Hex/base64, or raw JSON | |
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.
Sixth and final PR of the NEAR-consolidation stack (stacked on #430). Documents NEAR on the docs site (visualsign.dev), completing the migration.
Stack: A1 (#425) -> A2 (#426) -> A3 (#428) -> A4 (#429) -> B (#430) -> C (this).
What this PR does
docs/chains/near.mdx: mirrorschains/tron.mdx's structure -- the two input formats under oneCHAIN_NEARidentity, the intent-type table, signature standards, visualization strategy, andparser_cliexamples for both a transaction and an intents envelope.docs/changelog/near.mdx: a new changelog stream. Page shell only (frontmatter, subscribe/filter line) with no<Update>block -- this repo's changelog is curated at release time from draft fragments (docs/changelog/_drafts/README.md), so a PR author doesn't fabricate a release version.changelog.mdx's stream index and the drafts README's category list both gain anearentry.docs/changelog/_drafts/2026-07-30-near-chain-launch.md: the draft fragment for this migration's own user-facing change, per that workflow.docs/wallet-integration/dapps/near-intents.mdx: the three flows a NEAR Intents user signs -- deposit and withdraw (ordinary NEAR transactions) and the pre-signature intent envelope in between -- with real,parser_cli-verified request/response examples for each, the shared envelope format, and the implicit-account model.docs/wallet-integration/core-concepts/how-parsing-works.mdx: NEAR added to the chain-agnostic input-format table.Verification
parser_clioutput shown in these pages was generated by an actual run and copied verbatim (not hand-typed or reformatted) -- including the exact--output jsonkey ordering and theFallbackTextfield on every entry.make -C docs broken-linkspasses with the same 7 pre-existingrss.xmlfalse positives every existing chain/blog page already has (Mintlify-hosted feeds the local checker can't resolve) -- zero new broken links or anchors.visualsign-nearsource (the intent-type table field-by-field againstrender.rs, the signature-standard list againststandard_name(), the format-discrimination description againsttx.rs) and caught two inaccuracies before this PR was opened: theadd_public_key/remove_public_keytable row used the wrong field label, and the deposit example's JSON blocks didn't match the real serialization shape (missingFallbackText, wrong key order) -- both fixed with real, re-verified output.