Reviewing task entries

Entries is the log of every task completion on your projects. Nothing in it waits for your decision: the platform credits completions, and what you do here is read, search and spot-check.

📷 Screenshot placeholder — Entries, All projects, with the Count and Points cards above the table.

What an entry is

An entry is one task completion that has already been credited: this farmer earned these points for that task at that time. It is written in the same transaction as the points, so there is never an entry without points or points without an entry.

That order matters. The artefact of an approval queue — completions waiting for you, an approve button, a rejection the farmer reads — is not how the product works. By the time a completion reaches Entries, the farmer already has the points.

Why there is no approve step

Each verification mode settles the completion before the entry exists:

Auto (API) — the platform checked the provider (a Telegram join, a Discord join, an X follow) and credited only on a pass. A failed check produces no entry.
Self-attest — the farmer pasted a link, the platform checked its shape and credited straight away. The link is stored on the entry.
Manual review — the farmer submitted and was credited straight away. Nothing was captured, and nothing was held.
Custom (app signup) — your own endpoint was asked whether the farmer is an active user, over a window of up to 48 hours. The entry appears only once it said yes; a submission that expired or failed never becomes an entry.

Platform tasks — the ones the platform team publishes above your own — are credited the same way and appear in your log when a farmer completes one in your project.

What the page shows

The page opens on All projects; pick one project to narrow it. Two cards summarise the scope: Count (completions) and Points (the points they awarded in total). Below them, the table lists entries newest first, with the farmer, the task, its kind, the points and the time.

Search matches the task title, the task kind, the farmer's email or their wallet address.
The Live task / Deleted task filter separates entries whose task still exists from those whose task has since been removed. Your own tasks are never deleted — only deactivated — so a Deleted task entry belongs to a platform task the platform team removed. The entry keeps the task's title and kind from the time of completion.
Page size is 10, 20 or 50.

Open an entry for its detail: points awarded, task kind, whether the task is live or deleted, the project and its chain, the completion time, the farmer's wallet (with a copy button) and, for a self-attest entry, the proof of completion link.

📷 Screenshot placeholder — an entry's detail view showing the Proof of completion link.

Spot-checking self-attest entries

A self-attest proof is the farmer's word with a link attached. What the link should be depends on the action:

for a retweet, repost or comment, the link to the post itself — an X link must be a post (/status/) link;
for a follow or like, the farmer's profile link — an X follow by a farmer with a connected X account carries their handle automatically.

The platform only checked that the link had the right shape. Whether the post really exists, or the profile really follows you, is for you to open and see. Spot-check the entries with the largest rewards first.

When an entry is wrong

You cannot approve, reject, reverse or re-credit an entry. If a completion should not have been credited, send the entry's details to the platform team, who can void it. A void takes the points back from the farmer and marks the completion reversed. It is refused if the farmer has already spent those points on a token claim, so raise it early.

A reversed completion shows as Task reversed in that member's activity on your Members page, and the farmer sees it reversed in their own earnings. The Entries table itself does not flag reversed entries, and its Points card still counts the points as awarded.

What Entries is for

Use it as the audit trail of your season: who is farming, which tasks they complete, how fast points are being issued, and which self-attest proofs deserve a look. If a task is attracting completions you do not want, deactivate it from Tasks — the entries stay, the farmers keep their points, and no new ones arrive.