docs: align remaining behavior references - #995
Closed
grayfoxd wants to merge 13 commits into
Closed
Conversation
…vm-extension docs: align v4.13 transaction safety guidance
`evm:1` / `evm:11155111` / `evm:56` / `evm:97` were added as compatibility aliases alongside TRON's, but they protect nobody: the EVM networks were never part of a published release. `develop`'s builtins carry no `evm:` id at all, and 4.10.1 through 4.12.0 shipped TRON alone — no config.yaml or script can be holding one of those spellings. An alias is a promise to resolve something forever and it shows up in `config aliases`, so an entry nobody could have written is only clutter. The TRON ids stay: they did ship, and people's files hold them. tokens.json's rename map keeps its EVM rows deliberately. The two surfaces fail differently — an unresolvable id in config.yaml is an error the user reads and fixes, while an unmatched scope key silently yields an empty token list. Four lines is a cheap hedge against someone on a branch build losing their token book. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Vw3cw2uPxtDMZScdkmQpFx
Documentation-only pass over ts/docs, java/docs and both READMEs, reconciling every documented behaviour, error code, field type and terminal transcript against the current code. No source file changes. Behaviour and contract: - asset issue: local validation limited to what the service checks; chain-side bounds attributed to the node (transaction_rejected) - asset info/issue: ICO rate reported as the reduced trxNum/num pair - contract create2 keeps a chain block; deploy documents per-family contractAddress derivation (EVM nonce vs TRON prepared txID) - gasfree renamed to TIP-712; provider_error / provider_rate_limited scoped to what each adapter actually raises - tx info: EVM not_found is exit 2, TRON rpc_error exit 1 - machine-interface: migration_required moved to the exit-2 table, token_metadata_unavailable marked as crossing exit codes, usage_error narrowed to parser failures - secret handling: prompts documented as an interactive-command allowlist; signing commands never prompt Transcripts recomputed from the render layer (kv/table widths, row order, Block "#" prefix, relative-time suffixes, blank lines), and example data made self-consistent (txids, block numbers, pagination totals, per-seed EVM addresses). Java side: wallet selector tables, resource/stake-v2 outputs that are plain text rather than JSON, prompt wording, TxId casing, and examples that could not execute as written (votewitness placeholders, quoted method signatures, GetBlockByLimitNext arguments). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The remote branch was rebuilt as a single squashed commit (896361e) off 765bc2e, so it lacked the ten commits this branch already had. All 28 conflicting files resolved in favour of this branch: the remote side of every one of them was byte-identical to 4db02a4, i.e. the content this branch already contained before the documentation pass. Both sides are preserved. The five source files the squash omitted (governance auth mode, --build-only wording, auth_required text) and the two PRD working documents stay as they are on this branch; the remote contributed no content this branch was missing. Two merge artefacts fixed: a duplicated EVM example block in tx/sign.md, and a reverted (TRON only) tag in guide/scripting.md. Co-Authored-By: Claude Opus 5 (1M context) <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
3 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.