What is a token contract (NEP-141)?
Last updated: 27 October 2026
In short: a token on NEAR is a small program, called a contract, that lives at one account address and keeps a list of who holds how much. Most NEAR tokens follow a shared rulebook called NEP-141. The address is the token's real identity. Anyone can copy a name or a logo, but nobody can copy the address.
What is a token contract?
On NEAR, every account can hold a contract: code that runs when someone calls it. A token contract is one whose job is to track balances. When you "hold" a token, your wallet isn't storing coins. The token contract has a line that says your account holds this many units. Sending a token asks the contract to change two lines: yours goes down, the other person's goes up.
FLTC, for example, is the contract at fltc-af549c.launchpad.justhoot.near. Your FLTC balance is a number stored inside that contract.
Why the address matters more than the name
The name, symbol and logo a wallet shows come from the contract's own metadata, and whoever creates a token chooses them. A copy can say "Fletcher" and use the same picture. The account address can't be copied, because each NEAR account name exists only once.
So the one check that matters is the full address, character by character. The contract check does this for FLTC, and the safety page explains the habit.
What can a token contract do?
NEP-141 lists the calls every standard token should have. The three you will see most on an explorer are:
ft_transfer: send tokens from your account to another account. It needs exactly 1 yoctoNEAR attached, the smallest unit of NEAR, as proof that a real wallet approved it.ft_transfer_call: send tokens to a contract and tell that contract to do something with them, all in one go. This is how a swap starts: the token is sent to a pool, and the pool is told to trade it. If the receiving contract doesn't use all of the tokens, it can return some.ft_balance_of: read how many tokens an account holds. This only reads, so it costs nothing and needs no wallet.
The standard sets the minimum. A contract can also have extra calls of its own, such as a fee on transfers. That is why the code itself, not just the standard, decides how a token behaves. You can see a real ft_transfer_call on the gas fees page.
Who can change a contract?
A contract's code can be replaced by whoever controls its account. On NEAR, that means:
- Anyone holding a full-access key on that account. They can deploy new code at any time.
- Or, if the account has no keys, only what the contract itself allows, for example an upgrade method that a named owner or a DAO (a shared account run by votes) can call.
For FLTC: the contract account has no access keys, which I read from the chain on 27 October 2026. Upgrades can only happen through an on-chain proposal approved by the JustHoot DAO (see How FLTC works).
How do I check one?
- Get the full contract address from the project's own site, not from a message or an ad.
- Paste it into the token checker. It reads the metadata, supply, code fingerprint and access keys live from the chain.
- Look at the access keys. Full-access keys mean a person can change the code. No keys mean only the contract's own rules can.
- Open the address on NearBlocks to see its transactions and holders.
None of this tells you whether a token is a good buy. It tells you what the token is and who can change it. Words you don't know are in the glossary.
Sources
- NEP-141 Fungible Token standard: nomicon.io/Standards/Tokens/FungibleToken/Core
- NEAR Docs, "Access Keys": docs.near.org/protocol/access-keys
- FLTC contract access keys, read from NEAR (
view_access_key_list) on 27 October 2026