Record the evidence
An identified operator records a batch, milestone or inspection. Source files remain in private storage.
AMNAYA / BLOCKCHAIN & AI CENTRE
REFERENCE MODEL v0.1 · NO PUBLIC-CHAIN DEPLOYMENTEvidence that travels.
Responsibility that stays.
An Ethereum-based framework for transparency, accountability and provenance, adapted to the decisions that matter in each project.
The public tools below run in your browser. They do not connect a wallet, upload documents, spend gas or create verified project records.
ONE SHARED METHOD
From a claim to a reviewable trail.
Separate the duties
At least two reviewers other than the submitter assess the evidence. Distinct wallets must represent independently appointed people.
Commit on Ethereum
The registry records an evidence commitment, predecessor, actor and lifecycle events. An anchoring time is not an observation time.
Check the whole story
Compare authorized evidence to its commitment, current version, approvals and dispute status. Physical truth still needs inspection.
EIGHT PROJECT PROFILES
One framework.
Different evidence.
Evidence requirements
Proposed reviewer roles
Profiles are planning examples. No appointed partner, live chain of custody, regulatory certification or project accomplishment is asserted.
INTERACTIVE LIFECYCLE / SYNTHETIC RECORD
Try the controls before a pilot.
This simplified demonstration uses a fixed two-reviewer threshold. The execution kit implements project-specific roles, deadlines and onchain evidence commitments. Nothing here is a real blockchain transaction.
LOCAL INTEGRITY CHECK
Same file, same fingerprint?
Choose two local copies to compare their SHA-256 fingerprints. Files stay in this browser. A match confirms identical bytes, not truth, authorship or an Ethereum anchoring.
ETHEREUM ESSENTIALS
A deliberate technology boundary.
Ethereum + Solidity
Executable evidence registry with signature-authenticated transactions and readable events. Local EVM tests are delivered; no network or funded wallet is configured.
OpenZeppelin controls
Default-admin transfer delay, governance roles, project roles and pause controls. Operational permissions are not all timelocked. Production multisig and recovery need review.
Private evidence
Encrypt documents and enforce per-project access offchain. Use random IDs and salted, domain-bound commitments. Public-chain metadata can still reveal relationships.
Measured scaling
Evaluate Ethereum mainnet against an Ethereum-settled L2 after pilot measurements. A private EVM is not automatically secured by Ethereum mainnet.
Human-led AI
Proposed assistants check completeness, sources, anomalies and draft reports. No AI signer, final approval or dispute authority is deployed.
Accountable source data
Device signatures, calibration, sampling and source ownership are required for sensors or oracles. Blockchain cannot repair a false observation.
ILLUSTRATIVE GAS ESTIMATOR
Measure before committing.
Manual assumptions only, not live prices or a provider quote. A basic two-reviewer evidence record uses four transactions: proposal, two reviews and finalization.
Excludes deployment, participant enrollment, handovers, disputes, L2 data/settlement fees, private storage, RPC, integration, independent review, security audit and staff time. No total-cost estimate is implied.
PROJECT PAY-AND-USE
Transparent charges. Responsible use.
Define the paying entity, service scope, usage meter, network costs, spend caps, credits, dispute process and evidence export before paid activation. Eighteen proposed clauses and a project order worksheet cover internal cost allocation and external service use.
Draft guidelines only. No tariff, automatic renewal, payment collection or accepted agreement is activated.
Configure pay-and-use terms →EXECUTION / SEVEN GATES
A bounded first 100 days.
- Days 1–7 · Mandate Select one decision and justify shared verification.
- Days 8–21 · Charter Define participants, sources, schema, permissions, baseline and targets.
- Days 22–42 · Build Implement private evidence adapter, registry, roles and verification flow.
- Days 43–56 · Rehearse Synthetic records, security review, disputes, key recovery and cost tests.
- Days 57–70 · Pilot Use approved real data in a bounded sample; reconcile physical evidence.
- Days 71–84 · Correct Review errors, conflicts, missing data and outage recovery.
- Days 85–100 · Decide Compare evidence and costs; approve, revise, hold or stop.
Suggested pilot targets: zero self-approvals; complete required evidence; at least 95% complete required custody trails; every discovered invalid record flagged; dispute acknowledgment within one business day. Agree denominators, owners and exceptions before adoption.
Open the 100-day planning workbench ↗DELIVERED / NEXT TO IMPLEMENT
Know what is real.
Included now
- Eight editable project profiles and charter export
- Browser-only lifecycle and integrity demonstrations
- Solidity reference contract and commitment helper
- Local EVM lifecycle/control tests and pinned dependencies
- Governance, privacy, recovery and rollout runbook
Before production
- Appoint and verify people; approve project policy and territory/sector controls
- Independent smart-contract/security audit and broader adversarial testing
- Build project-level private evidence access and storage adapters
- Implement wallets, multisig, recovery, indexer and finality/reorg handling
- Approve network, pilot scope and operating spend
The current website vault has team-level access. This framework does not silently extend it to project-level data permissions. No named third-party collaborator is claimed. No token, investment offering, payment or escrow is part of the delivered model.
Primary technical references
Ethereum smart contracts · Oracles · Scaling · OpenZeppelin access control