[01] Operating model, ARCWELL on ARC
We record what externalsystems report , we do not executethe transaction.
ARCWELL turns transaction evidence into tamper-evident onchain records that authorized parties can verify. Anchor evidence on ARC, preserve an append-only audit trail, and let independent verifiers check what was submitted.
Anchors submitted on ARC
Records verified independently
Submitting organizations
Median confirmation time
Verifier accuracy (trailing 90 days)
ARCWELL is software for recording, anchoring, and verifying evidence of transactions that occurred through systems operated by other parties. The underlying transaction always happens somewhere else, our job is the proof trail, never the event itself.
What an ARC entry proves
An ARC entry proves specified data was submitted at a given time and has not been altered; it does not by itself prove the underlying transaction was lawful, valid, authorized, complete, or correctly classified.
Every screen, API field, and reward rule in ARCWELL is checked against this list. If a capability is not in the left column, it is out of scope, deliberately.
ARCWELL does
- Anchor transaction hashes and timestamps on ARC.
- Link records to supporting documents and source references.
- Preserve an append-only audit and correction history.
- Let authorized users submit and attest to records.
- Let verifiers review evidence and flag discrepancies.
- Provide read-only APIs and a public record explorer.
- Surface third-party rule or screening results with source and time.
- Reward objectively valid data-quality work, subject to separate review.
ARCWELL does not
- Create or issue securities; offer, promote, or sell securities; match buyers and sellers.
- Transfer ownership of an underlying instrument; hold customer assets or act as custodian.
- Route investment payments or perform delivery-versus-payment settlement.
- Certify Reg D, Reg S, Reg CF, accreditation, sanctions, KYC approval, or legal compliance.
- Provide investment advice or guarantee transaction validity.
Capital-markets vocabulary implies capabilities ARCWELL does not have. Across product, API, and documentation, legacy terms are replaced with language that describes exactly what the software does , recordkeeping and verification support, nothing more.
Each layer is independently deployable and independently auditable. Read paths are public where policy allows; write paths require authorization.
Onchain registry
Record identifiers, evidence hashes, timestamps, submitter signatures, correction links, verification outcomes.
Evidence storage
Encrypted or permissioned source files, content-addressed references, retention rules, access logs.
Organization portal
Record submission, evidence packaging, visibility controls, status tracking, corrections.
Public explorer
Searchable record metadata, provenance, timestamps, verification history, clear source labels.
Verifier workspace
Evidence comparison, structured findings, challenge submission, reputation, appeal history.
Data services
Read-only API, webhooks, exportable audit reports, source attribution, monitoring.
Reward system
Objective eligibility rules, anti-collusion controls, transparent reward calculations, separate legal review.
How we think about proof.
Five principles that hold whether a series has ten records or ten thousand.
01, Proof, not trust
Every claim in the explorer links to an anchored artifact, a hash, a timestamp, a signature. If it cannot be pointed to, it is not stated.
02, Append-only by default
Corrections are added to the record, never written over it. The original entry and every amendment stay visible, linked, and timestamped.
03, Source on every field
Each data point carries attribution, which system reported it, when, and under whose signature. Unattributed data does not ship.
04, Independent verification
Verifiers are structurally separate from submitting organizations, with reputation, challenge, and appeal history in the open.
05, Bounded by design
ARCWELL records what external systems report. Validity, legality, and classification of the underlying event remain with the parties and their advisers.
ARCWELL governance covers the protocol, the verifier network, and the reward system. It never touches the legality, validity, or classification of an underlying transaction, those questions belong to the parties involved and their own advisers.
Protocol rules
Anchor formats, hash schemes, and correction-link semantics are versioned and published. Changes ship with notice and migration notes.
Verifier rules
Eligibility, structured-finding formats, challenge windows, and appeal paths are objective and public. Reputation is earned on the record.
Reward rules
Reward calculations are transparent and tied to objectively valid data-quality work, subject to anti-collusion controls and separate review.
( Proof-only infrastructure )
See the operating model in practice.
Browse anchored RecordSeries in the public explorer, or bring your own records to a verification pilot.