try build

ROTATE.md

@@ -119,7 +119,7 @@ experience. Therefore we came up with the a new idea to initiate this namespace:
       coin
       { 'guard : (read-keyset 'ns-keyset)
       , 'credential-id : "credential-id"
-      , 'hostname : "https://spirekey.kadena.io"
+      , 'hostname : "https://chainweaver.kadena.io"
       , 'device-type : "device-type"
       , 'color : "#hexcolor"
       }

docs/KIP-0030/SPECS.md

@@ -148,7 +148,7 @@ const someHandler = async () => {
 
 The `initSpireKey` function is optional and can be used to configure the SDK to
 target a different wallet using a `config` object. When omitted the SDK will
-will use `https://spirekey.kadena.io`.
+will use `https://chainweaver.kadena.io`.
 
 If you do want to use a different host, you can provide it via the config:
 

docs/KIP-0030/guides/create-account-and-connect-to-dapp.md

@@ -23,16 +23,16 @@ Your dApp will connect to a Kadena SpireKey wallet dApp that can be hosted
 anywhere. You could run it locally as described in the official Kadena Spirekey
 [Github repository](https://github.com/kadena-community/webauthn-wallet/), serve
 it from your own domain, or use the Kadena SpireKey wallet hosted by Kadena on
-[spirekey.kadena.io](spirekey.kadena.io). This guide assumes that you will be
-using the latter approach.
+[chainweaver.kadena.io](chainweaver.kadena.io). This guide assumes that you will
+be using the latter approach.
 
 ## Link to the Kadena SpireKey wallet
 
 On any page of your dApp, create a simple link to the `/connect` page of the
 Kadena SpireKey wallet dApp.
 
 ```
-https://spirekey.kadena.io/connect?returnUrl=http://localhost:3000&networkId=testnet04
+https://chainweaver.kadena.io/connect?returnUrl=http://localhost:3000&networkId=testnet04
 ```
 
 You need to pass the URL of your dApp as a URL encoded query parameter
@@ -86,7 +86,7 @@ account information from the user. The value for this parameter must be URL
 encoded. See the example below.
 
 ```
-https://spirekey.kadena.io/connect?returnUrl=http://localhost:3000&networkId=development&reason=Your%20reason.
+https://chainweaver.kadena.io/connect?returnUrl=http://localhost:3000&networkId=development&reason=Your%20reason.
 ```
 
 ### Use the account data
@@ -164,7 +164,7 @@ of pending transactions by decoding the `pendingTxIds` query parameter.
 With the `optimistic=true` parameter, the connect url would look like this:
 
 ```
-https://spirekey.kadena.io/connect?returnUrl=http://localhost:3000&networkId=development&reason=Your%20reason&optimistic=true
+https://chainweaver.kadena.io/connect?returnUrl=http://localhost:3000&networkId=development&reason=Your%20reason&optimistic=true
 ```
 
 With this connect url, the user will be redirected to the following url after

docs/KIP-0030/guides/create-account.md

@@ -1,12 +1,12 @@
 # **Create a Kadena Spirekey account**
 
 You can create a Kadena SpireKey account on
-[spirekey.kadena.io](https://spirekey.kadena.io). If you have not created a
-Kadena SpireKey account before, you will be redirected to the
-[Welcome page](https://spirekey.kadena.io). On the Welcome page you can choose
-to either recover an account, which is explained in another guide, or register a
-new account. Click the `Register` button to enter the registration flow and
-create a new Kadena SpireKey account.
+[chainweaver.kadena.io](https://chainweaver.kadena.io). If you have not created
+a Kadena SpireKey account before, you will be redirected to the
+[Welcome page](https://chainweaver.kadena.io). On the Welcome page you can
+choose to either recover an account, which is explained in another guide, or
+register a new account. Click the `Register` button to enter the registration
+flow and create a new Kadena SpireKey account.
 
 ## Registration flow
 
@@ -46,8 +46,8 @@ In the future, it will be possible to configure custom networks as well.
 #### Note for wallet developers
 
 You may have noticed that the `Network` step is missing on
-[spirekey.kadena.io](https://spirekey.kadena.io/register). That is because the
-deployment of this wallet dApp is configured with the environment variable
+[chainweaver.kadena.io](https://chainweaver.kadena.io/register). That is because
+the deployment of this wallet dApp is configured with the environment variable
 `WALLET_NETWORK_ID` set to `testnet04`. This forces users to create an account
 on the respective network. Therefore the `Network` step of the registration flow
 does not need to be presented to the user. The preselected network (`Testnet`)
@@ -99,14 +99,15 @@ the blockchain and definitively create your new account.
 ## Registration completed
 
 After completing the registration flow you are redirected back to the main page
-of [Kadena SpireKey](https://spirekey.kadena.io). Instead of the welcome screen
-that was presented before you created your first account, you will now see a
-card representing your newly created account. While the registration transaction
-is being mined, the name of your account - the `c:account` - will be presented
-in an animated state. Once the registration transaction has been mined, the
-animation will stop and the `c:account` will be displayed. Part of the account
-name will be masked for display purposes. Press the copy button to the right of
-the account name and paste it anywhere to see the full account name. At this
-point you have a fully functional Kadena SpireKey account guarded by a WebAuthn
-credentials. You can use this account to connect your account to dApps that
-integrate with Kadena SpireKey and sign transactions initiated by those dApps.
+of [Kadena SpireKey](https://chainweaver.kadena.io). Instead of the welcome
+screen that was presented before you created your first account, you will now
+see a card representing your newly created account. While the registration
+transaction is being mined, the name of your account - the `c:account` - will be
+presented in an animated state. Once the registration transaction has been
+mined, the animation will stop and the `c:account` will be displayed. Part of
+the account name will be masked for display purposes. Press the copy button to
+the right of the account name and paste it anywhere to see the full account
+name. At this point you have a fully functional Kadena SpireKey account guarded
+by a WebAuthn credentials. You can use this account to connect your account to
+dApps that integrate with Kadena SpireKey and sign transactions initiated by
+those dApps.

docs/KIP-0030/guides/recover-account.md

@@ -14,17 +14,18 @@ layout: full
 # Recover a Kadena Spirekey account
 
 After you register a device for a Kadena SpireKey account, the account details
-are stored on the Kadena blockchain and in the `Local storage` of the
-browser you used to register the account. You can view this information using
-the Developer Tools for the browser by selecting **Application**, then expanding
+are stored on the Kadena blockchain and in the `Local storage` of the browser
+you used to register the account. You can view this information using the
+Developer Tools for the browser by selecting **Application**, then expanding
 **Storage**. If you clear local storage—for example, by selecting **Clear
 browsing data**—or try to use a different browser to access your Kadena SpireKey
-account, the [Kadena SpireKey wallet](https://spirekey.kadena.io) won't be able
-to identify the account that belongs to you or recognize you as a registered
-user. However, you can recover your account information through the passkey
-stored on any device you created your account with or added to your account. For example, if you used a smart
-phone to register a Kadena SpireKey account, you can use the passkey stored on
-that phone to recover your account information.
+account, the [Kadena SpireKey wallet](https://chainweaver.kadena.io) won't be
+able to identify the account that belongs to you or recognize you as a
+registered user. However, you can recover your account information through the
+passkey stored on any device you created your account with or added to your
+account. For example, if you used a smart phone to register a Kadena SpireKey
+account, you can use the passkey stored on that phone to recover your account
+information.
 
 ## Identify the passkey for an account
 
@@ -46,13 +47,13 @@ in a secure enclave on the phone.
 
 For demonstration purposes, assume that you registered for a Kadena SpireKey
 account from a browser running on your local computer. If that's the case, you
-can open [spirekey.kadena.io](https://spirekey.kadena.io) in the browser and see
-that your account information is displayed by default from the information in
-local storage.
+can open [chainweaver.kadena.io](https://chainweaver.kadena.io) in the browser
+and see that your account information is displayed by default from the
+information in local storage.
 
 To clear local storage:
 
-1. Open [Kadena SpireKey](https://spirekey.kadena.io).
+1. Open [Kadena SpireKey](https://chainweaver.kadena.io).
 2. Open the Developer Tools.
 3. Open the Console and type the following command:
 
@@ -68,7 +69,7 @@ To clear local storage:
 To recover account information:
 
 1. Click **Recover** or open
-   [spirekey.kadena.io/recover](https://spirekey.kadena.io/recover).
+   [chainweaver.kadena.io/recover](https://chainweaver.kadena.io/recover).
 2. Click in the Passkey fingerprint section.
 3. Select the passkey for the account you want to recover.
 

docs/KIP-0030/guides/send-transaction.md

@@ -125,7 +125,7 @@ navigate users back to your dApp. This information will be passed via url
 parameters.
 
 You will use the same host that you used to connect the account and navigate to
-the sign page: https://spirekey.kadena.io/sign
+the sign page: https://chainweaver.kadena.io/sign
 
 In the following table you can see what parameters are currently accepted by
 SpireKey.
@@ -152,7 +152,7 @@ const encodedTx = btoa(JSON.stringify(tx));
 const encodedReturnUrl = encodeURIComponent(RETURN_URL);
 
 // The url you need to navigate to sign and return the transaction
-const sendTransactionUrl = `https://spirekey.kadena.io/sign#transaction=${encodedTx}&returnUrl=${encodedReturnUrl}`;
+const sendTransactionUrl = `https://chainweaver.kadena.io/sign#transaction=${encodedTx}&returnUrl=${encodedReturnUrl}`;
 ```
 
 Once you construct the route to the wallet with the required parameters, you can

examples/embedded-nextjs/src/steps/Connect.tsx

@@ -24,7 +24,7 @@ export const ConnectStep = ({
 }) => {
   const [wallet, setWallet] = useLocalState(
     'wallet',
-    'https://spirekey.kadena.io/',
+    'https://chainweaver.kadena.io/',
   );
   const [networkId, setNetworkId] = useLocalState('networkId', 'testnet04');
   const [chainId, setChainId] = useLocalState('chainId', '14');
@@ -91,7 +91,7 @@ export const ConnectStep = ({
                 onSelectionChange={(w) => setWallet(w as string)}
                 selectedKey={wallet}
               >
-                <SelectItem key="https://spirekey.kadena.io/">
+                <SelectItem key="https://chainweaver.kadena.io/">
                   SpireKey
                 </SelectItem>
                 <SelectItem key="http://localhost:1337/">Local</SelectItem>

sdk/README.md

@@ -149,7 +149,7 @@ const someHandler = async () => {
 
 The `initSpireKey` function is optional and can be used to configure the SDK to
 target a different wallet using a `config` object. When omitted the SDK will
-will use `https://spirekey.kadena.io`.
+will use `https://chainweaver.kadena.io`.
 
 If you do want to use a different host, you can provide it via the config:
 

spirekey/pact/spirekey.repl

@@ -81,7 +81,7 @@
       coin
       { 'guard          :  (read-keyset 'ns-keyset)
       , 'credential-id  :  "credential-id"
-      , 'domain         :  "https://spirekey.kadena.io"
+      , 'domain         :  "https://chainweaver.kadena.io"
       , 'device-type    :  "device-type"
       , 'color          :  "#hexcolor"
       }