updates

Author: shahbaz17

src/pages/guides/bitcoin-taproot-mpc.mdx

@@ -34,12 +34,22 @@ started. Let’s dive in!
   [instructions on setting up the Web3Auth Dashboard](/docs/dashboard-setup).
 - Web3Auth MPC CoreKit SDK: This guide assumes that you already know how to integrate the MPC
   CoreKit SDK in your project and able to set up the login flow. If not, you can learn how to
-  [integrate Web3Auth in your web app](/docs/sdk/mpc-core-kit/mpc-core-kit-js).
+  [integrate Web3Auth MPC Core Kit SDK in your web app](/docs/sdk/mpc-core-kit/mpc-core-kit-js).
+
+## TLDR;
+
+- **Web3Auth MPC CoreKit**: Initialize the CoreKit instance and set up the login flow.
+- **Bitcoin Signer**: Create a BitcoinJS-compatible signer for BIP340 Schnorr signatures.
+- **Bitcoin Operations**: Implement Bitcoin-specific operations like address generation and
+  transaction signing.
+- **Usage Guide**: Learn how to use the application to interact with Bitcoin Taproot.
+
+      Get a clone of the [example repository](https://github.com/Web3Auth/web3auth-core-kit-examples/mpc-core-kit-web/mpc-core-kit-bitcoin-taproot) to follow along with the guide.
 
 ## Initialization
 
-Before interacting with Web3Auth MPC CoreKit, we need to initialize it. This is done in the App.tsx
-file, where we configure the CoreKit instance with the necessary parameters.
+Before interacting with Web3Auth MPC CoreKit, we need to initialize it. This is done in the
+`App.tsx` file, where we configure the CoreKit instance with the necessary parameters.
 
 ### Setting Up Web3Auth MPC CoreKit
 
@@ -53,22 +63,23 @@ import { tssLibFrostBip340 } from "@toruslabs/tss-frost-lib-bip340";
 let coreKitInstance: Web3AuthMPCCoreKit;
 if (typeof window !== "undefined") {
   coreKitInstance = new Web3AuthMPCCoreKit({
-    web3AuthClientId,  // Your Web3Auth Client ID
-    web3AuthNetwork: WEB3AUTH_NETWORK.DEVNET, // Connects to Web3Auth's DEVNET environment
+    web3AuthClientId,  // Your Web3Auth Client ID, get it from the Web3Auth dashboard
+    web3AuthNetwork: WEB3AUTH_NETWORK.DEVNET, // Web3Auth's DEVNET environment
     storage: window.localStorage, // Uses localStorage for persisting user session
     manualSync: true, // Requires manual syncing of key shares
     tssLib: tssLibFrostBip340, // Uses Frost-BIP340 for threshold signature scheme (TSS)
   });
 }
 ```
 
-Here’s what each parameter does:
+The parameters for initializing the Web3Auth MPC CoreKit instance are as follows:
 
-    *	web3AuthClientId – Your unique Web3Auth Client ID.
-    *	web3AuthNetwork – Specifies the Web3Auth network (DEVNET in this case).
-    *	storage – Determines where session data is stored; here, we use localStorage.
-    *	manualSync – Enables manual synchronization of key shares for added control.
-    *	tssLibFrostBip340 – Defines the threshold signature scheme (TSS) library, in this case, Frost-BIP340, which is optimized for Bitcoin Taproot.
+- `web3AuthClientId` is your unique Web3Auth Client ID,
+- `web3AuthNetwork` specifies the Web3Auth network (DEVNET in this case),
+- `storage` determines where session data is stored (using localStorage here),
+- `manualSync` enables manual synchronization of key shares for added control, and
+- `tssLibFrostBip340` defines the threshold signature scheme (TSS) library, specifically
+  Frost-BIP340, optimized for Bitcoin Taproot.
 
 ### Initializing the CoreKit Instance
 
@@ -86,18 +97,12 @@ useEffect(() => {
 }, []);
 ```
 
-Here’s how it works:
-
-    *	setIsLoading(true) – Sets a loading state while initialization is in progress.
-    *	coreKitInstance.init() – Calls the initialization method, which connects CoreKit to Web3Auth.
-    *	setCoreKitStatus(coreKitInstance.status) – Stores the current status of CoreKit after initialization.
-    *	setIsLoading(false) – Removes the loading state once the process is complete.
-
 ## Authentication
 
 The project uses Firebase for authentication, allowing users to log in securely using their Google
-accounts. The login function, implemented in App.tsx, handles this authentication flow and
-integrates with Web3Auth MPC CoreKit.
+accounts. You can choose any authentication provider that suits your needs, but for this example, we
+using Firebase for its ease of integration. The login function, implemented in `App.tsx`, handles
+this authentication flow and integrates with Web3Auth MPC CoreKit.
 
 ### Logging in with Google
 
@@ -186,19 +191,17 @@ export const signInWithGoogle = async (): Promise<UserCredential> => {
 </TabItem>
 </Tabs>
 
-Explanation
+The login function performs the following steps:
 
-    1.	Check CoreKit Instance – Ensures coreKitInstance is initialized before proceeding.
+    1.	Checks the CoreKit Instance – Ensures coreKitInstance is initialized before proceeding.
     2.	Sign in with Google – Calls signInWithGoogle() to authenticate the user via Firebase.
-    3.	Retrieve ID Token – After login, the Firebase ID token is fetched for authentication.
-    4.	Parse Token – Decodes the ID token to extract user information, including the sub field (a unique user identifier).
-    5.	Authenticate with Web3Auth – Calls loginWithJWT(), passing the Firebase ID token to Web3Auth for authentication.
+    3.	Retrieve ID Token – After login, the Firebase ID token is fetched.
+    4.	Parse Token – Decodes the ID token to extract user information, including the sub field (a unique user identifier) used during login with Web3Auth.
+    5.	Authenticate with Web3Auth – Calls loginWithJWT(), passing the Firebase ID token(JWT) to Web3Auth for authentication.
     6.	Commit Changes (If Needed) – If the user is logging in for the first time, commitChanges() ensures key shares are properly stored.
     7.	Handle Recovery (If Needed) – If Web3Auth requires additional shares to reconstruct the key, the UI prompts the user for recovery options.
     8.	Update Application State – The current CoreKit status is stored for UI updates.
 
-Here’s the explanation in the style of your reference:
-
 ## Bitcoin Signer
 
 To enable Bitcoin Taproot signing with Web3Auth MPC CoreKit, we need to create a
@@ -246,7 +249,7 @@ export function createBitcoinJsSignerBip340(props: { coreKitInstance: Web3AuthMP
 }
 ```
 
-### Explanation
+The createBitcoinJsSignerBip340 function performs the following steps:
 
 1️⃣ Import Required Libraries
 
@@ -312,16 +315,9 @@ return {
 
     *	The signer returns the tweaked Taproot public key and the associated Bitcoin network configuration.
 
-Summary
-
-- This function derives a Taproot-compatible public key using Web3Auth MPC CoreKit.
-- It implements both standard and Schnorr signing for Bitcoin transactions.
-- The returned object integrates seamlessly with bitcoinjs-lib, making it easy to use in Bitcoin
-  applications.
-
 ## Bitcoin Operations
 
-The BitcoinComponent.tsx file implements Bitcoin-specific operations, allowing users to:
+The `BitcoinComponent.tsx` file implements Bitcoin-specific operations, allowing users to:
 
 - showAddress – Display the Taproot (BIP340) Bitcoin address.
 - showBalance – Fetch and display the balance for the generated Bitcoin address.
@@ -331,8 +327,6 @@ The BitcoinComponent.tsx file implements Bitcoin-specific operations, allowing u
 This component integrates BitcoinJS (bitcoinjs-lib), Schnorr signatures (@bitcoinerlab/secp256k1),
 and Web3Auth MPC for Taproot-compatible signing.
 
-Code Implementation
-
 ```js
 import { Web3AuthMPCCoreKit } from "@web3auth/mpc-core-kit";
 import { useEffect, useState } from "react";
@@ -342,11 +336,9 @@ import * as bitcoinjs from "bitcoinjs-lib";
 import { createBitcoinJsSignerBip340 } from "./BitcoinSigner";
 import axios from "axios";
 import { BlurredLoading } from "./Loading";
-
-bitcoinjs.initEccLib(ecc);
 ```
 
-### Explanation
+The BitcoinComponent.tsx file imports the necessary libraries and components for Bitcoin operations:
 
 1️⃣ Dependencies and Libraries
 
@@ -554,13 +546,6 @@ const showBalance = async () => {
 </button>
 ```
 
-Summary
-
-- Derives a Taproot-compatible address using MPC-based signing.
-- Fetches UTXOs and balance via Blockstream API.
-- Signs transactions with Schnorr signatures (BIP340).
-- Broadcasts transactions using a centralized testnet API (for now).
-
 ## Usage Guide
 
 1. **Login**: Click the "Login" button to authenticate using Firebase.