Whitepaper

StoneProof: on-chain mineral traceability on Base

This page is a concise summary of the StoneProof protocol design. The full whitepaper goes deeper into our contract suite, fee model, lifecycle guarantees, and how we expose transparent but privacy-preserving telemetry.

Problem space

Mineral supply chains span miners, refiners, transporters, warehouses, traders and regulators. Today this data is siloed, unverifiable, and hard to audit in real time.

StoneProof approach

We model each actor and action as on-chain state on Base, while portals and APIs provide tightly scoped access to that state according to role.

Security & privacy

Event streams favour hashed identifiers and role labels over organization names, while still allowing regulators to prove end-to-end consistency against BaseScan.

Contract suite & state machines

• RolesManagerV2: defines platform and org-scoped roles.
• OrgRegistry: handles organization creation and metadata.
• MembershipManagerV2: maps people/wallets into org roles.
• MineralRegistryV2: tracks mineral IDs, status, and provenance.
• MineralWarehouseV2: storage, listings, and sales lifecycle.
• LogisticsManagerV2: transport requests, assignments, and routes.
• DisputeResolutionV2: disputes, escalation, and resolution states.
• SupplychainValidatorV2: checks that assets are trade-ready.

Protocol fees & costs

• Per-transaction protocol fee: contracts that integrate with the protocol processor (OrgRegistry, MembershipManagerV2, RolesManagerV2, MineralRegistryV2, MineralWarehouseV2, TokenizationV2, LogisticsManagerV2, MineralLicenseManagerV2, DisputeResolutionV2, SupplychainValidatorV2) currently charge a fixed fee of 0.00001 ETH per successful call, in addition to normal gas costs.
• Organization creation: creating a new organization in OrgRegistry goes through the same protocol fee path – today this means a one-time 0.00001 ETH protocol fee plus gas, regardless of the size of the org.
• Role & membership operations: assigning or revoking roles and linking members to organizations also use the protocol processor, so each on-chain update incurs the standard fee.
• Treasury handling: protocol fees are accumulated in the treasury and surfaced to admins via the control-panel protocol-fees dashboard; the whitepaper details how withdrawals are governed, but implementation is controlled by system owners and is not exposed to public UIs.

What the full whitepaper adds on top

• Formal role and permission model for every actor type.
• Detailed state diagrams for minerals, logistics, treasury, and disputes.
• Threat model and mitigations for common attack vectors.
• Indexing and data-access patterns for explorers and regulators.

Want early access to the full document? Share a contact email from the control-panel status page and we’ll reach out.

Loading...

Please wait while we fetch the information...

Preparing your interface