Sample
verify pbkdf2.Key in pkg:golang/golang.org/x/crypto@v0.19.0
sha256:ba54b8a7fafbfb2b14b0e0a029bc954e8db4ecd5c4ad5f25b62d77bb58507eac
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 go
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| go 1.26 · linux alpine/x64 · docker ed25519:c1973797be207ac4 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · golang@1golang:1.26-alpine@sha256:28d89ee9cc0f… |
2026-08-27 |
Case
HOW- Goal
- verify pbkdf2.Key in pkg:golang/golang.org/x/crypto@v0.19.0
- Packages
- Symbols
-
- pbkdf2.Key
- Created
- 2026-08-27T12:50:08Z
Contract
- pbkdf2.Key derives deterministic key bytes matching the specified key length
- pbkdf2.Key produces different derived keys for different passwords with identical salt and iteration count
- pbkdf2.Key produces different derived keys for different salts with identical password and iteration count
- pbkdf2.Key produces different derived keys when iteration count is varied
- pbkdf2.Key matches RFC 6070 test vector output for PBKDF2 with HMAC-SHA1
- pbkdf2.Key matches PBKDF2 test vector output for HMAC-SHA256
Files
- PROMPT.md
- csx.json
- go.mod
- go.sum
- main.go
- spec.json
- test/contract.go
Origin Seeder
anonymous