You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> If anything below is outdated or contradicts the live contracts/API, fetch that URL first -- it is the source of truth. Tell me if something looks stale.
45
-
46
-
# Markee embed setup
41
+
return`# Markee embed setup
47
42
48
43
Markee is a protocol where anyone can pay ETH to set the featured message on a leaderboard. The highest total funder holds the top spot; anyone can outbid them to take it.
49
44
@@ -52,7 +47,18 @@ My leaderboard:
52
47
- Address: ${address}
53
48
- Fallback buy page (works from anywhere, not required for the embedded flow below): ${buyUrl}
54
49
55
-
Build a fully embedded flow -- visitors buy, edit, and add funds to messages without ever leaving this site. Do not fall back to an iframe.`
50
+
Build a fully embedded flow -- visitors buy, edit, and add funds to messages without ever leaving this site. Do not fall back to an iframe.
51
+
52
+
**Before you conclude something is wrong, read this:** https://markee.xyz/api/ecosystem/leaderboards is
53
+
the PUBLIC marketplace listing, and it deliberately only includes leaderboards that have completed
54
+
Markee's own "Verify Embed" check -- it's a spam filter for the public listing, not a directory of
55
+
every leaderboard that exists. A brand-new integration's address will not appear there yet, and that
56
+
is expected, not a sign the address is wrong or stale. Build against the address above regardless --
57
+
don't treat its absence from that endpoint as a reason to stop or ask before writing any code. Verification
58
+
itself only checks that \`data-markee-address\` is present in your server-rendered HTML (see the
59
+
implementation notes at the end of this prompt); it does not depend on this fetch succeeding. Once
60
+
verified, the same code you're about to write starts resolving real data automatically -- nothing
constcommonNote=`Browser fetches to markee.xyz are blocked by CORS on most setups, so this needs a server-side hop. Find your leaderboard by matching \`address\` (case-insensitive) against "${address}" in the response. Useful fields: \`topMessage\`, \`topMessageOwner\`, \`topFundsAddedRaw\`, \`minimumPrice\` (fixed) / \`streamedRateRaw\` (streaming), \`topMarkeeAddress\`.`
285
+
constcommonNote=`Browser fetches to markee.xyz are blocked by CORS on most setups, so this needs a server-side hop. Find your leaderboard by matching \`address\` (case-insensitive) against "${address}" in the response. Useful fields: \`topMessage\`, \`topMessageOwner\`, \`topFundsAddedRaw\`, \`minimumPrice\` (fixed) / \`streamedRateRaw\` (streaming), \`topMarkeeAddress\`. No match yet is expected for a brand-new, not-yet-verified leaderboard (see the note near the top of this prompt) -- have the trigger component fall back to a "be first!" empty state in that case, not an error.`
0 commit comments