YAPFI
Protocol

How posts are verified

Every submission is checked against the live post before a reward is credited.

YAPFI does not take anyone's word for it. When a link is submitted, the server fetches the post from the platform and runs these checks in order:

  1. The post exists and is public. Deleted, private or mistyped links fail here.
  2. It is on the right platform for the task.
  3. The author is you. The post's author must be the handle you proved you own.
  4. It contains the required tag, such as $JUP on X or #JUP on TikTok.
  5. It says it is paid, when the campaign requires disclosure. #ad, #sponsored or the words "paid partnership" all count.
  6. It has not been rewarded before. One post earns one reward.

Where the data comes from

YAPFI reads the post from X or TikTok itself: that it exists, who wrote it and what it says. View and like counts are read from the platform where it shares them.

Flat tasks and per-view tasks

Flat tasks pay as soon as these checks pass. Per-view tasks need a real view count. Where the platform shares the count, views are read automatically. Where it does not, the submission is marked pending and the project enters the view count during review. YAPFI never pays out on estimated views.

Entry requirements

Campaigns are open to everyone by default. A project can set a minimum follower count, a minimum account age, or holders only. Holders only is checked on-chain on every post. Follower count and account age are read from X where X shares them. When a number cannot be read, YAPFI does not guess: the post waits for the project to check the profile and approve it.

Follower counts are easy to buy and say little about whether a post is good, so a minimum is a blunt tool. Projects that want to reward reach should prefer per-view tasks.