Cgpt setup is wallet Connection and Token Access Verification

Cgpt setup is the process of linking one EVM wallet to ChainGPT, selecting BNB Chain or Ethereum and matching the CGPT contract before token access. The connection exposes a public address for balance checks; it doesn't transfer tokens. A transaction begins only when the wallet signs an on-chain action, and the selected network must also hold its native gas asset: BNB on BNB Chain or ETH on Ethereum Mainnet.

Connecting one address to the ChainGPT session

ChainGPT starts a Cgpt setup by requesting an EVM address, then the wallet asks which account the application may view during the session.

Open ChainGPT, choose Connect Wallet and select an EVM route such as MetaMask or WalletConnect. The wallet then shows its own account selector, so the application never chooses an address silently. Approve only the address intended for CGPT activity. After connection, compare the shortened address in ChainGPT's header with the first and last characters shown in the wallet. A clean setup keeps that same account active while the dashboard reads balances, membership state or staking eligibility. The session stays off-chain until a later prompt requests a signature or transaction.

Connection and authorization are separate checkpoints. The first shares an address; the second proves control.

A message signature may establish login without paying gas because it isn't broadcast. By contrast, an approval, stake or transfer changes chain state and appears in the wallet as a transaction. Read the prompt label before confirming, then check the selected account again. This sequence separates connection, authentication and the first CGPT transaction.

Which network should hold CGPT?

CGPT belongs on BNB Chain for the native token path, while Ethereum holds the bridged ERC-20 representation under a separate contract address.

BNB Chain Mainnet uses chain ID 56 and pays gas in BNB; Ethereum Mainnet uses chain ID 1 and pays gas in ETH. Those identifiers separate state even though MetaMask can show the same 42-character account on both. A CGPT balance on one chain isn't readable from the other contract. If an exchange withdrawal or bridge delivery lands on Ethereum, switching to BNB Chain won't reveal it. The inverse also holds. A correctly formatted address can therefore still point to an empty balance. Match the network name, chain ID and contract address before proceeding.

ChainGPT identifies the BNB Chain deployment as native and the Ethereum deployment as bridged. ChainPort provides the documented return route from Ethereum to BNB Chain, but bridging creates a cross-chain operation rather than a wallet display change. Choose the destination from the activity you intend to perform, then fund BNB on BNB Chain or ETH on Ethereum Mainnet.

Matching the contract before importing CGPT

Contract verification matches the active network, the full token address and the 18-decimal setting before a wallet adds CGPT to its asset view.

On BNB Chain, the native CGPT contract is 0x9840652DC04fb9db2C43853633f0F62BE6f00f98. On Ethereum, the bridged contract is 0x25931894a86D47441213199621F1F2994e1c39Aa. Both report 18 decimals, which means 1 CGPT maps to 10 ¹⁸ base units. MetaMask should populate the ChainGPT name, CGPT symbol and decimal field after the correct address is pasted. A different network queries a different contract namespace, even when the displayed account remains unchanged.

An EVM address contains 20 bytes, displayed as 40 hexadecimal characters plus the two-character 0x prefix. The complete text therefore occupies 42 characters. EIP-55 preserves the 40-digit length while using mixed case for about 15 checksum bits; a random typing error has a 0.0247% probability of passing that checksum. Preserve that 42-character string when comparing addresses.

Wallet connection options and signing control

Wallet choice changes where signatures happen, yet ChainGPT receives the same public EVM address and session permissions from each supported connection route.

MetaMask, Trust Wallet and Rainbow keep transaction approval inside their wallet interfaces. WalletConnect supplies a communication protocol for another compatible wallet, including mobile apps reached through a QR session. In all four routes, ChainGPT receives the selected public address and requests signatures; it doesn't receive the private key. The practical difference is the screen or device where the holder reviews the request.

A desktop session might use MetaMask directly, while a mobile holder reaches the same ChainGPT request through WalletConnect and approves it inside Trust Wallet.

Gas assets and transaction sequencing

At that point, CGPT transactions use the active chain's native asset for gas, so BNB funds BNB Chain actions and ETH funds transactions on Ethereum.

On both EVM networks, gas measures computation separately from the CGPT amount. One ETH equals 10 ¹⁸ wei, while 1 gwei equals 10 ⁹ wei. BNB Chain also uses an 18-decimal native-unit scale. A plain native transfer to an externally owned account has an intrinsic cost of 21,000 gas. CGPT transfer and approval calls execute contract code, so the wallet estimates a higher gas limit for them.

Final cost multiplies gas used by the effective per-gas price. Ethereum pricing incorporates the block's base fee and a priority fee, while the submitted fee cap limits what the sender accepts. BNB Chain likewise quotes a network gas price in BNB units. The token balance can be sufficient while the native balance is too low, so check BNB or ETH before the first CGPT approval.

How does the wallet verify token access?

The wallet verifies CGPT access in two layers: a connection exposes the selected public address, while an on-chain approval authorizes a named contract.

Connecting costs 0 gas and creates no ERC-20 allowance. ChainGPT can read the account's balance through balanceOf, a view call. ERC-20 defines 6 core methods - totalSupply, balanceOf, transfer, transferFrom, approve and allowance - plus 2 required events. Its 3 metadata methods, name, symbol and decimals, are optional in the standard, although both CGPT deployments expose the metadata a wallet needs, as documented in Guide to cgpt examples.

When an application needs CGPT, the wallet shows a spender address, an amount and a network. Confirming approve writes that allowance to the token contract. A later ChainGPT contract uses transferFrom only within the recorded limit. Reading a balance, signing a login message and granting a token allowance are three separate operations.

Allowance control before staking or conversion

ERC-20 allowance control sets how many CGPT units a specific contract may move, and the permission remains recorded until its value changes.

The allowance parameter is a uint256, a 256-bit unsigned integer. An exact-value approval caps the spender at the entered amount; setting the value to 0 overwrites and removes the remaining allowance. When an interface follows the standard approve -then- transferFrom pattern, the first action involves 2 transactions: one records permission and one performs the stake, conversion or other contract call. Reconnecting the same wallet doesn't erase a sufficient allowance because the token contract stores it on-chain.

Disconnecting ends the application session, while revocation changes the allowance record. Keep those controls separate. ChainGPT Credits, written as CGPTc, add another irreversible state choice: converting CGPT into CGPTc is a one-way action, and the credits don't convert back into CGPT. Review the amount before creating CGPTc.

Reading confirmation from explorers and the dashboard

Explorer verification proves whether a CGPT transaction reached the intended chain, contract and account without relying on the wallet's token display alone.

An EVM transaction hash contains 32 bytes and appears as 64 hexadecimal digits after the 0x prefix, making 66 displayed characters. A transaction receipt records status 1 for success or 0 for failure. For a CGPT transfer, the ERC-20 Transfer event carries 3 fields: sender, recipient and value; the first 2 are indexed. These fixed structures let BscScan and Etherscan decode the same transaction components on their respective networks.

Search the hash on BscScan for BNB Chain or Etherscan for Ethereum, then compare the recipient, token contract and event value. The ChainGPT dashboard should reflect the same address after its interface refreshes. Explorer status settles the on-chain question, while the dashboard confirms application-level recognition through the completed CGPT Transfer event.

Recovering a missing balance without moving funds

A missing CGPT balance is usually a display or network-selection mismatch when the explorer already shows the correct token balance for the address.

Select the chain where the transaction settled, open the wallet's custom-token control and paste the matching CGPT contract. Importing a token costs 0 gas because it changes only the local asset list; it neither transfers CGPT nor alters the blockchain. If the relevant explorer reports a balance, the account owns those units even before the wallet renders them. If it reports zero, compare the transaction's network, recipient and token contract, then refresh ChainGPT with the same 42-character account selected.

Edge cases across bridges, accounts and mobile sessions

Bridge, account and mobile-session edge cases all reduce to one rule: each chain keeps separate token state even when the EVM address matches.

Ethereum's CGPT contract represents bridged tokens, while the BNB Chain contract represents the native deployment. ChainPort is the documented return route from Ethereum to BNB Chain. A bridge action changes balances through its own contracts and messages; selecting another network in MetaMask only changes the ledger the wallet displays. Gas is required on the chain where each submitted transaction executes, so destination planning includes both CGPT location and the matching native asset.

Account switching creates a second boundary. An allowance links 2 addresses - the owner and spender - inside 1 token contract, so another account has its own balance and permission state. A smart contract wallet also follows its contract's signature policy rather than the single-key path of an externally owned account. ChainGPT reads whichever address the wallet exposes for the active session.

On mobile, WalletConnect carries requests between ChainGPT and the chosen wallet. Closing or disconnecting that session stops new requests through the connection, but it leaves completed transactions and allowances on-chain. Hardware-backed accounts connected through MetaMask add device confirmation to the same EVM flow. Finish by matching the active address, chain ID and CGPT contract before confirming the contract call.

Helpful answers