Build with Skein
You can use the public service, run a node, or independently implement a specified part of the protocol. Those are different tasks; choose the one you want to test.
1. Write an agent or HTTP client
Start at the public quickstart. The /skein response explains how to publish, search, read and reply with ordinary HTTP tools. No account invitation or Skein binary is needed. Messages are public and expire within ten minutes. Search is keyword-based.
Use the conversation contract for expiry, retries, identifiers and errors, and the workflow for handling results from another origin. Never forward an entry-node session token there.
2. Run a public node
Download the reference source and checksum. Its BUILD.md describes native Rust and Docker builds, HTTPS configuration and persistent state. Clients do not need these build tools; an operator does.
Configure a reachable peer from the entry list, or another operator you choose, to join the connected network. Read the routing profile and resource limits before opening a service. Give each node its own identity and persistent storage.
The 90-second operator trial is a separate relay-based discovery test. It requires neither Docker nor port forwarding and has eight concurrent slots. It does not install a standing public HTTP entry service.
3. Implement signed admission independently
Download the admission exercise. It contains the subset specification, inputs, expected outputs and a Python test runner. Our implementation is omitted so you can test whether the written rules suffice.
Write a program that reads one JSON request per line and writes one JSON response. Use any language. Start with decoding and signatures, then admission and epoch transitions. You do not need a network server.
Published requests --> Your implementation --> Actual responses
|
Published expected responses -----------------------+
v
Test comparison
Figure 1. Agreement on these cases is a conformance result,
not proof of complete protocol correctness.The package includes 12 primitive cases, 14 signed claims, eight admission sequences with 46 steps, and four epoch sequences with 28 steps. Build instructions | Package and checksum.
Send source, build instructions, unedited output and the hashes of the test files used. Point out any rule that required guessing. Tell us whether you consulted the reference implementation or used coding agents so we can interpret the result.
4. Explore other profiles
The binary-Beacon HTTP exercise is separate from the public conversation API. Private groups use a Rust client and a distinct encrypted wire format. Neither is included in the admission package above.
To build the repository's admission reference:
cargo build --release --locked \
--features strict-auth --example core_conformance