zzstoatzz.io / atproto-bench
this repo has no description
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

docs: label Rust as rsky stack, not RustCrypto

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

zzstoatzz b73280f5 a4f54f2f

+2 -2
+2 -2
README.md
··· 238 238 |-----|----------:|----------:|---------:|------------:|-------------:|--------:| 239 239 | zig ([zat](https://tangled.sh/@zzstoatzz.io/zat)) | 81.6ms | 0.6ms | 45.5ms | 172.6ms | 300.4ms | 9.8s | 240 240 | go ([indigo](https://github.com/bluesky-social/indigo)) | 403.8ms | 0.4ms | 5.8ms | 0.0ms | 410.0ms | 20.8s | 241 - | rust (RustCrypto) | 301.0ms | 0.2ms | 120.9ms | N/A | 422.1ms | 8.7s | 241 + | rust ([rsky](https://github.com/blacksky-algorithms/rsky) stack) | 301.0ms | 0.2ms | 120.9ms | N/A | 422.1ms | 8.7s | 242 242 243 - the rust verify implementation is hand-rolled using the same low-level RustCrypto crates that rsky uses internally (k256, p256, serde_ipld_dagcbor, sha2) but not rsky's higher-level abstractions (rsky-repo, rsky-identity, rsky-crypto). no Rust equivalent of indigo's all-in-one `LoadRepoFromCAR` exists yet — [rsky](https://github.com/blacksky-algorithms/rsky) provides the library crates (MST, CAR, identity, crypto) but the end-to-end verify pipeline is assembled manually. [jacquard](https://tangled.sh/@nonbinary.computer/jacquard) also has MST/CAR/identity support and could serve as the basis for a higher-level verify path. 243 + the rust verify uses the same low-level crates that [rsky](https://github.com/blacksky-algorithms/rsky) (Rudy Fraser / BlackSky) uses internally (k256, p256, serde_ipld_dagcbor, sha2) but not rsky's higher-level abstractions (rsky-repo, rsky-identity, rsky-crypto). no Rust equivalent of indigo's all-in-one `LoadRepoFromCAR` exists yet — rsky provides the library crates (MST, CAR, identity, crypto) but the end-to-end verify pipeline is assembled manually. [jacquard](https://tangled.sh/@nonbinary.computer/jacquard) also has MST/CAR/identity support and could serve as the basis for a higher-level verify path. 244 244 245 245 compute time is dominated by CAR parsing (SHA-256 verification of 243k blocks) and MST operations. signature verification is sub-millisecond for all three — single ECDSA verify is trivial compared to the bulk data work. 246 246