ignite · julienrbrt · Mar 20, 2025 · Mar 20, 2025 · Mar 20, 2025 · Mar 20, 2025
@@ -1,8 +1,5 @@
 {
   "ignorePatterns": [
-    {
-      "pattern": "^https://twitter.com"
-    },
     {
       "pattern": "^https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request"
     },

@@ -1,4 +1,4 @@
-name: Check Markdown links
+name: Check links
 on:
   pull_request:
   push:
@@ -15,8 +15,8 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - uses: gaurav-nelson/[email protected].13
+      - uses: gaurav-nelson/[email protected].16
         with:
           folder-path: "."
           use-verbose-mode: "yes"
-          config-file: ".github/workflows/md-link-checker-config.json"
+          config-file: ".github/workflows/link-checker-config.json"
@@ -9,6 +9,7 @@
 ### Changes
 
 - [#4569](https://github.com/ignite/cli/pull/4569) Add flags to set coin type on commands. Add getters for bech32 prefix and coin type.
+- [#4589](https://github.com/ignite/cli/pull/4589) Fix broken links
 
 ### Fixes
 

@@ -353,7 +353,7 @@ Normally, Keplr provides a wallet object implementing the `OfflineSigner`
 interface, so you can simply replace the `wallet` argument in client
 instantiation with `window.keplr.getOfflineSigner(chainId)`. However, Keplr
 requires information about your chain, like chain ID, denoms, fees, etc.
-[`experimentalSuggestChain()`](https://docs.keplr.app/api/suggest-chain.html) is
+[`experimentalSuggestChain()`](https://docs.keplr.app/api/guide/suggest-chain) is
 a method Keplr provides to pass this information to the Keplr extension.
 
 The generated client makes this easier by offering a `useKeplr()` method that

@@ -9,7 +9,7 @@ description: Ignite Chain.
 
 _Ignite is a blockchain to help launch Cosmos SDK-based blockchains._
 
-Using Cosmos SDK and Ignite CLI, developers can quickly create a crypto application that is decentralized, economical for usage, and scalable. The Cosmos SDK framework allows developers to create sovereign application-specific blockchains that become part of the wider [Cosmos ecosystem](https://v1.cosmos.network/ecosystem/apps). Blockchains created with Cosmos SDK use a Proof-of-Stake (PoS) consensus protocol that requires validators to secure the chain.
+Using Cosmos SDK and Ignite CLI, developers can quickly create a crypto application that is decentralized, economical for usage, and scalable. The Cosmos SDK framework allows developers to create sovereign application-specific blockchains that become part of the wider [Cosmos ecosystem](https://cosmos.network/ecosystem/apps). Blockchains created with Cosmos SDK use a Proof-of-Stake (PoS) consensus protocol that requires validators to secure the chain.
 
 Even though tools like Ignite CLI simplify the development of a Cosmos SDK blockchain, launching a new chain is a highly complex process. One of the major challenges of developing and launching your own sovereign blockchain is ensuring the security of the underlying consensus. Since Cosmos SDK chains are based on the PoS consensus, each blockchain requires initial coin allocations and validators before they can be launched, which presents developers with significant challenges, such as determining their chain's tokenomics or coordinating a robust validator set.
 

@@ -2696,7 +2696,7 @@ Configs for the chain registry
 
 Scaffold the chain registry chain.json and assets.json files.
 
-The chain registry is a GitHub repo, hosted at https://github.com/cosmos/cosmos-registry, that
+The chain registry is a GitHub repo, hosted at https://github.com/cosmos/chain-registry, that
 contains the chain.json and assets.json files of most of chains in the Cosmos ecosystem.
 It is good practices, when creating a new chain, and about to launch a testnet or mainnet, to
 publish the chain's metadata in the chain registry.

@@ -205,11 +205,11 @@ const config = {
               },
               {
                 label: "Twitter",
-                href: "https://twitter.com/ignite_com",
+                href: "https://x.com/ignite",
               },
               {
                 label: "Linkedin",
-                href: "https://www.linkedin.com/company/ignt/",
+                href: "https://www.linkedin.com/company/allinbits",
               },
               {
                 label: "YouTube",

@@ -249,7 +249,7 @@ const client = new Client({
 );
 ```
 
-The problem is that for a new Ignite CLI scaffolded chain, Keplr has no knowledge of it thus requiring an initial call to [`experimentalSuggestChain()`](https://docs.keplr.app/api/suggest-chain.html) method to add the chain information to the user's Keplr instance.
+The problem is that for a new Ignite CLI scaffolded chain, Keplr has no knowledge of it thus requiring an initial call to [`experimentalSuggestChain()`](https://docs.keplr.app/api/guide/suggest-chain) method to add the chain information to the user's Keplr instance.
 
 The generated client makes this easier by offering a `useKeplr()` method that autodiscovers the chain information and sets it up for you. Thus you can instantiate the client without a wallet and then call `useKeplr()` to enable transacting via Keplr like so:
 

@@ -11,7 +11,7 @@ In this tutorial, you will build a blockchain for a scavenger hunt game and lear
 * Implement custom logic in the CLI commands
 * Use an escrow account to store tokens
 
-This tutorial was first presented as a workshop at GODays 2020 Berlin by [Billy Rennekamp](https://twitter.com/billyrennekamp).
+This tutorial was first presented as a workshop at GODays 2020 Berlin by [Billy Rennekamp](https://x.com/billyrennekamp).
 
 This session aims to get you thinking about what is possible when developing applications that have access to **digital scarcity as a primitive**. The easiest way to think of scarcity is as money; If money grew on trees it would stop being _scarce_ and stop having value. 
 

@@ -353,7 +353,7 @@ Normally, Keplr provides a wallet object implementing the `OfflineSigner`
 interface, so you can simply replace the `wallet` argument in client
 instantiation with `window.keplr.getOfflineSigner(chainId)`. However, Keplr
 requires information about your chain, like chain ID, denoms, fees, etc.
-[`experimentalSuggestChain()`](https://docs.keplr.app/api/suggest-chain.html) is
+[`experimentalSuggestChain()`](https://docs.keplr.app/api/guide/suggest-chain) is
 a method Keplr provides to pass this information to the Keplr extension.
 
 The generated client makes this easier by offering a `useKeplr()` method that

@@ -9,7 +9,7 @@ description: Ignite Chain.
 
 _Ignite is a blockchain to help launch Cosmos SDK-based blockchains._
 
-Using Cosmos SDK and Ignite CLI, developers can quickly create a crypto application that is decentralized, economical for usage, and scalable. The Cosmos SDK framework allows developers to create sovereign application-specific blockchains that become part of the wider [Cosmos ecosystem](https://v1.cosmos.network/ecosystem/apps). Blockchains created with Cosmos SDK use a Proof-of-Stake (PoS) consensus protocol that requires validators to secure the chain.
+Using Cosmos SDK and Ignite CLI, developers can quickly create a crypto application that is decentralized, economical for usage, and scalable. The Cosmos SDK framework allows developers to create sovereign application-specific blockchains that become part of the wider [Cosmos ecosystem](https://cosmos.network/ecosystem/apps). Blockchains created with Cosmos SDK use a Proof-of-Stake (PoS) consensus protocol that requires validators to secure the chain.
 
 Even though tools like Ignite CLI simplify the development of a Cosmos SDK blockchain, launching a new chain is a highly complex process. One of the major challenges of developing and launching your own sovereign blockchain is ensuring the security of the underlying consensus. Since Cosmos SDK chains are based on the PoS consensus, each blockchain requires initial coin allocations and validators before they can be launched, which presents developers with significant challenges, such as determining their chain's tokenomics or coordinating a robust validator set.
 

@@ -354,7 +354,7 @@ Normally, Keplr provides a wallet object implementing the `OfflineSigner`
 interface, so you can simply replace the `wallet` argument in client
 instantiation with `window.keplr.getOfflineSigner(chainId)`. However, Keplr
 requires information about your chain, like chain ID, denoms, fees, etc.
-[`experimentalSuggestChain()`](https://docs.keplr.app/api/suggest-chain.html) is
+[`experimentalSuggestChain()`](https://docs.keplr.app/api/guide/suggest-chain) is
 a method Keplr provides to pass this information to the Keplr extension.
 
 The generated client makes this easier by offering a `useKeplr()` method that

@@ -9,7 +9,7 @@ description: Ignite Chain.
 
 _Ignite is a blockchain to help launch Cosmos SDK-based blockchains._
 
-Using Cosmos SDK and Ignite CLI, developers can quickly create a crypto application that is decentralized, economical for usage, and scalable. The Cosmos SDK framework allows developers to create sovereign application-specific blockchains that become part of the wider [Cosmos ecosystem](https://v1.cosmos.network/ecosystem/apps). Blockchains created with Cosmos SDK use a Proof-of-Stake (PoS) consensus protocol that requires validators to secure the chain.
+Using Cosmos SDK and Ignite CLI, developers can quickly create a crypto application that is decentralized, economical for usage, and scalable. The Cosmos SDK framework allows developers to create sovereign application-specific blockchains that become part of the wider [Cosmos ecosystem](https://cosmos.network/ecosystem/apps). Blockchains created with Cosmos SDK use a Proof-of-Stake (PoS) consensus protocol that requires validators to secure the chain.
 
 Even though tools like Ignite CLI simplify the development of a Cosmos SDK blockchain, launching a new chain is a highly complex process. One of the major challenges of developing and launching your own sovereign blockchain is ensuring the security of the underlying consensus. Since Cosmos SDK chains are based on the PoS consensus, each blockchain requires initial coin allocations and validators before they can be launched, which presents developers with significant challenges, such as determining their chain's tokenomics or coordinating a robust validator set.
 

@@ -353,7 +353,7 @@ Normally, Keplr provides a wallet object implementing the `OfflineSigner`
 interface, so you can simply replace the `wallet` argument in client
 instantiation with `window.keplr.getOfflineSigner(chainId)`. However, Keplr
 requires information about your chain, like chain ID, denoms, fees, etc.
-[`experimentalSuggestChain()`](https://docs.keplr.app/api/suggest-chain.html) is
+[`experimentalSuggestChain()`](https://docs.keplr.app/api/guide/suggest-chain) is
 a method Keplr provides to pass this information to the Keplr extension.
 
 The generated client makes this easier by offering a `useKeplr()` method that

@@ -9,7 +9,7 @@ description: Ignite Chain.
 
 _Ignite is a blockchain to help launch Cosmos SDK-based blockchains._
 
-Using Cosmos SDK and Ignite CLI, developers can quickly create a crypto application that is decentralized, economical for usage, and scalable. The Cosmos SDK framework allows developers to create sovereign application-specific blockchains that become part of the wider [Cosmos ecosystem](https://v1.cosmos.network/ecosystem/apps). Blockchains created with Cosmos SDK use a Proof-of-Stake (PoS) consensus protocol that requires validators to secure the chain.
+Using Cosmos SDK and Ignite CLI, developers can quickly create a crypto application that is decentralized, economical for usage, and scalable. The Cosmos SDK framework allows developers to create sovereign application-specific blockchains that become part of the wider [Cosmos ecosystem](https://cosmos.network/ecosystem/apps). Blockchains created with Cosmos SDK use a Proof-of-Stake (PoS) consensus protocol that requires validators to secure the chain.
 
 Even though tools like Ignite CLI simplify the development of a Cosmos SDK blockchain, launching a new chain is a highly complex process. One of the major challenges of developing and launching your own sovereign blockchain is ensuring the security of the underlying consensus. Since Cosmos SDK chains are based on the PoS consensus, each blockchain requires initial coin allocations and validators before they can be launched, which presents developers with significant challenges, such as determining their chain's tokenomics or coordinating a robust validator set.
 

@@ -15,7 +15,7 @@ func NewScaffoldChainRegistry() *cobra.Command {
 		Short: "Configs for the chain registry",
 		Long: `Scaffold the chain registry chain.json and assets.json files.
 
-The chain registry is a GitHub repo, hosted at https://github.com/cosmos/cosmos-registry, that
+The chain registry is a GitHub repo, hosted at https://github.com/cosmos/chain-registry, that
 contains the chain.json and assets.json files of most of chains in the Cosmos ecosystem.
 It is good practices, when creating a new chain, and about to launch a testnet or mainnet, to
 publish the chain's metadata in the chain registry.

@@ -269,7 +269,7 @@ Ignite CLI is a free and open source product maintained by
 [Ignite](https://ignite.com). Here's where you can find us. Stay in touch.
 
 - [ignite.com website](https://ignite.com)
-- [@ignite on Twitter](https://twitter.com/ignite)
+- [@ignite on Twitter](https://x.com/ignite)
 - [ignite.com/blog](https://ignite.com/blog)
 - [Ignite Discord](https://discord.com/invite/ignite)
 - [Ignite YouTube](https://www.youtube.com/@ignitehq)
-Original file line number
+Diff line change
@@ Expand Up / @@ -249,7 +249,7 @@ const client = new Client({ @@
     );
     ```
-    The problem is that for a new Ignite CLI scaffolded chain, Keplr has no knowledge of it thus requiring an initial call to [`experimentalSuggestChain()`](https://docs.keplr.app/api/suggest-chain.html) method to add the chain information to the user's Keplr instance.
+    The problem is that for a new Ignite CLI scaffolded chain, Keplr has no knowledge of it thus requiring an initial call to [`experimentalSuggestChain()`](https://docs.keplr.app/api/guide/suggest-chain) method to add the chain information to the user's Keplr instance.
     The generated client makes this easier by offering a `useKeplr()` method that autodiscovers the chain information and sets it up for you. Thus you can instantiate the client without a wallet and then call `useKeplr()` to enable transacting via Keplr like so:
@@ Expand Down @@