> For the complete documentation index, see [llms.txt](https://docs.kumbaya.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kumbaya.xyz/getting-started/connect-your-wallet.md).

# Connect your wallet

When you click **Connect** in the top-right of the Kumbaya app, the **"How do you want to use Kumbaya?"** modal asks you to pick one of two paths. Both are non-custodial — you stay in full control of your funds — but they unlock different parts of the platform.

![The Kumbaya connect-wallet modal showing the two paths: Kumbaya Wallet (Full Access) and DEX only (Stay Private)](/files/3YjwiYyogWpzTsoCl9pX)

| Path                               | What you get                                   | What you don't get                    |
| ---------------------------------- | ---------------------------------------------- | ------------------------------------- |
| **Kumbaya Wallet** *(recommended)* | DEX + Launchpad + comments + tipping + profile | —                                     |
| **DEX only**                       | Swap + liquidity pools                         | Launchpad, profile, comments, tipping |

You can switch later if you change your mind.

## Kumbaya Wallet *(Full Access)*

This is the path you want if you plan to launch tokens, comment, tip, or have a profile. It uses [Privy](https://www.privy.io/) under the hood, and supports two ways to sign in:

**1. With your existing wallet** — connect MetaMask, Coinbase Wallet, Rainbow, or any WalletConnect-compatible wallet. Privy attaches your Kumbaya profile to that wallet address. Your assets stay in your wallet; Privy doesn't move them. You sign every transaction in your existing wallet as normal.

**2. With email or a social account** — Privy creates an embedded wallet for you, tied to your login. You don't install a browser extension, you don't write down a seed phrase. Supported login methods:

* **Email** (passcode sent to your inbox)
* **Google**, **X (Twitter)**, **Discord**, **GitHub**, **Telegram**

After signing in, your Kumbaya profile appears under that wallet — whether it was your existing one or a freshly-created embedded one.

> Your private key is never shared with Kumbaya. Embedded-wallet keys are held in Privy's secure infrastructure; only you can authorize transactions. You can export your key at any time if you want to move to a different wallet.

> ⚠️ **Each social-login method gives you a&#x20;*****different*****&#x20;embedded wallet.** Signing in with Google one day and email the next gives you two separate wallets with two separate balances. Pick one method and stick with it (or write down which method you used so you can find your funds again). Connecting an existing external wallet doesn't have this problem — that wallet is yours regardless.

## DEX only *(Stay Private)*

This is the path for traders who only want to swap and provide liquidity, with no social profile or attribution. You connect an existing wallet directly — no Kumbaya account.

* **Supported wallets:** any standard EVM wallet (MetaMask, Coinbase, Rainbow, WalletConnect-compatible).
* **What works:** the swap UI, the pool UI, adding/removing liquidity, collecting LP fees.
* **What doesn't:** launching tokens, claiming a token listing, posting yaps, tipping, building a profile, the launchpad feed actions. If you try to access launchpad-only features, the app will prompt you to switch to the Kumbaya Wallet path.

You can always switch from DEX-only to Kumbaya Wallet later — the modal lets you upgrade without losing your wallet connection.

## Switch to MegaETH

Kumbaya runs on **MegaETH**. The first time you do anything that requires a transaction, your wallet will prompt you to add and switch to the network. Approve the prompt — that's it.

If you want to add it manually:

| Field               | Mainnet value                     |
| ------------------- | --------------------------------- |
| **Network name**    | MegaETH                           |
| **Chain ID**        | `4326`                            |
| **RPC URL**         | `https://mainnet.megaeth.com/rpc` |
| **Currency symbol** | `ETH`                             |
| **Block explorer**  | `https://mega.etherscan.io/`      |

For testnet (chain ID `6343`), use `https://carrot.megaeth.com/rpc` and the testnet explorer.

## Get some ETH

You'll need a small amount of ETH on MegaETH to pay for gas. Most actions cost a tiny fraction of a cent thanks to MegaETH's design.

* **Bridge from Ethereum mainnet** using [**Rabbithole**](https://rabbithole.megaeth.com/bridge), the official MegaETH bridge.
* **On testnet**, grab free ETH from the [MegaETH testnet faucet](https://testnet.megaeth.com).

Once you've got a balance, you're ready to [**make your first swap →**](/trading/swap.md).

## Disconnecting

Click your address in the top-right corner of the app, then **Disconnect**. Your wallet stays — you're just signing out of this session.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kumbaya.xyz/getting-started/connect-your-wallet.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
