Your wallet signs
NEAR Connect hands the transaction to the wallet. TRIPLEES does not hold a NEAR private key or sign on the user’s behalf.
BUILT FOR ENVIRONMENTAL ACCOUNTABILITY / NEAR INTEGRATED
Make every environmental claim traceable.
TRIPLEES turns project documents, registry records and monitoring observations into reviewable investigations. NEAR adds a public integrity layer for approved reports — without publishing private evidence.
01 / THE PRINCIPLEEvidence stays inspectable. Decisions stay human. Report integrity becomes independently checkable.
TRIPLEES / NETWORK MODELFIG. 001
01Source evidence
02Human review
03NEAR commitment
04Public verification
ON-CHAIN RECORDDIGEST ONLY
01 — WHAT IT ISEnvironmental evidence intelligence
02 — WHAT NEAR DOESPublicly verifiable report integrity
03 — WHAT STAYS HUMANReview, judgment and approval
THE VERIFICATION LAYERNEAR PROTOCOL ↗02 / 05
WHY NEAR IS PART OF TRIPLEES
A report can be checked beyond the system that created it.
After a reviewer approves a report, TRIPLEES calculates a canonical SHA-256 digest. The reviewer’s NEAR wallet signs a call to the TRIPLEES registry contract. The contract records the report version and digest so the same report can be checked later by anyone with the original file.
See how the flow worksReviewer permission
The registry accepts commitments only from accounts granted reviewer permission by the contract owner.
Verify the exact file
The public verifier recalculates the report digest and compares it with the saved commitment and contract state.
NEAR TESTNET INTEGRATIONContract deployment and reviewer permissions are configuration gates; the software does not claim a live commitment until chain verification succeeds.
03 / THE PLATFORM
FROM EVIDENCE TO EXPLAINABLE REVIEW
One workspace for the story behind the claim.
TRIPLEES connects the records, analytical work and human decisions that sit behind an environmental project report.
MAP / 2026
▤
Evidence library
Upload documents, fingerprint files and extract supported PDF, CSV, JSON and text content with page, row or field references.
SOURCE RECORDS⌘
Investigation agents
Five bounded analytical roles organize evidence, research, integrity checks, monitoring signals and independent review.
ASSISTIVE ANALYSIS◎
Registry comparisons
Compare supplied registry rows and highlight potential overlaps, serial conflicts and inconsistencies for inspection.
SCOPED CHECKS⌁
Monitoring review
Keep observation source, time, severity, status and uncertainty visible. Imported and synthetic signals stay clearly labelled.
SOURCE-AWARE SIGNALS✓
Human review
Authorized reviewers inspect findings, record decisions with reasons and create immutable report versions.
HUMAN AUTHORITYN
NEAR report registry
Commit approved report digests to NEAR testnet, then expose a public check for the exact report file.
ON-CHAIN INTEGRITY04 / THE WORKFLOW
From a source file
to a public proof.
NEAR enters only after evidence has been examined and a human reviewer approves the report version.
Collect
Project records, uploaded evidence, imported registry data and monitoring observations.
OFF-CHAIN / PRIVATE WORKSPACEInvestigate
Agents organize claims and sources. Deterministic checks and model suggestions remain distinguishable.
ANALYSIS / ADVISORYApprove
A reviewer checks the finding trail and approves a specific version with a recorded reason.
HUMAN DECISIONCommit on NEAR
The connected wallet signs. The registry stores the digest and minimal version identifiers.
NEAR TESTNET / DIGEST ONLYVerify
Anyone can hash the downloaded report and compare it with the public contract record.
PUBLIC INTEGRITY CHECK05 / THE TRUST BOUNDARY
Keep private data private.
Put proof where it can be checked.
STAYS IN TRIPLEESOFF-CHAIN
Evidence and analysis
- Original documents and uploaded evidence
- Personal and project-sensitive information
- Agent outputs, citations and reviewer reasons
- Full report content and supporting context
SHA-256→
RECORDED ON NEARON-CHAIN
Integrity commitment
- Investigation identifier and report version
- Canonical report digest
- Submitting NEAR account
- Contract timestamp and optional metadata digest
A matching digest means the supplied bytes match the committed report version. It does not prove that the report is accurate, that an environmental outcome occurred, or that a carbon credit is certified.
WHAT MAKES TRIPLEES DIFFERENT
Not a token marketplace.
An evidence-to-verification workflow.
Many blockchain climate products center their experience on issuing, trading or retiring digital assets. TRIPLEES focuses on the quality and traceability of the records behind a claim. NEAR is used as a verifiable integrity layer after a human review — not as a source of environmental truth.
01Evidence first, token mechanics second — no token sale, carbon token or marketplace is required for the core workflow.
02Digest-only anchoring — private files and full reports are not placed on the public chain.
03Human-approved commitments — agents cannot approve a report or sign a transaction.
04Independent verification — the public check compares the original report bytes with the committed digest.
QUESTIONS / ANSWERS
Know what the record means.
TRIPLEES is designed to make its limits as visible as its capabilities.
Explore the workspace ↗Why does TRIPLEES use NEAR?＋
NEAR provides the public contract layer for approved report-digest commitments. A wallet signs the transaction, the registry records a versioned digest, and the public verifier can check the report later.
Does NEAR store the evidence files?＋
No. Original evidence, report contents, private context and reviewer reasons stay off-chain. The contract stores a digest and minimal identifiers needed to verify report integrity.
Does a verified digest mean a climate claim is true?＋
No. It proves only that the supplied report bytes match the digest recorded for that version. Source quality, methodology, environmental outcomes and credit eligibility still require independent assessment.
Is the NEAR wallet the same as my TRIPLEES login?＋
No. The application session controls access to the workspace. The NEAR wallet is connected separately and is used by an authorized reviewer to sign a report commitment.
Is the NEAR registry live right now?＋
The repository includes the NEAR testnet integration and wallet flow, but a contract ID, deployment and reviewer permission must be configured before real commitments can be submitted. The interface should show the configured state rather than imply a live deployment.
Does this replace X1 EcoChain?＋
No. NEAR report commitments and the existing X1 workflows are separate integrations with separate configuration and contract paths. The NEAR product experience does not silently replace or disable X1.
TRIPLEES / INVESTIGATE. VERIFY. TRACE.
Start with the evidence.
Finish with a verifiable record.
Explore the workspace using sample data, then connect a NEAR testnet wallet when the registry is configured.