Cgpt staking links pool multipliers and lock terms to tier points

Tier points connect a locked stake to participation benefits

Recognized staking points, also called CGPTsp, establish a ChainGPT Pad tier, while each campaign sets the participation conditions and reward rules. The tier names are Bronze, Silver, Gold and Diamond. A wallet below the entry threshold has no tier. Standard tiered initial DEX offerings (IDOs) use tier eligibility and allocation weight when determining participation. A larger point balance can improve that weight within the applicable rules. It does not purchase the sale tokens or complete registration. Those actions have their own requirements, including identity verification and regional eligibility for Standard IDOs.

Subscription Public Sales use a different allocation model. Staking and a tier are optional, while identity verification and regional eligibility are required. Points can provide an allocation boost or lower fees when the campaign enables those benefits. Such sales finalize allocations after the sale ends. A staking multiplier therefore cannot be read as a guaranteed multiple of tokens received. The allocation calculation also uses the sale’s rules and other participants’ commitments.

Do longer locks always produce more tier points?

Longer locks usually produce more points for the same CGPT amount, provided the selected pool applies a higher multiplier. A pool’s staking points equal the CGPT amount staked multiplied by that pool’s point multiplier. Duration influences which pool terms apply; it is not an extra factor multiplied into that formula. With unchanged principal and multiplier, elapsed days alone do not multiply the point balance again. Changes in the amount recognized as staked can change the calculation.

Pool designs can give equal lock durations different multipliers. Read the duration and multiplier together on the selected pool. The available options can change, so a remembered duration-to-multiplier pairing may describe another pool. For a point target represented by T and a multiplier represented by m, T divided by m gives the required CGPT amount before any pool minimum or rounding rule.

The withdrawal date sets the commitment boundary

A longer lock commits the staked tokens until the position’s applicable unlock time, even if the point benefit becomes useful sooner. Locked CGPT cannot fund another transaction during that period. Token prices can change while withdrawal remains unavailable. A campaign may also impose registration dates or snapshots within that lock. Qualifying for its tier does not automatically satisfy its timing requirements.

An accidental stake still carries its lock. A higher tier does not create an early withdrawal right.

Before committing, compare the actual lock with the period during which you need the tokens available. Early withdrawal is not a standard remedy for a mistaken deposit. Any exceptional withdrawal feature would need to be explicitly supported by that particular pool. A token-sale refund policy applies to the sale commitment; it does not cancel the separate CGPT staking lock.

Prepare the staking wallet and transaction funding

ChainGPT Pad’s CGPT staking pools operate on BNB Chain, also called BSC, and their transactions require BNB for gas. The wallet needs usable CGPT on that network, a supported connection and enough BNB for the transaction requests it approves. CGPT held on another network does not supply this pool’s staking balance. Confirm the selected wallet address before choosing a pool. That address identifies the position, so connecting a different account can hide a valid existing stake. Keep the pool’s duration, multiplier and reward terms together when reviewing the proposed deposit.

Open full-size image

Confirm the stake separately from wallet authorization

A wallet signature, token approval or transaction identifier alone does not establish a completed CGPT stake. Connection permits the application to interact with the wallet. An authentication signature may establish control of the address. A token approval, when requested, permits a specified contract to spend an authorized amount. The staking operation establishes the position under the selected pool’s rules.

Inspect what each wallet request authorizes, including its network, token amount and recipient contract. The interface may present authorization and execution through different requests; do not assume every wallet requires an identical transaction count. A submitted request can remain pending or fail. Read its outcome and the resulting staking position before treating the point calculation as available participation weight.

ChainGPT Pad displays the wallet’s points and tier. The usable total can include adjustments for existing positions, delegation or rentals.

An unrecognized stake before campaign registration

In this hypothetical example, a wallet submits a stake of 7 436 CGPT into a selected 2x pool. It has no other staking points. After submission, the staking page shows no position because its connection is reading the wrong network.

The expected contribution is 7 436 multiplied by 2, or 14 872 staking points. ChainGPT Pad uses that point total to determine the wallet’s tier. It does not mean the wallet owns 14 872 CGPT or has received a token reward. The stake record must identify the original CGPT amount and the chosen pool before the point total can support further participation.

Open full-size image

Inspect the transaction status, then reconnect the staking wallet on the pool’s required network. These checks do not create another deposit or change the lock. If the transaction is pending, wait for its outcome before considering another submission. If it failed, resolve the failure before attempting a stake again. Check that the successful transaction records a stake in the selected pool.

Here, the stake transaction succeeded. Correcting the connection and refreshing the display reveals the 7 436 CGPT position and its 14 872 points. The wallet can now use the recorded balance when assessing campaign eligibility. If the position or points remained unresolved, registration decisions would have to wait; submitting another stake would not establish what happened to the first deposit.

Points from separate pools contribute to one tier

ChainGPT Pad adds the point contributions from a wallet’s separate staking pools. Calculate each contribution using its own CGPT balance and multiplier, then add them together. The combined tier does not merge the pools’ withdrawal schedules. A position reaching its unlock time does not release another position whose lock remains active. Delegation and point rentals can also affect the points available for benefits. Compare points generated by your own deposits with the usable balance shown for the wallet, especially when some points have been assigned elsewhere.

Open full-size image

Adding tokens changes the V2 lock calculation

Adding CGPT to a V2 stake extends its lock proportionally to the amount added. This differs from assuming every addition restarts a full lock period. The existing unlock date also cannot be assumed to remain unchanged. An addition changes both the staking amount and the withdrawal commitment. Evaluate the applicable pool terms before approving it, then retain the updated unlock time with the position record.

The proportional re-lock rule belongs to the V2 staking implementation. A similarly named action in another contract needs its own terms. If the interface does not explain the applicable extension sufficiently, leave the addition unsigned. Increasing the point balance is useful only if the resulting lock still fits the participation period and token availability you need.

Does migrating to V2 restart the staking lock?

The V1-to-V2 migration is designed to preserve the existing lock term and unlock date, subject to successful execution and applicable migration terms. It moves the position into the corresponding V2 pool on the same network. Preservation also covers the staked amount on a one-to-one basis. Recognized accrued or pending rewards follow the migration mechanics, while normal staking activity and campaign calculations can still affect points.

Migration and adding CGPT are different operations. The migration itself is intended to avoid a fresh lock; a later stake addition follows V2’s re-lock rule. Wallet configuration and the available migration flow determine whether execution needs one transaction or several steps. An authorization request should not be mistaken for evidence the V2 position already exists.

An eligible V1 position may need completed migration to V2 before its points count for future benefits or campaign snapshots. Migration does not register the wallet for an IDO or giveaway. Each campaign retains its eligibility requirements.

Point-focused pools and token-reward pools serve different goals

A pool can award staking points while offering 0% annual percentage yield (APY) on the staked tokens. Point-focused pools and pools offering token yield have distinct reward terms. A larger point multiplier does not establish a larger token payout. When token rewards are part of a pool, use its stated reward basis and claim conditions to interpret the amount. An annualized percentage describes a rate over a year; it does not mean that percentage of principal becomes immediately withdrawable.

Pool availability and reward rates can change independently of the point formula. Read any displayed annual percentage rate (APR) or APY alongside its label and applicable terms. Membership access to AI tools follows separate access rules. AI credits fund paid tool requests, while staking points establish eligible membership benefits. Locking more tokens does not make the point balance a spendable credit balance.

How do I withdraw CGPT when the lock ends?

Once the position’s lock ends, use the staking interface to unstake with the wallet holding that position. In a time-locked CGPT pool without an early-withdrawal provision, withdrawal becomes available only after the lock term ends. Transaction funding is still necessary when the wallet submits an on-chain withdrawal. Keep the recorded unlock time distinct from the date you first requested or viewed unstaking. An interface error does not establish that the contract position disappeared. Inspect the existing position, transaction outcome and returned CGPT balance before treating the withdrawal as complete or repeating a request. Withdrawal belongs to the original staking wallet; point delegation does not redirect its CGPT.