From 5f0ecd63c4e9aa34341e872a15a745220fb1076a Mon Sep 17 00:00:00 2001 From: satyakwok Date: Wed, 13 May 2026 20:29:42 +0200 Subject: [PATCH] docs(readme): fix two stale claims (published box + explorer dep) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 1. Roadmap "Publish to crates.io once stabilises" was unchecked, but v0.1.0-alpha.0 is on crates.io since 2026-05-12 (verified via `crates.io/api/v1/crates/sentrix-grpc-wasm/versions`). Ticked the box + linked the crate. 2. Status said "used in production by sentrix-explorer-v2". Verified explorer-v2's Cargo.toml: no `sentrix-grpc-wasm` dep — explorer-v2 depends on `sentrix-proto` directly, same as this crate does. They are SIBLING consumers of sentrix-proto, not parent/child. Reframed to capture the actual lineage: grpc-wasm was born inside explorer-v2 then extracted as a reusable wrapper. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 542c455..7a02d99 100644 --- a/README.md +++ b/README.md @@ -66,12 +66,12 @@ Older chain hosts (v0.2 / v0.3) return `Status::unimplemented` for the newer met - [x] Standalone crate with `tonic-build` codegen - [x] CI: `cargo build` + `cargo build --target wasm32-unknown-unknown` - [ ] Smoke test: `wasm-pack test --headless --chrome` against staging endpoint -- [ ] Publish to crates.io once API surface stabilises +- [x] Published to crates.io ([`sentrix-grpc-wasm`](https://crates.io/crates/sentrix-grpc-wasm)) — v0.1.0-alpha.0 since 2026-05-12 - [ ] Optional: pre-built WASM artifact npm package (skip the local `wasm-pack` step for JS consumers) ## Status -`v0.1.0-alpha.0` — works, used in production by [`sentrix-explorer-v2`](https://github.com/Sentriscloud/sentrix-explorer-v2). Surface is the same as the explorer was using; nothing here is speculative. +`v0.1.0-alpha.0` on crates.io. Born as the gRPC-Web wrapper inside [`sentrix-explorer-v2`](https://github.com/Sentriscloud/sentrix-explorer-v2); now extracted as a sibling crate that any browser dApp can pull as a thin client over [`sentrix-proto`](https://crates.io/crates/sentrix-proto) without re-implementing the `tonic-web-wasm-client` glue. (explorer-v2 itself depends on `sentrix-proto` directly, not on this crate — they're siblings, not parent/child.) ## License