Merge branch 'dev' into welldone

.gitbook/building-dapps/configuring-nuxt.md

@@ -30,8 +30,7 @@ $ yarn add @bangjelkoski/node-stdlib-browser
 $ yarn add -D @bangjelkoski/vite-plugin-node-polyfills
 ```
 
-Make sure you are using the `vue-tsc@1.8.8
-`, `nuxt@^3.8.1`, `typescript@^5.0.4` versions.
+Make sure you are using the `vue-tsc@1.8.8` , `nuxt@^3.8.1`, `typescript@^5.0.4` versions.
 
 **Buffer**
 
@@ -134,15 +133,10 @@ export default defineNuxtConfig({
 
   // Vite related config
   vite: {
-    define: {
-      "process.env": JSON.stringify({}),
-      "process.env.DEBUG": JSON.stringify(process.env.DEBUG),
-    },
-
     plugins: [ // setting up node + crypto polyfils + vite TS path resolution
       tsconfigPaths(),
       nodePolyfills({ protocolImports: false })
-      ],
+    ],
 
     build: {
       sourcemap: false, // we don't generate

.gitbook/core-modules/auction.md

@@ -71,8 +71,8 @@ How to find the subaccountId that you will be transferring from:
 
 How to use funds that are currently associated with your Injective Address in bank module:
 
-* If you have existing non-default subaccounts, you'll want to do a [MsgDeposit](broken-reference) to one of your existing non-default subaccountIds and use that subaccountId as the `srcSubaccountId` below.
-* If you don't have existing non-default subaccounts, you can do a [MsgDeposit](broken-reference) to a new default subaccountId, which would be done via importing `getSubaccountId` from `sdk-ts` and setting the `subaccountId` field in [MsgDeposit](broken-reference) to `getSubaccountId(injectiveAddress, 1)`.
+* If you have existing non-default subaccounts, you'll want to do a[ MsgDeposit ](exchange.md#msgdeposit)to one of your existing non-default subaccountIds and use that subaccountId as the `srcSubaccountId` below.
+* If you don't have existing non-default subaccounts, you can do a [MsgDeposit](exchange.md#msgdeposit) to a new default subaccountId, which would be done via importing `getSubaccountId` from `sdk-ts` and setting the `subaccountId` field in [MsgDeposit](exchange.md#msgdeposit) to `getSubaccountId(injectiveAddress, 1)`.
 
 For more info, check out the [burn auction pool docs](https://docs.injective.network/develop/tech-concepts/auction\_pool/).
 

.gitbook/core-modules/token-factory.md

@@ -31,6 +31,8 @@ const subdenom = "inj-test";
 
 const msg = MsgCreateDenom.fromJSON({
   subdenom,
+  symbol: 'InjTest',
+  name: 'Inj Testing',
   sender: injectiveAddress,
 });
 

.gitbook/readme/token-metadata/README.md

@@ -56,7 +56,8 @@ There are other ways to define a token metadata for a denom on Injective and we'
 
 Verifying your token's metadata can be done in a couple of ways. Here are the verification levels and what they mean: 
 
-* **Verified** -> Your asset metadata has been added to the `@injectivelabs/token-metadata` package. You can find a tutorial on how to add your token's metadata to the package [here](../../../packages/token-metadata/CONTRIBUTING.md).
+* **Verified** -> Your asset metadata has been **submitted and verified** to the `@injectivelabs/token-metadata` package. You can find a tutorial on how to add your token's metadata to the package [here](../../../packages/token-metadata/CONTRIBUTING.md).
+* **Submitted** -> Your asset metadata has been **submitted** to the `@injectivelabs/token-metadata` package. You can find a tutorial on how to add your token's metadata to the package [here](../../../packages/token-metadata/CONTRIBUTING.md).
 * **Internal** -> Your asset's metadata has been verified on-chain using the `MsgSetDenomMetadata` message, as explained [here](https://docs.ts.injective.network/core-modules/token-factory#msgsetdenommetadata).
 * **External** -> Your asset's metadata has been verified on some external source like from Ethereum's contract details, etc.
 * **Unverified** -> Your asset's metadata has not been provided anywhere.