Sample
compute CRC32 checksum for strings and buffers using crc-32
sha256:87b90caeeaec71c7c6a8217f509f874ef902f909d3cdff3cc76073993d850b54
This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 1
- Signing keys that built it
- 1
Declared environment
linux 24 · ubuntu · glibc 2.39 x64 npm
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:c1973797be207ac4 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1node:22-alpine@sha256:c610fcdfb1d5… |
2026-08-28 |
Case
HOW- Goal
- compute CRC32 checksum for strings and buffers using crc-32
- Packages
- Symbols
-
- CRC32.bstr
- CRC32.buf
- CRC32.str
- Created
- 2026-08-28T08:13:17Z
Contract
- CRC32.str(str) computes 32-bit signed integer CRC-32 checksum for ASCII and UTF-8 strings
- CRC32.str('') returns 0 for empty string input
- CRC32.buf(buf) computes CRC-32 checksum for Buffer and Uint8Array byte sequences
- CRC32.bstr(binaryStr) computes CRC-32 checksum for 8-bit binary strings matching buffer CRC
- CRC32.str(part2, seed) and CRC32.buf(part2, seed) support incremental CRC-32 chaining with seed
Files
- PROMPT.md
- csx.json
- index.mjs
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous