Skip to content

Commit 7155ca3

Browse files
committed
feedback
1 parent 6e49710 commit 7155ca3

File tree

1 file changed

+29
-33
lines changed

1 file changed

+29
-33
lines changed

src/content/docs/en/developers/guides/canvas-badge-integration.mdx

Lines changed: 29 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -11,14 +11,11 @@ import Aside from "../../../../../components/Aside.astro"
1111
import BadgeDetails from "../_images/badgeDetails.jpg"
1212
import BadgeLevels from "../_images/badgeLevels.png"
1313
import ClickToZoom from "../../../../../components/ClickToZoom.astro"
14+
import Columns from "../../../../../components/Columns.astro"
1415
import ToggleElement from "../../../../../components/ToggleElement.astro"
1516

1617
We are thrilled to have you join us in building unique badges on Scroll Canvas, a product designed for ecosystem projects to interact with users in a more personal way on-chain.
1718

18-
<Aside>
19-
**Scroll Canvas** allows users to showcase on-chain credentials, status, and achievements called **Badges** issued and collected across the Scroll ecosystem. Users can mint a non-transferable and unique personal persona to collect and display their **Badges**.
20-
</Aside>
21-
2219
## Background
2320

2421
### Canvas
@@ -78,8 +75,9 @@ For Canvas and badge questions, please join [Scroll dev support channel](https:/
7875
| Issuance method | *Fully permissionless*: meaning your badge can be automatically issued by checking smart contract conditions <br/> *Gifted:* Badges can also be issues with no user interaction <br/> **Backend-authorized**: requires APIs to enable eligibility criteria ([API requirements](https://www.notion.so/Badge-APIs-95890d7ca14944e2a6d34835ceb6b914?pvs=21)) |
7976
| Support link | **Support channel link** to your Discord/Telegram group |
8077

78+
<Aside>
8179
On the badge details page, there's a button to **visit your official website**. We recommend creating a dedicated promotional page for the badge linked to that button. This will provide users with comprehensive information about the badge (background, purpose, how to obtain, available images, etc.).
82-
80+
</Aside>
8381
<Aside type="caution">
8482
Since **badges are permissionless**, Scroll Foundation may not troubleshoot individual third-party badges or answer eligibility questions. Provide ample resources for your community to mint badges smoothly. We ask that you share **Support URL** in Badge Listing process with enough resources (blog, how-to threads, TG/Discord support channel link).
8583
</Aside>
@@ -181,8 +179,9 @@ Since **badges are permissionless**, Scroll Foundation may not troubleshoot indi
181179
5. To maintain the availability of the check API and claim API, Scroll recommends maintaining a TPS of approximately 300. Adjust this rate accordingly if your API handles multiple badges simultaneously.
182180
6. If your badge image is stored on IPFS, due to the distributed nature of IPFS, the request time for users in different regions to access content on IPFS can be unpredictable. If they want a better user experience, they can self-host the content.
183181

184-
At this stage, your Badge is live on Scroll Canvas. Badge launch is permissionless. You can deploy as many badges as needed. Scroll does not need to approve your badge deployment.
185-
182+
<Aside>
183+
At this stage, your Badge is live on Scroll Canvas. Badge launch is permissionless. You can deploy as many badges as needed. **Scroll does not need to approve your badge deployment.**
184+
</Aside>
186185
<Aside type="caution">
187186
Regularly monitor server logs to stay informed of any potential issues, especially during the first 48 hours when the badge is live.
188187
</Aside>
@@ -201,29 +200,26 @@ Regularly monitor server logs to stay informed of any potential issues, especial
201200
2. Share on social media about your badge launch and the eligibility criteria. Use `#BadgeonScroll` and tag `@Scroll_ZKP` to boost more visibility.
202201
3. Monitor your community / support channel for user feedback. If there is any Canvas backend related issues, please reach out to Scroll Discord channel.
203202

204-
---
205-
206-
## Extra Boost: Getting Featured on [Discover Badges Page](https://scroll.io/canvas-and-badges)
207-
208-
<Aside>
209-
You can display **all of the badges** in your own product permissionlessly. Discover Badges page serves as an additional channel for your badges to get promoted.
210-
211-
Please be careful when submitting your application. We’re eager to introduce useful and creative badges for the Scroll ecosystem. The Scroll team is thoroughly reviewing each badge listing, which means the process might take a bit longer. Thank you for your patience.
212-
</Aside>
213-
214-
1. Ensure that your project is listed on the [Scroll Ecosystem Page](https://scroll.io/ecosystem). If you cannot find it yet, please [fill out this form](https://tally.so/r/waxLBW) to discuss onboarding your Badges with Scroll Partnerships team.
215-
2. **Application Portal**: [https://scroll.io/canvas/listing](https://scroll.io/canvas/listing)
216-
- General Badge Review Criteria :
217-
- Project is indexed on Scroll’s ecosystem page. If you cannot find it yet, please [fill out this form](https://tally.so/r/waxLBW).
218-
- Complete and clear badge description including Badge name, Issuer name, Issuer URL (website/official link), Support URL (support channel link).
219-
- Clear and reasonable eligibility criteria. Scroll holds discretion on not featuring badges with criteria that can be exploitive to users.
220-
- Badge design is high-resolution, representative of the issuer’s branding.
221-
- **Two badges** will be on display from the same project on Canvas & Badges page. If there are new and innovative new use cases for badges from the same project, Scroll team will consider making exceptions to allow up to two more badges.
222-
- Once your project is visible on the ecosystem page, after they submit the listing request form, Scroll team will review submission and approve on a weekly basis.
223-
- Badge Swaps and Withdrawal
224-
- After reaching the 2 badge quota, if a project team wants to add new badges, they can raise the request in Discord with link to the new badge information.
225-
226-
---
227-
228-
## FAQ
229-
{/* TODO */}
203+
<ToggleElement anchor="reference-cors">
204+
<div slot="title">Extra Boost: Getting Featured on [Discover Badges Page](https://scroll.io/canvas-and-badges)</div>
205+
206+
<Aside>
207+
You can display **all of the badges** in your own product permissionlessly. Discover Badges page serves as an additional channel for your badges to get promoted.
208+
</Aside>
209+
<Aside type="caution">
210+
Please be careful when submitting your application. We’re eager to introduce useful and creative badges for the Scroll ecosystem. The Scroll team is thoroughly reviewing each badge listing, which means the process might take a bit longer. Thank you for your patience.
211+
</Aside>
212+
213+
1. Ensure that your project is listed on the [Scroll Ecosystem Page](https://scroll.io/ecosystem). If you cannot find it yet, please [fill out this form](https://tally.so/r/waxLBW) to discuss onboarding your Badges with Scroll Partnerships team.
214+
2. **Application Portal**: [https://scroll.io/canvas/listing](https://scroll.io/canvas/listing)
215+
- General Badge Review Criteria :
216+
- Project is indexed on Scroll’s ecosystem page. If you cannot find it yet, please [fill out this form](https://tally.so/r/waxLBW).
217+
- Complete and clear badge description including Badge name, Issuer name, Issuer URL (website/official link), Support URL (support channel link).
218+
- Clear and reasonable eligibility criteria. Scroll holds discretion on not featuring badges with criteria that can be exploitive to users.
219+
- Badge design is high-resolution, representative of the issuer’s branding.
220+
- **Two badges** will be on display from the same project on Canvas & Badges page. If there are new and innovative new use cases for badges from the same project, Scroll team will consider making exceptions to allow up to two more badges.
221+
- Once your project is visible on the ecosystem page, after they submit the listing request form, Scroll team will review submission and approve on a weekly basis.
222+
- Badge Swaps and Withdrawal
223+
- After reaching the 2 badge quota, if a project team wants to add new badges, they can raise the request in Discord with link to the new badge information.
224+
225+
</ToggleElement>

0 commit comments

Comments
 (0)