How quests work
Verified X engagement, batch-checked once per quest, paid from engagement credit.
A quest points at one X post and asks members to like, retweet or comment on it. Members who complete every required interaction earn points and XP. Nothing is honor-system: Fealty reads the post's actual engagers and matches them against members' connected X accounts.
Verified once, at the end
Engagement is read once, when the quest expires, not polled while it runs. When endsAt passes:
- Fealty reads the post's likers, retweeters or repliers (whichever the quest requires).
- Members whose connected X appears in every required list get the points, atomically.
- The quest is marked ended and the reads are billed to your engagement credit.
Late engagement after expiry doesn't count, and the single batch read keeps costs flat no matter how many members participate.
What it costs
Reads are billed at official X API rates against your server's engagement credit: roughly one cent per 100 engagers read, with per-quest read ceilings protecting you from viral posts. If credit runs out, the quest pauses instead of failing and resumes when you top up.
Where members see quests
Quests post to #quests with the required interactions and end time, and also appear on the community hub with direct links to the post.