diff --git a/multisig/proposals/ethereum/vip-047/index.ts b/multisig/proposals/ethereum/vip-046/index.ts
similarity index 100%
rename from multisig/proposals/ethereum/vip-047/index.ts
rename to multisig/proposals/ethereum/vip-046/index.ts
diff --git a/multisig/simulations/ethereum/vip-047/abi/ILComptroller.json b/multisig/simulations/ethereum/vip-046/abi/ILComptroller.json
similarity index 100%
rename from multisig/simulations/ethereum/vip-047/abi/ILComptroller.json
rename to multisig/simulations/ethereum/vip-046/abi/ILComptroller.json
diff --git a/multisig/simulations/ethereum/vip-047/index.ts b/multisig/simulations/ethereum/vip-046/index.ts
similarity index 85%
rename from multisig/simulations/ethereum/vip-047/index.ts
rename to multisig/simulations/ethereum/vip-046/index.ts
index bbcd8f9a7..c391945cd 100644
--- a/multisig/simulations/ethereum/vip-047/index.ts
+++ b/multisig/simulations/ethereum/vip-046/index.ts
@@ -3,7 +3,7 @@ import { expect } from "chai";
 import { ethers } from "hardhat";
 import { forking, pretendExecutingVip } from "src/vip-framework";
 
-import vip047, { COMPTROLLER_CORE, COMPTROLLER_CURVE, PRIME } from "../../../proposals/ethereum/vip-047";
+import vip046, { COMPTROLLER_CORE, COMPTROLLER_CURVE, PRIME } from "../../../proposals/ethereum/vip-046";
 import COMPTROLLER_ABI from "./abi/ILComptroller.json";
 
 forking(20321056, async () => {
@@ -11,7 +11,7 @@ forking(20321056, async () => {
 
   describe("Post-VIP behavior", () => {
     before(async () => {
-      await pretendExecutingVip(await vip047());
+      await pretendExecutingVip(await vip046());
     });
 
     it("Comptroller Core should have correct Prime token address", async () => {
diff --git a/vips/vip-340/bscmainnet.ts b/vips/vip-340/bscmainnet.ts
index 0a29f7dca..38d295df4 100644
--- a/vips/vip-340/bscmainnet.ts
+++ b/vips/vip-340/bscmainnet.ts
@@ -6,8 +6,25 @@ const CRITICAL_TIMELOCK = "0x213c446ec11e45b15a6E29C1C1b402B8897f606d";
 const vip340 = () => {
   const meta = {
     version: "v2",
-    title: "VIP-340 [Ethereum] Automatization of Prime update",
-    description: ``,
+    title: "VIP-340 [Ethereum] Prime synchronisation in the Core pool",
+    description: `If passed, this VIP allows the automatic update of the Prime rewards every time a Prime holder interacts with a Prime market of the Core and Curve pools.
+
+#### Security and additional considerations
+
+We applied the following security procedures for this upgrade:
+
+- **VIP execution simulation**: in a simulation environment, validating the new configuration is the expected one
+- This VIP doesn’t upgrade any smart contract. It only configures the Prime contract on the Core and Curve comptrollers
+
+#### References
+
+- [VIP simulation](https://github.com/VenusProtocol/vips/pull/324)
+- [VIP-339 [Ethereum] : Venus Prime Deployment - Q3 2024](https://app.venus.io/#/governance/proposal/339)
+- [Documentation](https://docs-v4.venus.io/whats-new/prime-yield)
+
+#### Disclaimer for Ethereum VIPs
+
+Privilege commands on Ethereum will be executed by the [Guardian wallet](https://etherscan.io/address/0x285960C5B22fD66A736C7136967A3eB15e93CC67), until the [Multichain Governance](https://docs-v4.venus.io/technical-reference/reference-technical-articles/multichain-governance) contracts are deployed. If this VIP passes, [this](https://app.safe.global/transactions/tx?safe=eth:0x285960C5B22fD66A736C7136967A3eB15e93CC67&id=multisig_0x285960C5B22fD66A736C7136967A3eB15e93CC67_0x2aab4f994d730c4a9ec9dcdcbc348bc6a9e5d7ed7995927671f938c636a6fd86) multisig transaction will be executed. Otherwise, it will be rejected.`,
     forDescription: "Execute this proposal",
     againstDescription: "Do not execute this proposal",
     abstainDescription: "Indifferent to execution",