---
title: Swap NEAR: paid out as BEP-20 on BNB Smart Chain | Sablebolt
description: Swap NEAR for BTC, USDT or another coin — two addresses, no account. Here NEAR is a BEP-20 token on BNB Smart Chain: 0x address, BNB for fees.
url: https://sablebolt.io/coin/near-protocol
---

# Swap NEAR Protocol (NEAR)

NEAR is the coin of the NEAR Protocol network, where accounts have names like alice.near. On this site, NEAR is handled as a BEP-20 token on BNB Smart Chain: the payout goes to a 0x address, not to a NEAR account. Here you can swap NEAR for another coin, or get NEAR for what you hold — with two addresses and no account.

- **Price:** $4.68

- **24 h:** +1.15%

- **Market cap:** $6.13B

- **24 h volume:** $485.10M

- **Circulating:** 1.31B NEAR

- **Max supply:** No cap

Market data by CoinGecko

## NEAR on NEAR Protocol — the facts that matter for a swap

- **Shown here as:** NEAR

- **Address looks like:** 0x… (42 characters)

- **Confirmations we wait for:** 15

- **Typical arrival after you send:** ≈ 2–6 min

- **Fee token for later moves:** BNB

- **Extra field:** none

- **Issued by:** Binance (Binance-Peg)

- **Explorer:** [bscscan.com](https://bscscan.com/)

### Contracts

The contract was read directly from BNB Smart Chain on 12 October 2026 (name "NEAR Protocol", symbol NEAR, 18 decimals) and matches CoinGecko's listing of Binance-Peg NEAR Protocol. It is a pegged token issued by Binance, not the NEAR network's native coin. A token with the same name and a different contract is not it.

- NEAR Protocol`0x1Fa4a73a3F0133f0025378af00236f3aBDEE5D63`

## NEAR key facts — the numbers that do not change daily

- **Native chain opened:** 13 October 2020transfers enabled by validator vote; press coverage, not NEAR's docs

- **Native consensus:** Proof of stake, Doomslugsharded under Nightshade

- **Native block time:** about 600 msfinality about 1.2 s, per docs.near.org

- **Native smallest unit:** 1 yoctoNEAR = 10^-24 NEAR24 decimal places

- **Native accounts:** alice.near, 64-hex implicit, 0x…none of them accepted by the form

- **What this site handles:** Binance-Peg NEAR Protocol, BEP-20contract 0x1Fa4a73a3F0133f0025378af00236f3aBDEE5D63 on BNB Smart Chain

- **BEP-20 decimals:** 18read from the contract; the native coin has 24

- **BEP-20 supply:** about 12.95 million NEARtotalSupply of the peg contract; native supply about 1.31 billion

- **BNB Smart Chain block time:** 0.45 secondssince the Fermi hard fork, 14 January 2026

- **Confirmations the site waits for:** 15 on BNB Smart Chainabout 2–6 minutes

Checked on 14 October 2026: the peg contract's name, symbol, decimals and totalSupply were read from BNB Smart Chain through a public RPC (name "NEAR Protocol", symbol NEAR, 18 decimals); CoinGecko lists the same contract as Binance-Peg NEAR Protocol and gives the native supply; native block time, finality, account formats and yoctoNEAR come from the exchange-integration page at docs.near.org; the 0.45-second block time and the hard-fork dates from docs.bnbchain.org and the BNB Chain blog. The 13 October 2020 date is from press coverage of the mainnet vote, not from a NEAR document. The site's route data allows three seconds per confirmation, so the 2–6 minute estimate is conservative against the current block time.

## Which network should the NEAR arrive on?

- **Someone else is receiving.:** Ask whether they can receive NEAR on BNB Smart Chain. If they can, you need their 0x address (42 characters). A NEAR account name such as alice.near, or a 64-character implicit account, cannot receive the payout from this site.

- **An exchange is receiving.:** Open the exchange's NEAR deposit page and look for a network choice. Pick BNB Smart Chain (BEP-20) and use the 0x address it shows. If the exchange offers only the NEAR network for NEAR deposits, do not use it as the receiver here.

- **Your own wallet is receiving.:** Use a wallet that holds BNB Smart Chain assets — any Ethereum-style wallet does. The NEAR token lands at your 0x address; to move it again you need a little BNB in the same wallet for the fee.

- **You hold native NEAR and want to swap it.:** The deposit side is also on BNB Smart Chain. If your NEAR sits in a NEAR-network wallet, it has to be moved to the BEP-20 form first — through an exchange that supports both networks, for example — before it can be sent to the deposit address here.

## How to swap NEAR

1. Choose the two sides. Open the form on the home page, pick NEAR as what you send, then what you want to receive — or the other way round when NEAR is what you want to end up with. There is no separate route page for NEAR yet.
2. Enter the amount. The estimate updates as you type and refreshes every 60 seconds. The minimum for the pair is shown under the field.
3. Paste the receiving address. For a NEAR payout the form checks for a 42-character 0x address — a BNB Smart Chain address. A name ending in .near is rejected, and that is intended.
4. Send the deposit and follow it. You get a one-time deposit address on BNB Smart Chain. Send the NEAR token there in one transaction; your wallet pays the BSC fee in BNB. The status page shows each stage and both transaction hashes, and the BSC side can be looked up on BscScan.

## Before you send — checklist

- The receiving address is a 0x address on BNB Smart Chain, not a NEAR account name and not a 64-character NEAR implicit account.
- If an exchange is receiving, its NEAR deposit page is set to BNB Smart Chain (BEP-20).
- If NEAR is what you send, it is the BEP-20 token at the contract above, and the sending wallet holds a little BNB for the fee.
- The amount is sent in one transaction, from a wallet you control.
- The status link is saved.

## What a NEAR swap costs

- **The rate is floating.** The estimate follows the market and is fixed when your deposit confirms — after 15 confirmations on BNB Smart Chain, about 2–6 minutes.
- **The network fee for the payout** is shown in the form and already taken out of "You get". A BEP-20 transfer on BNB Smart Chain is cheap compared with Ethereum.
- **Sending the deposit** costs your wallet a BNB Smart Chain fee, paid in BNB. That fee is not part of the swap. A wallet holding the NEAR token and no BNB cannot send.

Small amounts cost more in percent, because the payout network fee is the same size for a small swap as for a large one.

## How NEAR works for a sender — on two chains — the native chain and the peg on BNB Smart Chain

NEAR on this site is not on the NEAR network. That sentence is the whole guide in short, and everything below explains it. The figures were checked on 14 October 2026 at docs.near.org, docs.bnbchain.org and against the contracts on BNB Smart Chain.

### The native chain, for reference

NEAR Protocol is, in its documentation's words, "a sharded proof-of-stake blockchain using Doomslug consensus", with Nightshade as the sharding design. Its exchange-integration page gives the pace: blocks "produced in ~600 ms, final in ~1.2 s". Amounts are counted in yoctoNEAR — 1 NEAR = 10^24 yoctoNEAR — and accounts have names (alice.near), 64-character hexadecimal implicit IDs, Ethereum-like 0x IDs and deterministic 0s IDs. The chain opened to transfers on 13 October 2020, after a validator vote; that date comes from press coverage, since NEAR's own docs do not record it.

None of this is where your swap happens.

### The chain this site uses

The form pays NEAR out as a BEP-20 token on BNB Smart Chain, and takes NEAR deposits there. The token is Binance-Peg NEAR Protocol at the contract 0x1Fa4a73a3F0133f0025378af00236f3aBDEE5D63; read from the chain it reports the name NEAR Protocol, the symbol NEAR and 18 decimals, and a total supply of about 12.95 million tokens — against roughly 1.31 billion native NEAR listed by CoinGecko. Binance issues it against native NEAR it holds, one to one, the same way it issues its pegged USDT on BNB Smart Chain. It carries NEAR's name and price; it moves with BNB Smart Chain's rules.

|  | What applies to a deposit or payout here |
|---|---|
| Network | BNB Smart Chain |
| Address | 0x…, 42 characters |
| Fee token | BNB, paid by the sending wallet |
| Decimals | 18 |
| Confirmations the site waits for | 15 |
| Explorer | bscscan.com |

### Blocks and confirmations on BNB Smart Chain

BNB Smart Chain's documentation gives its block time as approximately 0.45 seconds, reduced from 3 seconds through the Lorentz, Maxwell and Fermi hard forks — the last of them on 14 January 2026. The route data this site is built from waits for **15** confirmations on a NEAR deposit and allows about three seconds for each, which gives the 2–6 minute estimate on the status page. At today's block time fifteen confirmations pass in a few seconds, so most of those minutes are processing and the payout on the other network; the estimate is deliberately on the safe side.

### Fees

Every transfer of the token is a contract call on BNB Smart Chain, and the sending wallet pays for it in BNB. A wallet that holds the NEAR token and no BNB cannot send — the most common reason a NEAR deposit "will not go". The payout fee is the site's cost, shown in the form and already taken out of "You get"; [USDT network fees compared](https://sablebolt.io/blog/usdt-network-fees-compared) shows what a BEP-20 transfer costs relative to the other networks here.

**Native NEAR cannot reach the deposit address.** A NEAR-network wallet refuses a 0x destination, and an exchange withdrawal on the NEAR network goes to a NEAR account, not to BNB Smart Chain. If what you hold is native, it has to become the BEP-20 token first — the Addresses section explains how.

## NEAR addresses — the ones the form rejects, and the one it takes — alice.near, 64 hex, 0x

The NEAR network has the richest account model of any chain on this site, and the form accepts none of its formats. That is correct behaviour, not a gap. Formats were checked against docs.near.org on 14 October 2026.

| Format | Example shape | Belongs to | Form |
|---|---|---|---|
| Named account | alice.near, shop.alice.near | NEAR network | Rejected |
| Implicit account | 64 lowercase hexadecimal characters | NEAR network | Rejected |
| Ethereum-like NEAR account | 0x plus 40 hex characters, on NEAR | NEAR network | Rejected if used on NEAR; see below |
| Deterministic account | starts with 0s | NEAR network | Rejected |
| BNB Smart Chain address | 0x plus 40 hex characters, 42 in all | BNB Smart Chain | Accepted |

### The one that looks right and is not

The trap is the 0x form. NEAR's docs list Ethereum-like account IDs starting with 0x, created when someone signs in with an Ethereum wallet; a BNB Smart Chain address also starts with 0x and has the same 42 characters. The form checks the format, and both pass it. What the form cannot see is which network the wallet behind that address is set to. A payout goes to the address you give on BNB Smart Chain, always. If the address came from a NEAR-network wallet's Ethereum-style account, the token still arrives on BNB Smart Chain at that address — and the NEAR wallet will never show it, because it is on another chain. Whether you can recover it depends on whether you hold the key to that 0x address in an Ethereum-style wallet.

### What to give for a NEAR payout

1. **Your own wallet:** any Ethereum-style wallet, switched to BNB Smart Chain. Copy the 0x address from its Receive screen. If the token does not appear after the payout, add it by the contract above; bscscan.com shows the balance either way.
2. **An exchange:** open the NEAR deposit page and look for a network choice. Pick BNB Smart Chain (BEP-20) and use the address it shows. If the exchange offers NEAR only on the NEAR network, it cannot receive from here — the payout would be the BEP-20 token at a NEAR account that does not exist on BNB Smart Chain.
3. **Another person:** ask whether they can receive NEAR on BNB Smart Chain. If they answer with alice.near, the answer is no.

### What to send for a NEAR deposit

The deposit address the form shows is on BNB Smart Chain. Send the BEP-20 token from a wallet on that chain, with a little BNB for the fee. If your NEAR is native — in a NEAR-network wallet, or at an exchange that holds it on the NEAR network — move it first: deposit to an exchange that lists NEAR on both networks, withdraw on BNB Smart Chain to your own 0x wallet, then send from there. Exchanges deduct their withdrawal fee from the amount, so withdraw a little more than the swap amount.

### A memo?

No. Neither BNB Smart Chain nor the form uses a memo for NEAR. If an exchange's NEAR deposit page shows a memo, that page is almost certainly for the NEAR network, where exchanges often share one account and distinguish deposits by memo — a sign you are on the wrong network choice. [Memo, destination tag, payment ID](https://sablebolt.io/blog/memo-destination-tag-payment-id) covers the coins that do need one.

## Checking a NEAR transaction — on BscScan — not on a NEAR explorer

Because the token lives on BNB Smart Chain, both legs of a NEAR swap on this site are visible on bscscan.com, and the status page links there. A NEAR-network explorer such as nearblocks.io shows the native chain and will not find these transfers. Read on 14 October 2026.

### What a BscScan transaction page shows

A token transfer opens with the transaction hash, its status (success or fail), the block number and timestamp, and how many confirmations the block has. Then the sender, the contract called — the NEAR Protocol token at 0x1Fa4…5D63 — and a "Tokens transferred" line with the sending address, the receiving address and the amount in NEAR. Below are the value in BNB sent alongside (zero for a token transfer), the transaction fee in BNB, the gas price and gas used. The token's own page lists its name, symbol, decimals, total supply and every transfer.

### A deposit you sent

1. Copy the transaction hash from your wallet's activity list.
2. Open it on bscscan.com. Not found means the wallet has not broadcast it — a wallet that was switched to another network when you pressed Send is the usual reason, and then the transaction may exist on that other network instead.
3. Check "Tokens transferred": the token must be NEAR Protocol at the contract above, the destination the deposit address from the form, the amount what you entered. A token with the same name and another contract is not a NEAR deposit.
4. Watch the confirmations. The status page here updates when 15 are reached.

### A payout you received

1. Open the payout hash from the status page.
2. Find your address as the receiver in "Tokens transferred". The amount is "You get" from the form.
3. If your wallet shows nothing, check the network selector first — the token is on BNB Smart Chain — then add the token by contract. The token's balance for your address is on bscscan.com whether the wallet shows it or not; [Wallet shows zero after a USDT transfer](https://sablebolt.io/blog/wallet-shows-zero-after-usdt-transfer) walks through the same problem with another token.
4. Keep the hash.

### Reading the two sides of a native-to-peg move

If you moved native NEAR through an exchange before swapping, that move has two separate records: a NEAR-network transaction into the exchange, which nearblocks.io shows, and a BNB Smart Chain withdrawal out of it, which bscscan.com shows. They have different hashes and are not linked on any explorer. The swap here starts only with the second one. [What a block explorer shows about a swap](https://sablebolt.io/blog/what-a-block-explorer-shows-about-a-swap) and [Reading a swap status page](https://sablebolt.io/blog/reading-a-swap-status-page) are the general versions of this section.

## The mistakes that cost money with NEAR here

Almost every NEAR mistake on this site is the same mistake: treating the BEP-20 token as if it were the native coin. The table is ordered by how often it happens.

| Mistake | What happens | What to do |
|---|---|---|
| Giving a .near account for the payout | The form refuses it | Give a 0x address on BNB Smart Chain |
| Withdrawing from an exchange on the NEAR network to the deposit address | The withdrawal form rejects a 0x destination, or the exchange sends to a NEAR account that is not the deposit | Choose BNB Smart Chain (BEP-20) for the withdrawal |
| Payout to an exchange that lists NEAR only on the NEAR network | The token lands on BNB Smart Chain at an address the exchange does not watch | Check the deposit page's network list first; afterwards only that exchange can help |
| 0x address from a NEAR-network wallet | The payout arrives on BNB Smart Chain; the NEAR wallet never shows it | Use an Ethereum-style wallet's address; if it has happened, import the key into one, if you hold it |
| Sending with no BNB in the wallet | The transaction cannot be sent | Add a little BNB first |
| Sending a lookalike token | Not a NEAR deposit | Compare the contract with 0x1Fa4a73a3F0133f0025378af00236f3aBDEE5D63 |
| Exchange withdrawal fee taken from the amount | Less arrives than the form expects; payout is smaller, or the deposit is under the minimum | Set the withdrawal so that the amount arriving matches the form |

### The wrong-network payout, in detail

The form cannot tell from a 0x address which network a wallet will look at; it always pays on BNB Smart Chain. Three outcomes follow from the address you give. Your own Ethereum-style wallet: switch it to BNB Smart Chain and the token is there. An exchange that lists NEAR on BNB Smart Chain: credited after its own confirmation count. An exchange that lists NEAR only on the NEAR network, or a NEAR-network wallet's 0x account: the token is on chain at that address, provably, on bscscan.com — and whether anyone can spend it depends on who holds the key to that address on BNB Smart Chain. For an exchange that is the exchange's decision; for your own key it is a matter of importing it into a wallet that speaks BNB Smart Chain. [Sent USDT to the wrong network](https://sablebolt.io/blog/sent-usdt-to-the-wrong-network) is the same situation with a different token, and its decision tree applies.

### Native NEAR sent "to the deposit"

A NEAR-network wallet will not accept a 0x address as a destination, so this usually fails before anything leaves. The dangerous case is an exchange with a free-text address field: if it accepts a 0x string and sends on the NEAR network, the coins go to an Ethereum-like NEAR account with that ID — on the NEAR network, not on BNB Smart Chain, and nowhere near the swap. Only that exchange can trace it. Before withdrawing, the network selector must say BNB Smart Chain or BEP-20; if there is no such selector, that exchange cannot send to the deposit address.

### Lookalikes

BNB Smart Chain has no shortage of tokens named NEAR. The form's deposit address is watched for the one contract above, and nothing else counts. Your wallet shows the name a token claims; bscscan.com shows its contract. Compare before sending.

**One check prevents all of this.** Wherever a NEAR address or network is chosen — your wallet, an exchange's deposit page, an exchange's withdrawal page — it must say BNB Smart Chain, and the address must start with 0x. The word "NEAR" on its own is not enough.

## What changed, and when — for the peg and its chain — dated, with sources

Two histories matter here: NEAR's own, briefly, and BNB Smart Chain's, because that is where the token moves. Dates were read on 14 October 2026 from docs.near.org, docs.bnbchain.org and the BNB Chain blog; the one press-sourced date is marked.

| Change | Date | For a sender | Source |
|---|---|---|---|
| NEAR mainnet opens to transfers | 13 October 2020 | The native coin becomes transferable | Press coverage of the validator vote |
| NEAR blocks at ~600 ms, finality ~1.2 s | Current figure | Older docs said ~1 s and ~2 s | docs.near.org, exchange integration |
| BSC Lorentz hard fork: 3 s → 1.5 s blocks | 29 April 2025 | Confirmations come twice as fast | docs.bnbchain.org |
| BSC Maxwell hard fork: 1.5 s → 0.75 s | 30 June 2025 | — | BNB Chain blog |
| BSC Fermi hard fork: 0.75 s → 0.45 s | 14 January 2026, 02:30 UTC | Fifteen confirmations in under ten seconds | BNB Chain blog, docs.bnbchain.org |

**NEAR's own pace.** The exchange-integration page now says blocks are produced in about 600 ms and final in about 1.2 s; an earlier version of the same guidance gave about 1 s and 2 s. NEAR's docs do not date the change, so this page does not either. It matters only if you are moving native NEAR to an exchange before swapping: that leg is fast.

**BNB Smart Chain, 2025–2026.** The documentation's overview describes the block time as "approximately 0.45 seconds (reduced from 3s through the Lorentz, Maxwell, and Fermi hardforks)". Lorentz activated on mainnet on 29 April 2025 (BEP-520, phase one, 1.5 seconds); Maxwell on 30 June 2025 (BEP-524, 0.75 seconds); Fermi on 14 January 2026 (BEP-619, phase three, 0.45 seconds). For a deposit the effect is simple: the fifteen confirmations the site waits for take a few seconds instead of the forty-five they took at three-second blocks. The site's estimate still allows three seconds per confirmation, which is why the status page says 2–6 minutes rather than something shorter — the remainder is processing and the other network's payout.

**The peg contract.** Its creation date could not be read from a public BNB Smart Chain node on 14 October 2026 (state that old is not served by the nodes tried), so it is not given here. What can be read is its state today: 18 decimals and about 12.95 million tokens in supply, each one backed, by Binance's description of its pegged tokens, by native NEAR held one to one.

**What has not changed.** The token is still the BEP-20 at 0x1Fa4…5D63, it still needs BNB to move, and it is still not a NEAR account. Faster blocks changed the wait, not the rules.

## NEAR on its own chain next to NEAR as a BEP-20 token

Same name, same price, two different things. The site handles only the right-hand column; the left is here so that you can tell them apart. Checked on 14 October 2026 at docs.near.org and against the contract on BNB Smart Chain.

|  | Native NEAR | NEAR as BEP-20 (this site) |
|---|---|---|
| Lives on | NEAR Protocol | BNB Smart Chain |
| Issuer | The NEAR network — no issuer | Binance, against native NEAR it holds |
| Address | alice.near, 64 hex, 0x… or 0s… on NEAR | 0x…, 42 characters, on BNB Smart Chain |
| Smallest unit | 1 yoctoNEAR = 10^-24 NEAR (24 decimals) | 10^-18 of a token (18 decimals) |
| Fee token | NEAR | BNB |
| Block time | about 600 ms; final in about 1.2 s | 0.45 s; the site allows 3 s per confirmation |
| Supply | about 1.31 billion (CoinGecko) | about 12.95 million (contract totalSupply) |
| Explorer | nearblocks.io | bscscan.com |
| Can be frozen by an issuer | No | Depends on the issuer's contract and policies |
| Routes here | None — not handled | [NEAR](https://sablebolt.io/coin/near-protocol) in the form on the home page; no route page yet |

**What "pegged" means for you.** The token is a claim on native NEAR held by Binance; its price follows NEAR because Binance converts between the two at one to one for its users. On chain it is an ordinary BEP-20 contract with 18 decimals, not 24, so the smallest amount it can represent is a million times larger than a yoctoNEAR — irrelevant at any amount worth swapping, visible only if you compare raw integers on the two explorers.

**Why the site uses the peg.** The route data this site is built from carries NEAR on BNB Smart Chain, with a 0x address and 15 confirmations, and the form follows that data. It is the same reason the site's USDT on BNB Smart Chain is Binance-Peg USDT: one network, one address format, one fee token for everything on that chain. [USDT TRC-20 to BEP-20, three ways](https://sablebolt.io/blog/usdt-trc20-to-bep20-three-ways) shows the same chain from the USDT side.

**When native is what you want.** The form cannot pay to a NEAR account. If the NEAR has to end up in a .near wallet, receive the token on BNB Smart Chain at an exchange that lists NEAR on both networks, then withdraw on the NEAR network. That second step is the exchange's, with its own fee and confirmation count, and it is the only way from this site to a native balance.

**When native is what you have.** The mirror image: deposit the native coin at such an exchange, withdraw on BNB Smart Chain to your own 0x wallet, then send the token to the deposit address here. [BNB](https://sablebolt.io/coin/bnb) is the coin to keep a little of in that wallet, because every transfer of the token costs BNB.

## About NEAR — only what a swapper needs

NEAR Protocol is a proof-of-stake network with its own account model. Instead of only key-derived addresses, NEAR has named accounts — bob.near, for example — that anyone can register under a top-level account, and implicit accounts denoted by a 64-character address that corresponds to a key pair. Account names are 2 to 64 characters of lower-case letters, digits and the separators . - _, per the NEAR documentation (checked on 12 October 2026). NEAR also supports Ethereum-like accounts identified by a hexadecimal address, created when someone signs in with an Ethereum wallet.

None of that is what the form uses. On this site NEAR is the BEP-20 token on BNB Smart Chain: the contract 0x1Fa4a73a3F0133f0025378af00236f3aBDEE5D63, which reports the name NEAR Protocol and the symbol NEAR when read from the chain, and which CoinGecko lists as Binance-Peg NEAR Protocol. Binance issues it against NEAR it holds, one to one, the same way its pegged USDT on BNB Smart Chain is issued. It carries the NEAR name and price, but it lives on BNB Smart Chain, moves with BNB Smart Chain fees, and is sent to a 0x address.

That difference is the one thing to get right. A 0x address on BNB Smart Chain looks exactly like an Ethereum address, because it is the same format on a different network; the form cannot tell from the address alone whether your wallet is set to BNB Smart Chain, so check that yourself. And a NEAR-network address — a name or 64 hexadecimal characters — is rejected by the form, which is a protection, not a bug: the token cannot be delivered there.

The deposit side works the same way. If the NEAR you hold is native, in a NEAR-network wallet, it must first become the BEP-20 token before it can be sent to the deposit address — typically by depositing it to an exchange that supports both networks and withdrawing on BNB Smart Chain. If it already sits in a BNB Smart Chain wallet as the token above, send it from there and keep a little BNB in the wallet for the fee.

Our route data counts a NEAR deposit as confirmed after 15 confirmations on BNB Smart Chain, about 2–6 minutes — the estimate still allows three seconds per block, although BNB Smart Chain has produced a block about every 0.45 seconds since the Fermi hard fork of 14 January 2026, so the wait is mostly processing. A swap into NEAR depends on the network you send from. BscScan shows both legs on the BNB Smart Chain side.

## FAQ

Can I receive the payout at my alice.near account?

No. The payout is the BEP-20 token on BNB Smart Chain and goes to a 0x address. The form rejects a NEAR account name for that reason.

Is BEP-20 NEAR the same as NEAR?

Same name and price, different thing. It is a token issued by Binance on BNB Smart Chain against native NEAR it holds. It is not on the NEAR network and cannot be sent to a NEAR account directly.

I sent native NEAR from the NEAR network to the deposit address. What now?

The deposit address is on BNB Smart Chain, and a NEAR-network transfer cannot reach it — a NEAR wallet will refuse a 0x destination. If something was sent across networks by an exchange, contact that exchange; the swap here only sees deposits on BNB Smart Chain.

Which network do I pick on the exchange?

BNB Smart Chain (BEP-20) — both for withdrawing NEAR to the deposit address and for receiving a NEAR payout. Make sure the deposit page shows a 0x address.

How long does it take?

A swap from NEAR takes about 2–6 minutes: 15 confirmations on BNB Smart Chain. A swap into NEAR depends on the network you send from — 2–5 minutes from TRON, 4–10 from Ethereum, 21–44 from Bitcoin.

What is the minimum?

It is shown under the amount field for the pair you selected and moves with network fees.

Why does the form reject my 64-character NEAR address?

Because it is an implicit account on the NEAR network, and the token here lives on BNB Smart Chain. The form takes a 42-character 0x address only.

I gave a 0x address from my NEAR wallet. Where is the payout?

On BNB Smart Chain, at that address — bscscan.com shows it. A NEAR-network wallet cannot display it. If you hold the private key of that 0x account, import it into an Ethereum-style wallet set to BNB Smart Chain.

Do I need BNB to receive NEAR?

Not to receive it. To send the token on again you need a little BNB in the same wallet, because every BEP-20 transfer is paid in BNB.

How do I turn the payout into native NEAR?

Through an exchange that lists NEAR on both BNB Smart Chain and the NEAR network: deposit the token on BNB Smart Chain, withdraw on the NEAR network to your .near account. The form cannot do that step.

Which explorer shows my NEAR swap?

bscscan.com, for both legs — the token is on BNB Smart Chain. A NEAR-network explorer such as nearblocks.io will not find these transfers.

How do I know the token in my wallet is the right NEAR?

Compare its contract with 0x1Fa4a73a3F0133f0025378af00236f3aBDEE5D63 in the wallet's token details or on bscscan.com. BNB Smart Chain has other tokens named NEAR; only this contract is what the form pays and accepts.

## Related

### Coins

- [BNB](https://sablebolt.io/coin/bnb)
- [Tether](https://sablebolt.io/coin/tether)
- [Ethereum](https://sablebolt.io/coin/ethereum)
- [Solana](https://sablebolt.io/coin/solana)
- [Bitcoin](https://sablebolt.io/coin/bitcoin)
- [Polygon](https://sablebolt.io/coin/polygon)

### Posts

- [Sent USDT to the wrong network: what can and can't be recovered](https://sablebolt.io/blog/sent-usdt-to-the-wrong-network)
- [Reading a swap status page: every state from waiting to finished](https://sablebolt.io/blog/reading-a-swap-status-page)

## External resources

- [NEAR docs — account IDs](https://docs.near.org/protocol/accounts-contracts/account-id)
- [CoinGecko — Binance-Peg NEAR Protocol](https://www.coingecko.com/en/coins/binance-peg-near-protocol)
- [CoinGecko — NEAR Protocol](https://www.coingecko.com/en/coins/near)
- [BscScan](https://bscscan.com/)