Software prototype / Working prototype

Merkle Commitments with Poseidon in Rust

A collaborative Rust and arkworks work-in-progress prototype for Poseidon commitments, Merkle roots and membership paths.

Status
Paused
Evidence basis
Supporting artifacts
Started
2026-05
Context
Exploratory cryptographic engineering and learning work using arkworks.

Role

Collaborative contributor

A collaborator wrote the initial core implementation. My later work covers selected Poseidon, tree and proof updates, examples and documentation. The repository history records those later changes; it does not make me the sole author of the prototype.

Collaboration: Project collaborator: initial core implementation

Simplified Merkle membership structure
Simplified structure for explanation only. It is not an audited circuit diagram.

Scope

The prototype explores how Poseidon-based leaf commitments can be arranged into a Merkle tree and checked through membership paths in Rust using arkworks components.

Contribution

A collaborator wrote the initial core. My later contributions covered selected Poseidon, tree and proof components, examples and documentation. I do not claim sole authorship of the prototype.

Evidence

The public repository contains the prototype and its documented limitations. Its history records selected updates to Poseidon, membership proofs and tree construction, plus later documentation changes.

These are records of changes to a collaborative prototype, not evidence of sole authorship or a security audit. The project-record JSON is a portable copy of this description.

Current boundary

A native threshold check is not a zero-knowledge threshold proof. Moving from the current prototype to that claim requires a real circuit, constraints, tests, parameter review and independent security scrutiny.

Claim boundary

What this does not establish

  • The current threshold check is native rather than zero knowledge.
  • Parameters are demonstrative rather than production cryptographic parameters.
  • The prototype is unaudited and must not be treated as production cryptography.
  • The repository and commit history provide inspectable records, not an independent security or authorship audit.