Cgpt
Cgpt is a Utility Token That Converts Into Platform Credits
Cgpt is a one-way conversion workflow inside the ChainGPT application: connect the Web3 wallet holding CGPT, open the CGPTc balance control, enter the token amount and review both the CGPT debit and CGPTc credit before confirming. Once the wallet action settles, the token amount leaves the source balance and the resulting credits appear in the dashboard account. The credits carry a fixed $0.01 unit value and can't be converted back into CGPT.
On this page
In short: It is a utility-token conversion workflow that requires a connected Web3 wallet, previews CGPT and CGPTc amounts before confirmation, then records irreversible credits in the dashboard balance.
Opening the credit balance and setting the source amount
The CGPT credit conversion starts from the CGPTc balance control, where the ChainGPT dashboard opens the amount-entry modal and displays the connected wallet account and token balance.
After connecting through MetaMask, Trust Wallet, Rainbow Wallet or WalletConnect, look near the account settings at the top right of the dashboard. The CGPTc control displays the account's opening credit balance. Selecting it opens the conversion modal. Enter the CGPT source amount and let the interface calculate the credit output. Keep the modal open while checking the wallet address, selected network, available token balance, CGPT debit and CGPTc credit. All five fields describe one pending decision, so a mismatch should stop the flow before the wallet receives a transaction request.
For Cgpt conversion, the useful sequence is connect, open the balance control, choose the source amount, inspect the preview and then confirm through the wallet. It preserves a visible quote, unlike beginning from an isolated wallet screen.
Wallet and network prerequisites before the quote
The wallet prerequisite for CGPT conversion is an account linked to ChainGPT, holding CGPT on a supported network and enough native currency for execution fees.
CGPT has two EVM token deployments relevant to this route. BNB Smart Chain uses chain ID 56, the BEP-20 token and BNB for transaction fees. Ethereum uses chain ID 1, the ERC-20 token and ETH for fees. Both CGPT contracts expose 18 decimal places, making one whole token equal to 10^18 base units, although the interface handles that scaling. MetaMask, Trust Wallet and Rainbow Wallet can present these EVM accounts, while WalletConnect pairs a compatible wallet session. Matching the account and chain matters more than repeatedly refreshing a balance on the wrong network.
Reading the CGPT and CGPTc preview
The conversion preview pairs a live CGPT input with a fixed-value CGPTc output, giving the reader the two amounts needed for the final confirmation decision.
From there, CGPTc keeps a fixed usage denomination of $0.01 per credit. That makes 100 CGPTc equal to $1, 500 CGPTc equal to $5 and 1,000 CGPTc equal to $10. The CGPT side of the preview moves with the token quote used by the interface, so the source amount isn't a permanent conversion ratio. Read the current pair as a single quote rather than combining an old token price with a fresh credit amount.
The units serve different jobs in the decision. The first shows how many CGPT tokens the wallet will spend; the second shows how much ChainGPT usage balance the account will receive. The paired preview is stronger than an estimate made from a price viewed elsewhere.
Fixed parameters behind the conversion
Three fixed parameters anchor the CGPT credit conversion inside the dashboard: token precision, EVM address format and the single permitted conversion direction for account credits.
| Parameter | Fixed value | Decision impact | Standard count |
|---|---|---|---|
| CGPT token precision | 18 decimal places | Keeps wallet and contract amounts aligned | 10^18 base units per token |
| EVM address format | 20-byte address | Identifies the connected account and contracts | 40 hexadecimal digits, or 42 characters with 0x |
| Conversion direction | CGPT to CGPTc | Makes confirmation final | 1 permitted direction |
| Together these parameters define the source amount, account identity and final state. | 3 fixed checks | ||
One CGPTc carries $0.01 of fixed usage value, so 100 CGPTc represents $1 across the ChainGPT credit system. The source quote can move while those credit units stay stable. A 1-way conversion leaves 0 reverse routes in the interface, making the preview the last place to change the amount. These fixed checks turn a variable token quote into a precise account-credit decision, which is discussed in Cgpt setup for beginners fundamentals.
Approval and conversion as separate wallet actions
The wallet approval and the credit purchase are separate CGPT conversion actions when the selected account hasn't already granted enough token allowance to the purchase contract.
BEP-20 and ERC-20 allowances let the credit-purchase contract request the entered CGPT amount from the wallet. With no sufficient allowance, the wallet first displays an approval using the 4-byte ERC-20 method selector 0x095ea7b3. The app then requests the purchase transaction. A first conversion therefore uses 2 on-chain confirmations in this state, while a later conversion uses 1 when the existing allowance covers the amount. Each request has its own network fee and transaction hash.
An approval alone produces no CGPTc. If the approval settles and the purchase isn't submitted, the CGPT stays in the wallet while the allowance remains available under its recorded limit. Reopen the balance modal, obtain a fresh preview and submit the purchase without repeating an adequate approval. When a wallet displays an unlimited allowance, that permission stays active until it's changed. Separate receipts provide clearer evidence than counting wallet popups.
What changes after the conversion is confirmed?
Confirmed CGPT conversion changes two balances: the wallet's token balance falls by the submitted amount and the ChainGPT account gains the quoted CGPTc credit amount.
The purchase contract pulls the approved CGPT amount, and the wallet pays the network fee in BNB or ETH. ChainGPT then records the quoted CGPTc against the connected dashboard account. The credit total appears near the account settings rather than as another BEP-20 or ERC-20 token inside the wallet. Its unit remains $0.01 after conversion, even though the market value of the CGPT spent for it moves. A settled credit entry therefore represents usable ChainGPT balance, while unconverted CGPT remains an on-chain wallet asset.
Dashboard balance verification after settlement
Dashboard balance verification compares the recorded CGPTc total with the previewed credit output after its purchase transaction reaches a visible successful status in the on-chain receipt.
Note the opening CGPTc balance before confirming, then reopen the same balance control after settlement. The expected total equals the opening balance plus the quoted output, minus any credits consumed between those observations. This check uses 3 figures and catches a stale interface reading without guessing from the CGPT wallet balance. A 250-CGPTc increase carries $2.50 of usage value, while a 2,500-CGPTc increase carries $25. If the account was reconnected, confirm the dashboard still shows the same EVM address used for the purchase.
Once the arithmetic matches, don't submit the conversion again. The balance equation gives better account-level proof than the wallet's CGPT decrease by itself.
On-chain receipt checks when the balance lags
An on-chain receipt separates transaction settlement from a delayed ChainGPT dashboard refresh, letting the user confirm execution before changing wallet settings or repeating the purchase.
Copy the purchase transaction hash from the wallet. Use Etherscan for Ethereum or BscScan for BNB Smart Chain. An EVM transaction hash contains 32 bytes, shown as 64 hexadecimal digits or 66 characters including the 0x prefix.
Read the receipt status, sending account, destination contract and token movement. Receipt status 1 means execution succeeded; status 0 means it didn't apply the requested state change. Match the sending account to the address shown in ChainGPT before interpreting the credit balance. The purchase receipt matters more than an earlier approval receipt because only the purchase creates the credit claim.
A successful receipt paired with an old dashboard total points to a session or display delay. Reconnect the same address and refresh the balance control once. A finalized receipt is stronger evidence than a lingering wallet label.
Recovering a missing CGPT balance
A missing CGPT source balance most commonly means the connected wallet account or network differs from the account and chain holding the on-chain tokens in question.
Close the modal before signing anything. Compare the shortened dashboard address with the account selected in MetaMask, Trust Wallet or Rainbow Wallet, then select the chain holding CGPT. BNB Smart Chain must report chain ID 56 and Ethereum must report chain ID 1. Reconnect ChainGPT and reopen the CGPTc balance control. If the wallet needs a manual token entry, an EVM address has 40 hexadecimal digits and 42 characters with its 0x prefix. Keep BNB or ETH available for the matching network fee. Correcting the session alignment is more direct than transferring tokens to another account.
One-way credits and the final amount decision
The final CGPT amount should cover only the CGPTc usage balance the account needs, because every confirmed conversion closes the route back to tokens permanently.
Translate the planned credit balance into its fixed unit before accepting the live CGPT quote. A 250-CGPTc output represents $2.50, 2,500 CGPTc represents $25 and 10,000 CGPTc represents $100 of usage value. Those relationships stay constant; the CGPT debit shown beside them is the time-sensitive part. If the output exceeds the intended balance, edit the amount in the modal before sending any wallet request.
At the last review, compare 4 items: connected account, selected network, CGPT debit and CGPTc output. Treat an allowance request as a separate action, then retain the purchase transaction hash and check the new dashboard total. The workflow finishes only when the receipt succeeds and the balance arithmetic agrees. A conversion limited to planned usage preserves more flexibility than converting the entire wallet balance.
Practical questions
Does converting CGPT into CGPTc require staking?
No, converting CGPT into CGPTc doesn't require staking. The ChainGPT dashboard supports pay-as-you-go credits through the connected Web3 wallet, while staking belongs to separate membership and launchpad functions. The conversion still requires CGPT in the selected account, the correct supported network and enough BNB or ETH to pay the network fee generated by the wallet transaction.
Which asset pays the gas for a CGPT credit purchase?
BNB pays the network fee on BNB Smart Chain, while ETH pays it on Ethereum. The fee comes from the same connected wallet account submitting the approval or purchase transaction. CGPT itself supplies the conversion amount, not the gas payment. If the flow needs both an allowance approval and a credit purchase, each on-chain action carries its own fee under the selected network's conditions at the moment of submission.
Are CGPTc balances shared across connected wallet accounts?
CGPTc balances belong to the ChainGPT dashboard account created from the connected wallet address. They aren't pooled across every account visible inside MetaMask, Trust Wallet or Rainbow Wallet. Switching the selected EVM address changes the account context the dashboard reads. Reconnect the address used for the purchase before deciding a successful conversion failed to update in that account.
When does a converted CGPTc balance expire?
The conversion workflow assigns no published expiry period to CGPTc acquired from CGPT. The dashboard presents converted credits as the account's available usage balance, while promotional or membership balances follow separate refill rules. Disconnecting a wallet doesn't create an expiry event. Track the converted amount in the same dashboard account instead of assuming every monthly membership cycle resets purchased credits automatically unless a clearly stated program rule explicitly says so.
Could an unsigned conversion preview change the CGPT wallet balance?
No, an unsigned conversion preview doesn't change the CGPT wallet balance or create CGPTc. The modal calculates both amounts before an on-chain instruction reaches the wallet. A state change starts only after the account signs and broadcasts an approval or purchase transaction. Closing the preview before those steps produces no transaction receipt and no dashboard credit entry at all.
Is the CGPT-to-CGPTc route available through the ChainGPT API?
The documented CGPT-to-CGPTc acquisition route runs through the ChainGPT application dashboard, while ChainGPT APIs consume credits already associated with the account. Connect the Web3 wallet, open the CGPTc balance control and complete the displayed conversion there. An API call doesn't replace the wallet approval or purchase transaction. After the dashboard balance updates, supported API usage draws down CGPTc under the pricing assigned to each function and request type for that connected account.