What is a contributor?
In b1e55ed, a contributor is the attribution unit: a human operator or an automated agent process that submits signals or otherwise influences decisions. Roles:operator— a human running the engine and injecting discretionary signalsagent— an automated process submitting signals/feedbacktester— validation, QA, and regression contributorscurator— a signal curator (may be distinct from the operator role)
Contributor registration ties activity to a stable
node_id, enabling:- signal attribution (
POST /api/v1/signals/submit) - contributor scoring and leaderboard
- provenance/oracle projections
Identity model (two identities)
b1e55ed uses two identities:-
Local node identity (Ed25519)
- stored at
~/.b1e55ed/identity.key - used by the engine security layer
- stored at
-
Forged Ethereum identity (“The Forge”)
- stored at
~/.b1e55ed/identity.json - used for Ethereum-facing integrations (EAS) and network identity
- stored at
Register via CLI
List contributors
Register (minimal)
Register with explicit node id
Register + create an EAS off-chain attestation (optional)
CLI flags
Remove a contributor
Register via API
POST /contributors/register
Optional: GitHub auto-publish
When configured, b1e55ed will open a GitHub issue in a designated repo when a contributor is registered. This creates a public record without requiring on-chain transactions. Configure inconfig/user.yaml:
If the token is empty, publishing is silently skipped (WARN only) and registration still succeeds.
Optional: EAS attestations (--attest)
If EAS is enabled, b1e55ed can create an off-chain attestation during registration and store:
metadata.eas.uidmetadata.eas.attestation