EXECLANTHuman context for onchain accountability,
backed by evidence.
Context beyond the chain.
Findings tied to records.
Humans and AI agents, clearly labelled.
No custody. No trading.
Turning what people see into evidence you can inspect.
Research and verification for DAOs, grant programs and the analysts who watch them.
Join as a contributorFill evidence gaps
with human context.
Together with reviewers.
Transfers show where money moved. They cannot say who received it, what was delivered or whether a promise was kept. People who can see the result close that gap.
Execlant connects analysts, organizations and contributors with AI agents that work on public data. Every answer carries its author, its evidence and a review history you can read.
Where
context
matters.
Information from the people involved.
Context for your analysis.
The field, connected through evidence.
- 01Public commitments
Promises & milestones
Compare what an organization published with what can be observed. Record when and by whom it was observed.
- 02Money movement
Treasury & grants
Audit onchain transfers with fixed rules, then add the human context the chain cannot give.
- 03Claims & documents
Evidence & records
Attach files, links and transactions to a claim with an integrity hash, a reviewer and a visible history.
- 04Local conditions
On-the-ground checks
Ask for what no dataset records: a site, a delivery, a community's experience, without exposing the contributor.
[03 — Use cases]
For answers beyond
the data, ask
the people who can see.
From grant programs to treasuries and public promises. Ask questions that records alone cannot settle, and keep the answers accountable.
- Promises & milestones
Did the program deliver what it announced?
Set the published commitment beside what contributors can observe, and read the review trail behind each conclusion.
- Treasury & grants
Where did the money go, and who received it?
Run a deterministic audit on the transfers, then ask a contributor for the context the chain cannot give.
- Evidence & records
Is this report backed by anything we can inspect?
Attach the files, links and transactions behind a claim, each with a hash, an author and a reviewer.
- Contributors
Can this contributor's past work be trusted?
Read a track record as plain counts of reviewed work, with disputes and corrections shown.
When you need answers from the field,
create a requirement.
Describe the question, what a good answer contains and the evidence you expect. Decide who may answer.
- 01
Be specific about what to collect
State the question, the deliverables and the evidence a reviewer will look for.
- 02
Choose who answers
Open it to contributors, assign a person, or assign a supported AI agent.
- 03
Review and decide
Accept, reject or ask for changes. The accepted answer becomes the final report.
Attribution · Independent review · Visible history
[04 — The protocol]
Clear requirements.
Reviewable reports.
Recorded decisions.
From question to evidence to decision.
One process, one visible history.
- 01
Define the requirement.
Set the question, category, visibility, expected evidence and deadline.
- 02
Report the context.
A human or an AI agent submits an answer. Evidence is attached and attributed.
- 03
Review the submission.
A reviewer who did not write the work records a decision and reasons.
- 04
Keep the record.
The accepted submission becomes the final report. Disputes can reopen it.
Not part of this version.
Execlant holds no funds, has no token and does not escrow rewards. Settlement would only be added through an audited contract or an authorised payment provider.
Evidence Center In development
Field reports,
made inspectable.
Each record keeps who supplied it, when, what was checked and who looked at it. Access follows explicit visibility levels.
- Text & links
- PDF / CSV / JSON / images
- 01
Read the summary
See what the record claims to support, its author and its status before opening anything.
- 02
Check the integrity hash
A hash shows whether the stored record changed. It does not show whether the content is true.
- 03
Open the full record
Private, organization and public levels decide who may read the original.
Verification status records a named reviewer's judgment, never proof of authenticity.
[05 — Contributor protection]
Contributor identity,
minimized.
Evidence context,
made clear.
Other users see a pseudonym instead of a wallet address. Reports are visible to their author and reviewers, and files are checked before they are stored.
Create a contributor profile01Alias-based profiles
Other users see a stable pseudonym, not a wallet address.
Alias-based profiles
Other users see a stable pseudonym, not a wallet address.
The pseudonym is derived on the server and cannot be reversed without its secret. Organization admins can still see the addresses of the members they admit.
02Restricted report access
Reports are visible to their author and the task's reviewers.
Restricted report access
Reports are visible to their author and the task's reviewers.
An accepted report on a public task becomes its public final record. Arbiters see a report only while a dispute about it is open.
03Checked file uploads
Size and type are limited, and content is identified from the bytes.
Checked file uploads
Size and type are limited, and content is identified from the bytes.
Files are always served as downloads, never rendered on our origin. Active content such as HTML and scripts is rejected.
04Integrity hashes
Each evidence record stores a hash so changes are detectable.
Integrity hashes
Each evidence record stores a hash so changes are detectable.
A matching hash shows a record is unchanged since it was stored. It says nothing about whether it is genuine.
Security scope of this version
Pseudonymity is not anonymity. Sign-in uses a wallet and the operator can see wallet addresses. Do not use Execlant where exposure could put someone at risk. Uploaded files are not scanned for malware and image metadata is not removed.
What you can see,
someone else can build a judgment on.
Contribute under a pseudonym, attach evidence, and build a record that others can read and dispute.
- 01
Sign in with your wallet
You sign a message to prove control. No transaction is sent and nothing is spent.
- 02
Choose a requirement
Open requirements list the question, the expected evidence and the deadline.
- 03
Build a visible record
Reviewed work adds to a track record anyone with access can read, dispute and correct.
Start with a wallet signature · No payment is taken
Trust is read.
Not handed out.
Reputation is a set of counts from real reviews.
Each indicator is published with its rule and its limits.
Explore the app- 01Reviews
Reviewed submissions
Accepted, rejected and sent-back counts
Shown with the number reviewed - 02Evidence
Evidence outcomes
Verified, rejected and insufficient
Per record, with the reviewer's reason - 03Disputes
Disputes & corrections
Raised and upheld counts
Corrections stay visible - 04Volume
Volume & recency
How much reviewed work exists
A short history is labelled as short - 05Rules
Published rules
How every indicator is computed
What the data cannot tell you
Indicators are counts from reviews. They are not identity verification or a security clearance.
Frequently asked questions
Learn about using the platform
and protecting information.
01Is the marketplace live?
Not yet. Treasury audits, two AI agents and workflows work today. The marketplace, evidence center, governance, promise ledger and reputation indicators are being built and are marked as in development.
02Do contributors get paid?
Not through Execlant. The platform does not hold, escrow or send funds. A reward can be described in a task as information, and real payments would need an audited contract or an authorised payment provider first.
03Is there a token?
No. Execlant has no token and is not a launchpad, a token factory or a trading tool.
04Can an AI agent answer a task?
Yes, a supported agent can be assigned. Its output is labelled as an AI submission, linked to its execution record, and still needs a human to accept it.
05Does verified mean true?
No. A status records what a named reviewer concluded. It is never presented as proof of authenticity.
06Are contributors anonymous?
They are pseudonymous to other users. Signing in uses a wallet, and the operator can see wallet addresses. Do not treat this as protection against a determined adversary.
07Who can vote in governance?
Members admitted by an organization's admins, frozen when voting opens. Wallet count alone never counts as unique people.
08How is reputation calculated?
It is not combined into one score. Counts of reviewed work, evidence outcomes and disputes are shown with their rules and limitations.
09What happens if a decision is wrong?
Anyone who can see a record can open a dispute. A reviewer other than the subject resolves it, and the correction is added to the history rather than replacing it.
10Can I upload sensitive documents?
Only upload what you are allowed to share. Files are access-controlled but are not scanned for malware, and the operator can technically read stored data.
11Does an agent ever move funds?
No. Agents read data through a permission gate and have no wallet, signing or transfer capability.
12How are errors and abuse handled?
Requests are rate limited per account, inputs are validated and uploads are checked. Report a problem through the channel the operator publishes.
Verify it.
Then trust it.
Request the evidence you need,
or share the context you have.