PXAHUB
Skip to article
User guide
Guide navigation

PXT and staking

Prepare PXT: from a DEX to an available balance

Check the required permission, official swap entry, bridge direction and platform credit before staking.

Updated

On this page

Start with the permission you need

Read staking levels and permissions first. PXT is used for staking permissions. PAT is a different token; buying PAT does not give you a PXT staking level. Holding PXT and staking PXT are also different states. Ordinary posts currently do not require staking.

  1. 1Check your target and existing balance
  2. 2Swap for PXT on a DEX
  3. 3Verify bridge and platform credit
  4. 4Stake and check permissions

Step 1: install MetaMask if you do not have a wallet

MetaMask manages on-chain assets; PXAHub is the publishing and review site; PancakeSwap is a decentralized exchange (DEX). They are separate account systems. Signing into PXAHub with Google does not automatically create a funded MetaMask wallet.

  1. Open the official MetaMask download page. Use its browser-extension entry on a computer, or its official app-store links on a phone.
  2. Create a wallet if this is your first one. For an existing wallet, use the official recovery or import flow. A newly created address does not automatically receive your old assets.
  3. Set your unlock password and recovery method as shown. If using a recovery phrase, keep the original phrase offline. If choosing an available social recovery method, follow the official instructions to protect the associated account and password. Your PXAHub password is separate.
  4. Find and copy your complete receiving 0x address. A receiving address can be shared; your recovery phrase, private key and unlock password must never be given to a website, operator or support agent.
  5. On a phone, you can open the DEX in MetaMask's built-in browser. With an external browser, use the MetaMask/WalletConnect option actually offered and return to the page after wallet confirmation.

Done when: you can open your wallet and identify its network and full receiving address. Installing a wallet does not give it tokens. Screens vary by version; see MetaMask's wallet creation guide.

Step 2: select BNB Smart Chain mainnet

Select BNB Smart Chain / BNB Chain in the wallet network picker. If missing, use Add network and check BNB Chain's official configuration. For manual mainnet setup:

  • Network name: BNB Smart Chain; chain ID: 56.
  • RPC: https://bsc-dataseed.bnbchain.org.
  • Fee currency: BNB; explorer: https://bscscan.com.

Do not select testnet chain ID 97 or opBNB. The same 0x address can exist on different networks without its assets automatically moving between them.

Done when: the wallet shows BNB Smart Chain mainnet. Buying PXT starts on this chain, separately from later operations on PXA Chain.

Step 3: fund the wallet for the swap and network fees

A DEX exchanges one on-chain asset for another. This swap flow is not a direct bank-card purchase of PXT. You need a supported payment asset and BNB for network fees. Paying for PXT with USDT still requires BNB. Leave some BNB for fees instead of swapping it all.

If you already hold assets in another wallet or exchange, select BNB Smart Chain in MetaMask and copy your receiving address. On the sending service choose its supported BNB Smart Chain / BSC / BEP-20 withdrawal network. Check the asset, address, amount, fees and network; first verify a small receipt. Do not select Ethereum, Tron, opBNB or testnet. An exchange account balance does not automatically appear in MetaMask.

If you have no on-chain assets, check the funding options MetaMask actually offers in your region, or use a service available to you to obtain BNB/payment assets and withdraw on the matching network. Payment methods, identity checks, minimums and fees depend on that service. PXAHub does not collect fiat or require payment to an operator to buy for you.

Done when: MetaMask shows the received BNB and payment asset on BNB Smart Chain. A withdrawal request, completed payment and wallet receipt are separate stages. See MetaMask's transfer guide for context; its example network must not replace the BNB Smart Chain network required here.

Verify the network and token

The project's DEX purchase route uses PancakeSwap on BNB Smart Chain. Open the official swap page and check its domain, network and output token contract. Do not identify PXT by its name alone.

The BNB Chain PXT contract recorded in the project's formal issuance record is 0xeA141BD8e87f6C08B141e759545020d49Ee826FE. See its BscScan token page. This is a BNB Chain token address, not a PXA Chain staking contract or your platform deposit address. Recheck it against the official wallet entry before proceeding.

Swap on the decentralized exchange

  1. Select BNB Smart Chain in your wallet and prepare the payment asset and BNB for network fees.
  2. Select your payment token and the PXT contract you have verified.
  3. Enter your intended amount. Check expected output, price impact, minimum received, route and fees. Account for your existing balance and target level; the staking threshold is not a fixed purchase price.
  4. If approval is required, inspect the spender and allowance. Then review the swap and confirm it yourself in your wallet.
  5. Wait for the swap transaction to succeed and verify your actual PXT balance on the same network. An approval alone does not complete the swap.

See PancakeSwap's official swap explanation. Quotes and fees are those displayed at execution. Understand any risk notice before deciding; do not blindly dismiss it or keep increasing slippage. This guide does not promise a token price, liquidity or investment return.

Step 4: connect the DEX and verify the swap result

On the official PancakeSwap page above, choose Connect Wallet, then MetaMask, and connect only the account you intend to use. Match the displayed address to MetaMask and keep BNB Smart Chain selected. Connecting is not a purchase and never requires entering your recovery phrase.

Choose your payment token. In the receiving-token picker, paste the complete PXT contract from this page and verify the result. Quotes depend on actual pools. Stop and check if there is no quote, no route, or insufficient assets/BNB; do not send money to an unfamiliar address to “buy tokens.” Follow the approval and swap steps above, reviewing what you spend and receive before confirming.

Afterward, open the transaction from wallet activity and verify success on BscScan. If PXT is hidden, use Import tokens / Custom token on BNB Smart Chain, supplying this page's PXT contract and checking symbol PXT and decimals 18. Importing displays existing assets; it does not buy or move them. The official PXA Chain token page also distinguishes assets by chain.

Done when: the swap succeeded and the same BNB Smart Chain address has a higher actual PXT balance. A connected wallet or successful approval is not enough.

Step 5: add PXA and check whether the next step is open

For PXA, use the network entry on the official PXA Chain transfer page. Check chain ID 784, native fee currency PXA, RPC https://rpc.pxachain.com, and explorer https://explorer.pxachain.com. Adding a network does not move your BNB Chain assets.

PXT is the permission token, BNB pays BNB Smart Chain fees, and native PXA pays PXA Chain fees. They are not interchangeable. BSC PXT and its corresponding PXA asset also have different contracts; do not reuse the BSC address on PXA. Read the bridge guide and check the public bridge. It remains closed, so new users must wait here. An ordinary transfer cannot replace bridging, and you must not assume free PXA gas will appear automatically. Follow the fee-funding instructions published when the service opens.

Step 6: bind your own wallet to your PXAHub account

The current production flow uses a self-custody financial wallet, rather than requiring a deposit into an operator-held account. Sign into the PXAHub account you intend to publish or review with. Open qualification and wallet binding, then Manage financial wallet binding. Select PXA mainnet (784) and your intended address in MetaMask.

Connect, verify the full address, request binding, and read the binding message before signing. This is a message signature, separate from a purchase, token approval or on-chain stake. Binding alone does not spend tokens or on-chain gas. Verify the bound address afterward. The current qualification limit is one wallet per account; do not casually unbind or change it to troubleshoot a balance.

A DEX connection does not bind PXAHub. Logging into PXAHub with a wallet is not proof that financial binding is complete either. Check the same bound address for purchasing, bridge receipt and staking. If a different address is already bound, establish which account and wallet you intend to use before moving assets.

Done when: the qualification/staking page shows the correct bound wallet. Native PXA gas claims are currently paused; do not assume binding gives you free gas. Users with PXA-side assets and gas can continue; users needing a new bridge transfer must wait for the public entry to open.

Move from a purchase balance to a usable balance

BNB Chain PXT and the platform balance used on PXA Chain are different. When a bridge is required, enter through the official bridge entry, select BNB Chain → PXA Chain, and verify PXT, the destination network and a receiving wallet you control. The bridge may default to the reverse direction. Wait for both source and destination completion before continuing.

Open the PXAHub wallet and staking management. Match the bound address, network, actual PXA-side balance and staked amount. The current self-custody flow does not require another deposit into an operator-held address. After receipt at your own bound PXA address, do not transfer again merely to obtain “platform credit.” A balance-reading error calls for checking chain records, not another deposit.

Continue once the balance is ready

Open staking management, verify the account, available balance and conditions, and follow the staking guide. Avoid duplicate submissions. For problems, record the transaction hash, network, time and circumstances and use feedback. Never share private keys or seed phrases.