- What the person did
- Typed an email address into Copperpot Coffee's newsletter box and tapped Subscribe.
- What was checkedEmail submitted
- The submission, in this demo. That is the fast version and it is open to throwaway addresses. The safer version rewards after the person clicks the confirmation email, so only a verified inbox gets paid, and the confirmation doubles as the double opt-in.
- What landedToken
- In production: a small amount in the brand's token or USDC, or store credit. In this demo: Lummuns (LMN).
- The integration
- Fast version: the form posts to the brand's server, which signs a link and returns it to the page. Verified version: the server sends the confirmation email as usual, and when the person clicks it, the server signs the link and places it in the welcome email. Either way the address goes to the brand's list, never to Sliyd.
1Your page reports the event to your server
POST /rewards { event: "subscribed" }2Your server signs a single-use Sliyd link with your campaign secret
link = sign(campaign, secret, { src: "newsletter-signup" })3Sliyd opens a wallet from the link and pays the reward on claim
sliyd.com/reward/<campaign>/<id>?…&chk=…
Signing happens on your server, in whatever language it runs. The campaign secret never reaches a browser, and a link cannot be forged without it.
- What the brand gets
- Sign-ups per visitor, against the unrewarded box
- Verified against unverified sign-ups, which is the cost of the fast version
- A wallet attached to every subscriber, for the next campaign
This demo works the same way: the page confirms the action, the demo's own server signs the link, and the browser only ever sees the finished URL.
