(01)
Onchain Registry
Record identifiers, evidence hashes, timestamps, signatures, and verification outcomes on ARC.
Evidence hashesTimestampsSignatures
Proof-only infrastructure
ARCWELLON ARC® — Transaction-Proof Infrastructure on ARC
[ Transaction evidence · ARC ]
Verifiable records for real-world transactions. Anchor evidence on ARC, preserve a tamper-evident audit trail, and let independent verifiers check what was submitted.
ARC network, operational
128k+ anchors · 340 organizations
( Scroll )
[02] Approach
Approach — how ARCWELL anchors evidence
Capital-markets tooling wants to execute the transaction. ARCWELL does not. We anchor tamper-evident evidence on ARC, preserve an append-only trail, and let independent verifiers check what was submitted. Submit, anchor, verify, correct.
[ Proof-only ][ Append-only audit ][ Independent verification ]
[03] Operating boundary
Operating boundary — what ARCWELL does and does not do
Proof, not execution
The ARCWELL product boundary
"We record what external systemsreport, we do not executethe transaction."
01 / Anchor
Hashes, timestamps, and submitter signatures anchored on ARC.
02 / Verify
Independent verifiers review evidence and flag discrepancies.
03 / Correct
Corrections append to the record, nothing is silently rewritten.
[04] Record explorer
Record series
Anchored on ARC
[05] Network activity
We do not move assets.We move evidence into the open.
Anchors submitted on ARC
Records verified
Organizations anchoring
Verifier accuracy
Anchored on ARC
Every record carries an evidence hash, timestamp, and submitter signature.
Independently verified
Verifiers compare evidence and flag discrepancies for structured review.
Append-only history
Corrections extend the trail, original entries are never rewritten.
[06] Capabilities
Six layers ofproof infrastructure.
Every layer records and verifies, none of them execute the transaction.
01 / 06
(02)
Evidence Storage
Permissioned source files with content-addressed references, retention rules, and access logs.
Content-addressedRetentionAccess logs
(03)
Organization Portal
Submit records, package evidence, set visibility policies, track status, and file corrections.
SubmissionVisibilityCorrections
(04)
Public Explorer
Searchable record metadata, provenance, timestamps, and verification history, with clear source labels.
SearchProvenanceSource labels
(05)
Verifier Workspace
Evidence comparison, structured findings, challenge submission, reputation, and appeal history.
FindingsChallengesReputation
(06)
Data Services
Read-only APIs, webhooks, and exportable audit reports with full source attribution.
Read-only APIWebhooksAudit exports
[07] Process
From submitted recordto anchored proof.
- Anchor confirmation
- ~4 s
- History
- Append-only
- Verifier rewards
- Objective rules
( 01 )
Submit record
An authorized organization submits a transaction record with its external reference and event type.
( 02 )
Package evidence
Supporting documents are bundled, content-addressed, and linked to the record with signatures.
( 03 )
Anchor on ARC
The evidence hash, timestamp, and submitter signature are anchored on ARC, tamper-evident from that moment.
( 04 )
Verify independently
Verifiers compare disclosed evidence, file structured findings, and flag discrepancies.
( 05 )
Correct transparently
Corrections append to the record with their own anchor. The original entry is never rewritten.
01, 05
[08] Data model
What ARCWELL records
Six entities, one job: turn transaction evidence into tamper-evident onchain records that authorized parties can verify. Nothing else is issued, traded, or settled here.
- 01
OrganizationProfile
Who submits. A registered organization with a verified signing identity and a public profile on the explorer.
orgIdsigningKeys[]visibilityDefault - 02
RecordSeries
How records are grouped. An append-only stream of related transaction records under one visibility policy.
seriesIdanchorPolicyretentionClass - 03
ParticipantReference
Who is referenced. Privacy-preserving pointers to counterparties, never personal data on chain.
participantRefroleCodeconsentFlag - 04
TransactionRecord
What happened. A structured description of an off-chain event, hashed and anchored on ARC.
evidenceHasheventTimestampchainAnchor - 05
ValidationResult
What verifiers found. Independent confirmations and discrepancies, each signed and time-stamped.
verifierIdfindingquorumWeight - 06
EvidenceBundle
What backs it. The documents, signatures, and timestamps a reviewer can inspect against the anchor.
bundleUridocumentCountretention
See the entities working end to end.
The dashboard walks every entity with live sample records, verifier findings, and correction trails.
Proof infrastructure only. ARCWELL does not execute, broker, custody, or settle transactions.
[09] Validation notes
Validation notes — what operators verify
ARCWELL gave our reporting a single tamper-evident trail, every record we submit is anchored on ARC and independently checkable.
Reporting operations
Helix dataset, submitting organization
98.6%
Verifier accuracy
~4 s
Anchor confirmation
0
Silent edits, ever
"Discrepancy flags arrive with evidence attached, review takes minutes, not weeks."
Compliance desk
Terra record set
"The correction trail reads like a ledger: append-only, timestamped, complete."
Operations team
Northbound series
"The read-only API plugged straight into our existing audit reporting."
Data team
Atlas workspace
[10] FAQ
Proof, explained.
The boundary questions, up front. Anything else is a message away.
Still curious? Reach the team directly.
An anchor proves that specified data was submitted at a given time and has not been altered since. It does not by itself prove the underlying transaction was lawful, valid, authorized, or correctly classified.
