LUNOR / QUESTS

Infrastructure for community programs.

Quests, reviews, and a USDT ledger for the communities around a Lunor project. One organization, many communities, one permission model.

DEMO DATA

Follow the launch thread

Draft · 3 tasks · 150 XP

01
A quest version
Contributors claim the version that was published, not whatever the draft says tomorrow.
02
A review decision
Approve, reject, star, or hold. The reason code is stored separately from the note.
03
A ledger entry
XP, Lunor Points, and USDT each move by append-only records. A retry does not pay twice.

A task is verified only when the provider can actually see it. If an API cannot confirm the action, the claim waits for a person.

Tenant checks: A session from one community cannot read another community's members.
Signed webhooks: The signing secret stays off the JSON body. Replays are rejected.
No card data: Plans are paid in USDT. Reward funds are a separate book.

USDT / month

149

USDT / month, example

359

USDT / month, example

Custom

USDT, quoted

The HTTP API uses scoped keys, cursor pagination, and idempotency on anything that moves money or rewards.

{
  "error": {
    "code": "QUEST_NOT_AVAILABLE",
    "message": "This quest is no longer available.",
    "requestId": "req_01h..."
  }
}