From 6a6ade6fba02f234877d74c2ad69a76e3122fa9d Mon Sep 17 00:00:00 2001 From: Mike Date: Fri, 14 Aug 2026 16:12:25 +0300 Subject: [PATCH] docs: name the decoder package @w3tech.io/torpc-decoder Registry status is stated in the implementation repository rather than here. Co-Authored-By: Claude Opus 5 (1M context) --- GOVERNANCE.md | 2 +- README.md | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index f157bd9..fc1b1ad 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -93,7 +93,7 @@ The current normative document is [`specs/evm-v1.md`](./specs/evm-v1.md), at Dra Tiers at or above 3 are reserved. A reserved tier can only be given meaning by a specification release, never by an implementation choosing one unilaterally. -Reference packages, currently `@torpc/decoder` and `@torpc/toevm-rules`, use semantic versioning in their own repository and declare their target specification version in their README and package metadata. +Reference packages, currently `@w3tech.io/torpc-decoder` and `@torpc/toevm-rules`, use semantic versioning in their own repository and declare their target specification version in their README and package metadata. ## TORPC Conformant certification diff --git a/README.md b/README.md index cf3a223..91ffd2d 100644 --- a/README.md +++ b/README.md @@ -143,15 +143,15 @@ LICENSE CC0 1.0 Universal, covering everything above Code lives in [w3tech/torpc-js](https://github.com/w3tech/torpc-js), licensed Apache-2.0: -- **`@torpc/decoder`** (`codec/`), the reference bidirectional mapper between standard EVM +- **`@w3tech.io/torpc-decoder`** (`codec/`), the reference bidirectional mapper between standard EVM JSON-RPC responses and the TORPC compact form. Structural only, no ABI resolution. - **`@torpc/toevm-rules`** (`packages/torpc-toevm-rules/`), the typed ruleset library that names each normative transformation as a pure function. - **`bench/`**, the benchmark harness: token efficiency plus retrieval accuracy over pinned ETH mainnet fixtures. -Those are the in-repository package names. Nothing is published to a public registry yet, so build -from source in that repository. +That repository's README states which of those names are published and which are in-repository +only. Either way the sources build from a checkout. The conformance runner in this repository ships no transform of its own. It validates the golden vectors, and it exercises an implementation only through an adapter you point at one, in any