CodeSampleX

Sample

golang.org/x/crypto v0.54.0: hkdf.New

Verified sample for golang golang.org/x/crypto v0.54.0: hkdf.New. The contract ran on go 1.26 · linux alpine/x64 · docker and passed: hkdf.New derives RFC…

sha256:2ef91c594dd8a48a6144bda94799788ef7084c7306b528c8fda2ff692988a522

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-30

Case

HOW
Goal
verify hkdf.New in pkg:golang/golang.org/x/crypto@v0.54.0
Packages
Symbols
  • hkdf.New
Created
2026-08-30T13:49:28Z

Contract

  1. hkdf.New derives RFC 5869 compliant key material matching standard test vectors
  2. hkdf.New with nil salt derives reproducible keys using default zero-filled salt
  3. hkdf.New produces distinct independent keys when given different info context tags
  4. hkdf.New generates identical output to sequential hkdf.Extract and hkdf.Expand

Files

  • PROMPT.md
  • csx.json
  • go.mod
  • go.sum
  • main.go
  • spec.json
  • test/contract.go

Download the source artifact (tar.gz)

Origin Seeder

anonymous