Why we publish research artefacts in blockchain

Open-source and research aren’t “marketing”. They’re how we make claims testable, attract collaborators, and build the credibility needed for grants and long-horizon partnerships.

Illustration slot
Replace this block with your generated image (e.g. “artefact pipeline”).

Artefacts turn opinions into evidence

In frontier blockchain work, a lot of “insight” is actually a fragile claim: it breaks under adversarial assumptions, production constraints, or new information. Publishing artefacts makes the claim inspectable.

  • Code makes behaviour concrete.
  • Benchmarks make trade-offs measurable.
  • Specs make intent reviewable.
  • Reproducible experiments make results falsifiable.

Open science compounds credibility

The fastest way to lose trust is to sell certainty. The best way to earn trust is to show your work: what you tested, where it fails, and what you still don’t know.

“We publish to be corrected early — before the real world corrects us later.”

It also makes the business stronger

Consulting and partner delivery benefits from the same artefacts: reusable tooling, reference implementations, and internal playbooks that reduce cycle time. Open research is the R&D engine behind applied work.

What we publish

Typical artefacts from a research thread:

  1. Problem statement + threat model
  2. Model or formalisation (when possible)
  3. Prototype implementation
  4. Adversarial tests + performance benchmarks
  5. Write-up with decisions, trade-offs, and next questions
Want to sponsor or partner?

If you’re funding a research direction, co-authoring artefacts, or shipping to production, we’re happy to collaborate.