In NEAR, users can register named accounts (e.g. bob.near) which are simpler to use and remember.
Named accounts can create sub-accounts of themselves, helping to better organize related-accounts. In this way, named accounts work as domains, particularly:
Only registrar can create short top-level accounts (e.g. near, aurora).
Anyone can create long top-level accounts, e.g. verylongaccountnamethatis32chars.
near can create bob.near, and bob.near can create app.bob.near.
near cannot create app.bob.near, and test.near cannot create sub.example.near.
Minting an NFT on a blockchain allows the creator to prove ownership and authenticity of the digital asset
Swagger Doc | ReDoc
Path parameters:
chain:[string] chain to work with. Either testnet or mainnet .
contract_id:[string] smart contract account .
Body parameters:
account_id: Your account id.
token_id: The token ID , must be unique.
title: The name of this specific token.
description: A longer description of the token.
media: URL to associated media. Preferably to decentralized, content-addressed storage.
media_hash : The base64-encoded sha256 hash of content referenced by the media field. This is to guard against off-chain tampering.
reference : URL to an off-chain JSON file with more info.
reference_hash : Base64-encoded sha256 hash of JSON from reference field. Required if reference is included.
receiver_id: The account that's receiving the token.
Example:
On Near Protocol , NFTs are not stored in the user's wallet, instead, each NFT lives in a NFT contract. The NFT contract works as a bookkeeper, this is: it is in charge of handling the creation, storage and transfers of NFTs.
In order for a contract to be considered a NFT-contract it has to follow the NEP-171 and NEP-177 standards. The NEP-171 & NEP-177 standards explain the minimum interface required to be implemented, as well as the expected functionality.
Swagger Doc | ReDoc
Path parameters:
chain : [string] chain to work with. Either testnet or mainnet .
account_id :[string] your account.
Body Details:
Body parameters:
spec : a string that MUST be formatted nft-n.n.n where "n.n.n" is replaced with the implemented version of this Metadata spec.
name : the human-readable name of the contract.
symbol : the abbreviated symbol of the contract.
icon : a small image associated with this contract. Encouraged to be a data URL.
base_uri : Centralized gateway known to have reliable access to decentralized storage assets referenced by reference or media URLs. Can be used by other frontends for initial retrieval of assets, even if these frontends then replicate the data to their own decentralized nodes, which they are encouraged to do.
📎 Create a Sub-account
📎 Deploy NFT Contract
🖼️ NFT | Minting