From d106f07996981c67d722005805cbac92d6c29a7e Mon Sep 17 00:00:00 2001
From: fanyarachel <906119636rachel@gmail.com>
Date: Mon, 23 Sep 2024 17:53:01 +0800
Subject: [PATCH 1/3] fix the title

---
 .../developers/guides/canvas-badge-integration.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/src/content/docs/en/developers/guides/canvas-badge-integration.mdx b/src/content/docs/en/developers/guides/canvas-badge-integration.mdx
index ed1bd6d3c..101356aa5 100644
--- a/src/content/docs/en/developers/guides/canvas-badge-integration.mdx
+++ b/src/content/docs/en/developers/guides/canvas-badge-integration.mdx
@@ -22,7 +22,7 @@ We are thrilled to have you join us in building unique badges on Scroll Canvas,
 
 Each Canvas is a `Profile` smart contract, minted by the users through the `ProfileRegistry` contract on Scroll. Canvas is not transferrable and unique to each wallet.
 
-Canvas is an open onchain profile database of user identities and achievements ([check out dashboard built by community on Dune](https://dune.com/queries/3930803/6609287)).
+Canvas is an open onchain profile database of user identities and achievements ([check out dashboard built by community on Dune](https://dune.com/soodoo/scroll-marks)).
 
 ### Badge
 
@@ -51,7 +51,7 @@ Badge issuance and deployment of the contract is fully permissionless. Please fo
 For Canvas and badge questions, please join [Scroll dev support channel](https://discord.com/channels/853955156100907018/1028102371894624337)
 </Aside>
 
-## Step 1: Badge Design Guidelines `Design`
+## Step 1 `Design`: Badge Design Guidelines 
 
 <Columns>
     <Fragment slot="1"><ClickToZoom src={BadgeDetails} alt="BadgeDetails" caption="Example of badge detail page"/></Fragment>
@@ -82,7 +82,7 @@ On the badge details page, there's a button to **visit your official website**.
 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).
 </Aside>
 
-## Step 2: Deploying Badges & Go Live `Engineering`
+## Step 2 `Engineering`: Deploying Badges & Go Live 
 
 <Aside type="tip" title="Deployment Resources">
 - [Canvas Dev Doc (contract included)](https://github.com/scroll-tech/canvas-contracts)
@@ -152,7 +152,7 @@ Since **badges are permissionless**, Scroll Foundation may not troubleshoot indi
 4. **Access Readiness**: Ensure badge contract address implements `defaultTokenURI`, allowing retrieval of default display data (`name, image, description`) via `bytes32(0)` with informative name and description. 
 5. **Set up support**: Prepare a channel for your badge holders can find you for support, get the url to join that channel ready.
 
-## Step 3: Sanity Check `Test`
+## Step 3 `Test`: Sanity Check 
 
 1. Please visit `https://scroll.io/canvas/badge-contract/{{badgeContractAddress}}` to ensure that the badge is functioning correctly.
     - For `badgeTokenURI` link returned, ensure correct cross-origin configuration
@@ -186,7 +186,7 @@ At this stage, your Badge is live on Scroll Canvas. Badge launch is permissionle
 Regularly monitor server logs to stay informed of any potential issues, especially during the first 48 hours when the badge is live.
 </Aside>
 
-## Step 4: Reveal Your Badge `Announce`
+## Step 4 `Announce`: Reveal Your Badge 
 
 1. To get the word out faster, you are encouraged to embed badge mint and discovery in your product!  Scroll provides an example code for anthropomorphic "assistants" to pop up when the user meets the badge minting requirements.
     
@@ -201,10 +201,10 @@ Regularly monitor server logs to stay informed of any potential issues, especial
 3. Monitor your community / support channel for user feedback. If there is any Canvas backend related issues, please reach out to Scroll Discord channel.
 
 <ToggleElement anchor="reference-cors">
-    <div slot="title">Extra Boost: Getting Featured on [Discover Badges Page](https://scroll.io/canvas-and-badges)</div>
+    <div slot="title">Get listed on [Canvas & Badges] (https://scroll.io/canvas-and-badges)</div>
 
     <Aside>
-        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.
+        You can display **all of the badges** in your own product permissionlessly. Discover Badges page serves as an additional discovery channel for your badges.
     </Aside>
     <Aside type="caution">
         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.

From 1a104f121fd9556c2c8ced9ddac7ba4cae30e6bd Mon Sep 17 00:00:00 2001
From: fanyarachel <906119636rachel@gmail.com>
Date: Thu, 26 Sep 2024 21:31:19 +0800
Subject: [PATCH 2/3] Unbold the text under toggle list

---
 src/components/ToggleElement.astro                 |  2 +-
 .../developers/guides/canvas-badge-integration.mdx | 14 +++++++-------
 2 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/src/components/ToggleElement.astro b/src/components/ToggleElement.astro
index 58ba96588..c1b44990c 100644
--- a/src/components/ToggleElement.astro
+++ b/src/components/ToggleElement.astro
@@ -48,7 +48,7 @@ const anchorHash = anchor.replace(/\s+/g, "-")
     border-radius: 27px;
     border: 1px solid #dadada;
     overflow: hidden;
-    font-weight: 600;
+    font-weight: 400;
     padding-left: 0.3rem;
     @apply text-black dark:text-white-800 border-primary dark:border-dark-primary;
   }
diff --git a/src/content/docs/en/developers/guides/canvas-badge-integration.mdx b/src/content/docs/en/developers/guides/canvas-badge-integration.mdx
index 101356aa5..b7d71d61d 100644
--- a/src/content/docs/en/developers/guides/canvas-badge-integration.mdx
+++ b/src/content/docs/en/developers/guides/canvas-badge-integration.mdx
@@ -26,7 +26,7 @@ Canvas is an open onchain profile database of user identities and achievements (
 
 ### Badge
 
-**Badges** are attestations of identities, achievements and traits verified through the [Ethereum Attestation Service](https://docs.attest.sh/docs/welcome), issued **permissionlessly by different ecosystem projects**. Badges are wallet-bound and non-transferable. **Badges facilitate interactions between ecosystem projects and users.**
+**Badges** are attestations of identities, achievements and traits verified through the [Ethereum Attestation Service](https://scroll.easscan.org/learn/scroll), issued **permissionlessly by different ecosystem projects**. Badges are wallet-bound and non-transferable. **Badges facilitate interactions between ecosystem projects and users**. 
 
 Developers can issue badges in three methods:
 
@@ -48,7 +48,7 @@ Developers can design badges in two ways:
 Badge issuance and deployment of the contract is fully permissionless. Please follow the steps below to issue a Badge for your project.
 
 <Aside type="note" title="Join Developer Support Channel">
-For Canvas and badge questions, please join [Scroll dev support channel](https://discord.com/channels/853955156100907018/1028102371894624337)
+For Canvas and badge questions, please join [Scroll dev support channel](https://discord.com/invite/scroll)
 </Aside>
 
 ## Step 1 `Design`: Badge Design Guidelines 
@@ -72,7 +72,7 @@ For Canvas and badge questions, please join [Scroll dev support channel](https:/
 | Description       | Brief description of the *purpose* of this badge and *who is eligible* |
 | Structure         | *One single attribute*<br/>  *Multiple Badges with levels* trigged by different actions and traits |
 | Category          | *Achievement*: tasks you have done. e.g. Scroll Origin NFTs, tasks completion badge <br/> *Identities*: who you are. e.g. Ethereum year, GItcoin passport, NFT community badge |
-| 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)) |
+| 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, requires APIs <br/> *Backend-authorized*: requires APIs to enable eligibility criteria |
 | Support link      | **Support channel link** to your Discord/Telegram group |
 
 <Aside>
@@ -146,8 +146,6 @@ Since **badges are permissionless**, Scroll Foundation may not troubleshoot indi
             // http code is not 200
             ```
     </ToggleElement>
-
-    More details: [Badge APIs] {/* TODO: where to put this extra page */}
     
 4. **Access Readiness**: Ensure badge contract address implements `defaultTokenURI`, allowing retrieval of default display data (`name, image, description`) via `bytes32(0)` with informative name and description. 
 5. **Set up support**: Prepare a channel for your badge holders can find you for support, get the url to join that channel ready.
@@ -193,15 +191,17 @@ Regularly monitor server logs to stay informed of any potential issues, especial
     <aside>
     📖
     
-    [**Scroll Canvas - A**nthropomorphic "assistants" **Integration Guide for Developers**](https://www.notion.so/Scroll-Canvas-Anthropomorphic-assistants-Integration-Guide-for-Developers-2712f7a91af042c0a2d145af804bab51?pvs=21)
+    [**Scroll Canvas - A**nthropomorphic "assistants" **Integration Guide for Developers**](https://github.com/scroll-tech/frontends/blob/mainnet/docs/canvas.md)
     
     </aside>
     
 2. Share on social media about your badge launch and the eligibility criteria. Use `#BadgeonScroll` and tag `@Scroll_ZKP` to boost more visibility.
 3. Monitor your community / support channel for user feedback. If there is any Canvas backend related issues, please reach out to Scroll Discord channel.
 
+---
+
 <ToggleElement anchor="reference-cors">
-    <div slot="title">Get listed on [Canvas & Badges] (https://scroll.io/canvas-and-badges)</div>
+    <div slot="title">Get listed on [Canvas & Badges](https://scroll.io/canvas-and-badges)</div>
 
     <Aside>
         You can display **all of the badges** in your own product permissionlessly. Discover Badges page serves as an additional discovery channel for your badges.

From 13fdded4dad4fe1e5ae2c0188cc6bed1815ded0a Mon Sep 17 00:00:00 2001
From: fanyarachel <906119636rachel@gmail.com>
Date: Sun, 29 Sep 2024 15:24:25 +0800
Subject: [PATCH 3/3] Update the content

---
 .../guides/canvas-badge-integration.mdx       | 22 +++++++++++++------
 1 file changed, 15 insertions(+), 7 deletions(-)

diff --git a/src/content/docs/en/developers/guides/canvas-badge-integration.mdx b/src/content/docs/en/developers/guides/canvas-badge-integration.mdx
index ec0128e53..218bb5711 100644
--- a/src/content/docs/en/developers/guides/canvas-badge-integration.mdx
+++ b/src/content/docs/en/developers/guides/canvas-badge-integration.mdx
@@ -152,7 +152,14 @@ Since **badges are permissionless**, Scroll Foundation may not troubleshoot indi
 
 ## Step 3 `Test`: Sanity Check 
 
-1. Please visit `https://scroll.io/canvas/badge-contract/{{badgeContractAddress}}` to ensure that the badge is functioning correctly.
+1. Once your badge has been deployed on Scroll, you can auto-check some of these requirements by running `yarn check-badge`.([link to check badge script](https://github.com/scroll-tech/canvas-contracts/blob/master/script/CheckBadge.s.sol))
+    - If your badge minting transaction reverts, we recommend debugging using `cast`:
+
+    ```bash
+    cast run --rpc-url https://rpc.scroll.io [txhash]
+    ```
+
+    This call will simulate the transaction in a local environment and show you the call stack and revert reason.
     - For `badgeTokenURI` link returned, ensure correct cross-origin configuration
     <ToggleElement anchor="reference-cors">
     <div slot="title">Reference: CORS</div>
@@ -171,11 +178,12 @@ Since **badges are permissionless**, Scroll Foundation may not troubleshoot indi
             
             - **`scroll.io` domain**: requests originating from **`scroll.io`** are permitted.
     </ToggleElement>
-2. Review the information on the badge detail page: Confirm that all basic badge information and redirect links are correct and match the information you provided.
-3. Verify that the check API is operational. Test it with 2-4 wallet addresses eligible/ineligible to mint this badge and confirm that the claim API is functioning properly.
-4. If you have created a badge that can be upgraded, please use wallets that meet different level requirements to attempt minting it. Ideally, find at least one wallet per level requirement to ensure the badge mints correctly.
-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. 
-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. 
+2. **Review the information on the badge detail page**: 
+    - Confirm that all basic badge information and redirect links are correct and match the information you provided.
+    - Verify that the check API is operational. Test it with 2-4 wallet addresses eligible/ineligible to mint this badge and confirm that the claim API is functioning properly.
+    - If you have created a badge that can be upgraded, please use wallets that meet different level requirements to attempt minting it. Ideally, find at least one wallet per level requirement to ensure the badge mints correctly.
+3. 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. 
+4. 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. 
 
 <Aside>
 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.**
@@ -205,7 +213,7 @@ Regularly monitor server logs to stay informed of any potential issues, especial
     <div slot="title">Get listed on [Canvas & Badges](https://scroll.io/canvas-and-badges)</div>
 
     <Aside>
-        You can display **all of the badges** in your own product permissionlessly. Discover Badges page serves as an additional discovery channel for your badges.
+        You can display **all of the badges** in your own product permissionlessly. Canvas and Badges display page serves as an additional discovery channel for your badges.
     </Aside>
     <Aside type="caution">
         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.