How the system works

1) A venue posts a funded bounty — it defines the outcome it wants (verified arrivals, reservations, qualified introductions) and reserves the full reward budget upfront. 2) Trusted local members discover the bounty and deliver the outcome through their real relationships — a tap, an RSVP, a check-in. 3) Slyyyde verifies the outcome with check-in codes, evidence, and venue review. 4) The member is paid from the funded pool, Slyyyde keeps its success fee, and every unused dollar returns to the venue.

A funded bounty is a prepaid reward for a specific, measurable result. The venue sets the qualifying outcome, the reward amount, the capacity, and the deadline — and reserves the budget before the bounty goes live. Because the money is committed upfront, members know the reward is real, and venues only pay for outcomes that are actually verified.

The venue funds the bounty budget upfront. Slyyyde holds the budget, verifies each outcome, and pays the member's reward out of the funded pool. Slyyyde keeps a success fee on verified outcomes, and whatever is left unspent returns to the venue. Members never invoice or chase the venue — settlement is handled entirely inside the platform.

You can review taps and connections, discover and claim open bounties, track verification and payout status, follow your Trust Score and tier progress, view bonuses and reward history, create a referral link, update payout details, and manage your public profile and card.

Attribution proves that an outcome came through you. Your Trust Score is the running measure of your verified performance and determines your tier. A bounty reward is the cash you earn for a verified outcome. Bonuses are separate cash rewards for configured milestones, streaks, or qualified referrals. Trust Score points themselves are not cash and cannot be withdrawn.

Your NFC card opens your public member page instantly — no app needed. The tap is logged with a timestamp, and the person can leave their name and contact as a connection attributed to you.

Not directly. Taps and connections are the attribution trail — they prove the relationship started with you. Money comes from verified bounty outcomes: a guest who checks in, a reservation that shows up, an introduction that converts. Only verified outcomes count toward your earnings and leaderboard position.

Tell an admin. Your card can be deactivated instantly — its tap link stops working — and a new card can be issued to you without losing your history.

Bursts are throttled: taps are rate-limited per device, and repeated hits from the same device inside the hour don't stack. Since taps aren't money, gaming them earns nothing anyway.

Open bounties appear in your dashboard and in opportunity alerts. Each one states the qualifying outcome, the reward, the capacity, and the deadline. Deliver the outcome through your tap link, RSVP link, or check-in flow — the attribution is recorded automatically, and the result enters the verification queue.

Verification is layered: one-time check-in codes prove physical arrivals, submitted evidence is reviewed, the venue confirms delivery, and fraud controls flag anomalies. An outcome only counts — and only pays — after it clears verification. Rejected outcomes always come with a reason you can see on your dashboard.

Because every bounty is funded upfront, your reward is already reserved before you start. Once your outcome is verified, your payout is recorded with the amount, method, and reference, and paid from the funded pool. Slyyyde deducts its success fee, and any budget left unspent when the bounty closes returns to the venue. Your dashboard shows verified earnings and completed payouts separately.

Payouts are batched and recorded as they clear the funded pool. If a payout is queued, it is almost always waiting on final verification or the settlement batch — never on the venue paying first, because the budget was funded upfront. You never chase a venue for payment yourself; that's Slyyyde's job.

Every payout requires a payment method, payment reference, and evidence or approval note. Payouts of $1,000 or more require approval from a second administrator, and the administrator who requested the payout cannot approve their own request.

Pending means the reward was earned but still needs review. Approved means the amount passed review but has not necessarily been sent. Paid means Slyyyde recorded the completed payment from the funded pool.

Yes. Every outcome carries an immutable audit trail — who delivered it, who verified or rejected it, when, and every payout against it. Failed workflows, stale items, approval requests, and reconciliation issues are also tracked in the admin exception queue until resolved.

Your Trust Score is the running measure of your verified performance on the platform. It grows every time an outcome you delivered clears verification, and it determines your tier — which controls your share of bounty rewards and your access to premium opportunities. It is a reputation signal, not a cash balance.

Points are issued after a verified outcome or after both parties independently confirm an introduction. A verified introduction earns 50 points, carries no cash value, and is capped at 10 rewarded introductions per UTC month. Every reward uses a unique ledger record so the same event cannot be credited twice.

Each bounty category has a base amount per verified outcome plus possible volume points. Current rules include verified guests for Events, completed bookings for Rentals, completed engagements for Consulting, verified funded amounts for Capital, and verified outcomes for Other bounties. The exact category rules are shown through your incentive progress and can be updated prospectively by admins.

Current examples are: Events, 120 points per verified outcome plus 4 per verified guest; Consulting, 220 plus 50 per completed engagement; Capital, 300 plus 20 per verified $1,000 funded; and Other, 150 plus 25 per verified outcome. Rental rules follow the configured completed-booking values. Admins can update future incentive rules, while existing ledger entries remain recorded.

Your lifetime ledger points determine your current tier. The configured tiers currently progress from 70% to 75% and then 80% of the reward pool allocated to a verified outcome. The applicable percentage is fixed when the outcome is verified, so a later tier change does not silently rewrite an older reward.

An outcome is the category-specific result a bounty pays for — checked-in guests, a completed booking or engagement, or verified funded volume. It is recorded and verified through check-in codes, evidence, and venue review before points or milestone progress count.

Milestones pay a configured cash bonus after your verified outcome total reaches a threshold. A streak bonus is created after the required number of consecutive verified outcomes. These rewards appear in your reward ledger and move through pending, approved, and paid states rather than being paid automatically without review.

Create your referral link from the incentive section of your dashboard. A referral qualifies only after the referred member delivers their first verified outcome. At that point, the configured referral bonus is added once to your reward ledger.

When your ledger points reach the configured priority threshold, your dashboard marks you eligible for premium bounties before general release. Eligibility is a benefit, not a guarantee that a specific bounty will be assigned to you.

The Incentive Engine on your dashboard shows total points, tier progress, pending, approved and paid rewards, milestones, streaks, referrals, badges, and recent reward-ledger entries. If a number looks wrong, contact an admin so it can be reconciled against verified outcomes and the immutable ledger.

Event campaigns are attendance bounties: the venue funds a reward pool for verified guests, and each member gets a personal invite link for that campaign. Guests who RSVP through your link are attributed to you.

Every RSVP gets a one-time check-in code. Door staff scan or enter it at the event — first use checks the guest in and credits you; any reuse is rejected. That's the proof a guest actually came through your tap.

No. A contact can hold one spot per event, no matter whose link they use — first link wins the attribution.

A verified attribution report: total RSVPs against capacity, actual check-ins, and the per-member breakdown of who delivered which guests.

A restaurant can reward a Tap member for bringing a stated number of verified guests during one visit—for example, bring 4 guests and receive one free meal up to $30. Slyyyde manages attribution and verification; the restaurant supplies and funds the meal directly.

Start an active offer from your dashboard and share its unique check-in link with the guests who are physically joining your visit. Every required guest must submit their own check-in during that same visit. Taps, link opens, and unverified names do not count.

After the guest target is reached, Slyyyde reviews the visit. Once approved, show the venue-facing redemption code. An admin records the restaurant's completed redemption with a required note, and you can redeem each offer only once.

The cap is the maximum restaurant-funded value, not cash owed by Slyyyde. Every offer may have restrictions such as dine-in only, excluded items, gratuity, taxes, service times, and an expiration date. The published offer terms control redemption.

No. Venue meals are separate from Trust Score points, tiers, bounty rewards, and Slyyyde cash bonuses. Guest check-ins for an offer do not automatically become event attendance or bounty outcomes.

Guest contacts are normalized and privately hashed to block duplicates, members cannot count themselves, a guest cannot be attributed to competing visits for the same offer, links close after qualification or expiry, and every approval and redemption is recorded in an immutable audit trail.

Verified outcome value — the dollars that have cleared verification, filterable by time window and category. Pending and rejected outcomes never count.

It's still in verification. The board updates the moment it clears. If it was rejected, the reason is on your dashboard.