NEAR account names: named, sub-accounts and 64-character accounts
Last updated: 31 October 2026
In short: a NEAR account has a name, and the name comes in two main kinds. A named account looks like alice.near and is easy to read. An implicit account is a 64-character string of digits and letters that is just a public key written in hex. Both work the same way when you send or receive. Read a name from right to left, because the last part tells you which account it belongs to.
The NEAR wallet page covers keys and seed phrases. This page is only about names: what the rules are, how the two kinds differ, how to get each one, and why the details matter when you send money.
What counts as an account name?
NEAR's rules are short. A name must be between 2 and 64 characters long. It can use lowercase letters (a-z), digits (0-9), and the separators ., - and _. No capital letters, no spaces, no @. A dot splits the name into parts, and a - or _ can only sit between letters or digits, never at the start or end of a part and never twice in a row.
So alice.near, max_99.near and app.alice.near are valid. Alice.near, _alice.near and alice..near are not.
The two main kinds
| Named account | Implicit account | |
|---|---|---|
| Looks like | alice.near | 64 digits and letters a to f |
| Made from | A name someone registers | A key pair, with nothing to register |
| Exists when | An existing account creates it | Someone first sends it NEAR, even 0 NEAR |
| Easy to read | Yes | No |
Both kinds can hold NEAR and tokens, and both can have a contract attached. They are separate accounts. A named account and an implicit account made by the same wallet are two different things.
Implicit accounts: a key in disguise
You make a key pair on your own device. The public half of the key is 32 bytes. Written in hex, that is 64 characters, and that string is the account name. Nobody has to approve it, and nothing is recorded on the chain yet. The account only appears when someone sends it NEAR. The NEAR docs say a transfer of 0 NEAR is enough to create it.
Here is a real one. The person who made the FLTC swap in the NearBlocks lesson used the account fb8803d7d93cac1ffc3828845c0e1c9ca194b219118b7ac36d9ffe4fd1d805e2. The key that signed that transaction is ed25519:HvsdDqKe7TA8zbQ7o7nUso2jSeh9NZxMWcn7r2P9jJDw. I decoded that key from base58 into hex on 31 October 2026, and it gives exactly the account name above. That is the whole trick: the name and the key are the same thing in two spellings.
When the account is created, the network gives it one full-access key, the one that matches the name. Whoever holds the matching private key controls the account. The docs also note that deleting the private key of an implicit account locks it for good.
There is one more look-alike. An address that starts with 0x followed by 40 hex characters is an Ethereum-style account, made when someone signs in to a NEAR app with an Ethereum wallet such as MetaMask. NEAR also has two newer kinds that start with 0s and 0u. You are unlikely to meet them as a beginner.
Named accounts and sub-accounts
Named accounts work like website domains. NEAR's own specification puts it this way:
- A special account called
registrarcreates the top-level names, likenear. - Only
nearcan createalice.near. - Only
alice.nearcan createapp.alice.near, which is called a sub-account. nearcan not createapp.alice.neardirectly, andbob.nearcan not createapp.alice.neareither.
A parent has no control over its sub-accounts once they exist. Each one is its own account, with its own keys and its own contract. What controls it is those keys and that contract, not the name.
FLTC's contract is a good example to read. Its account is fltc-af549c.launchpad.justhoot.near. Read it from right to left: near made justhoot.near, then justhoot.near made launchpad.justhoot.near, then launchpad.justhoot.near made fltc-af549c.launchpad.justhoot.near. The name shows which account created it. It does not, on its own, show who runs the code. That is what the token contract page and the token checker are for.
How do I make one?
Implicit: install a wallet and create a new account. Many wallets give you an implicit account by default. It becomes real the first time you receive NEAR.
Named: most wallets let you pick a name like yourname.near while you set up, and then create it for you. If the name is taken, you choose another. Under the hood, the wallet asks the near account to create the new name, or an account you already control creates a sub-account of itself. The docs show how to do this by hand with the NEAR command-line tool, but you do not need that.
Creating any account costs about 0.00707 NEAR in total, almost all of it a fixed 0.007 NEAR charge for the space the account takes up (see gas fees). For a named account the charge is paid when it is created. For an implicit one it is paid when it first receives NEAR. The wallet or the sender usually covers it. Write your seed phrase down on paper first, as the wallet page explains.
Why the details matter
- A typo sends money to the wrong place. A transaction on a blockchain cannot be undone. The NEAR docs have a whole guide on checking the receiving account for this reason. Copy and paste a name instead of typing it, and read it slowly before you approve.
- Look-alike names are cheap to make. Anyone can create a sub-account under an account they control, with any name they like.
fltc.something.nearis not made by FLTC. Only the last parts of the name tell you who made it. The same goes for0versusoand-versus_. See the safety page and seed-phrase scams. - A named account can be read out loud; an implicit one cannot. That is the main reason people pick a name.
- An implicit account has no one to ask. If you lose the key, there is no account owner to call. The same is true of any account whose keys are lost.
Words you don't know are in the glossary.
Sources
- NEAR Docs, "Address (Account ID)": docs.near.org/protocol/accounts-contracts/account-id
- NEAR Protocol Specification, "Accounts": nomicon.io/DataStructures/Account
- NEAR Docs, "Creating Implicit & Named Accounts": docs.near.org/protocol/tutorials/creating-implicit-and-named-accounts
- NEAR Docs, "Gas (Execution Fees)", for the account creation charge: docs.near.org/protocol/transactions/gas
- NEAR Docs, "Validating Recipient Accounts": docs.near.org/web3-apps/tutorials/account-validation
- The example transaction, read from a NEAR archival node on 31 October 2026: HumMzbDtETZWFxv1ofeiVMcx4kb3mDANzZDEYhfeh4zy