For EVM developers

NEAR by Example

Learn NEAR smart contracts the way you already think — in Solidity. Every concept is shown side by side: the Solidity you know on the left, the NEAR equivalent (Rust) on the right. Compact, complete, and (soon) compile-verified.

The Rosetta table

The quick EVM → NEAR lookup. A blank cell means there’s no direct analog on that side.

Solidity / EVM	NEAR
`ERC-20`	`NEP-141`Fungible token
`ERC-721`	`NEP-171`NFT
`ERC-1155`	`NEP-245`Multi-token
`address`	`AccountId`Named accounts (alice.near), not 20-byte hashes
`msg.sender`	`env::predecessor_account_id()`
`tx.origin`	`env::signer_account_id()`
`msg.value`	`env::attached_deposit()`NearToken (yocto-NEAR)
`wei (10^18)`	`yocto-NEAR (10^24)`
`mapping(k => v)`	`LookupMap / UnorderedMap`Explicit, from near_sdk::store
`require / revert`	`assert! / env::panic_str`Rolls back, refunds unused gas
`constant`	`const (module level)`
`view / pure`	`&self method`A receiver, not a keyword
`payable`	`#[payable]`
`emit Event(...)`	`env::log_str (NEP-297 JSON)`
`approve + transferFrom`	`ft_transfer_call`Transfer-and-call; no allowance
`proxy upgrade pattern`	`DeployContract action`Native self-upgrade
`EIP-712 / meta-tx`	`NEP-366 + access keys`Native account abstraction
`selfdestruct`	—No equivalent (accounts deleted explicitly)

Chapters

Getting started

Your first contract

State & storage

State, constants & locals

Functions & calls

Functions: view, mutating & payable