Skip to main content

11 docs tagged with "smart-contracts"

View all tags

Address Mapping

How Polymesh 32-byte accounts and 20-byte EVM addresses map onto each other, why the mapping is one-way in one direction, and why an account must call map_account before receiving funds at its EVM address.

EVM & Smart Contracts

Polymesh's EVM surface - the pallet-revive dual-VM contract engine, precompiles, EVM address mapping, runtime calls from a wallet, and the Ethereum JSON-RPC proxy

Fungible Asset Precompile (ERC-20)

Use any Polymesh fungible asset as an ERC-20 token from Solidity and Ethereum tooling, with parts of ERC-3643 and ERC-7943 - address derivation, the full method reference, events, revert reasons, and the limits to design around.

Fungible Asset Precompile Changelog - v8.0 to v8.1.2

Polymesh chain v8.1 exposes every native fungible asset as an ERC-20 token through a pallet-revive precompile; v8.1.1 completes the ERC-3643 and ERC-7943 surface with pausing, agent checks, partial freezing and recipient-directed forced transfers.

NFT Precompile Changelog - v8.0 to v8.1.2

Polymesh chain v8.1.1 exposes every NFT collection as an ERC-721 token through a pallet-revive precompile, with ERC-721Metadata token URIs, ERC-165 introspection and ERC-7943 transfer checks.

Non-Fungible Asset Precompile (ERC-721)

Use any Polymesh NFT collection as an ERC-721 token from Solidity and Ethereum tooling - address derivation, the full method reference, token URIs, approvals, events, revert reasons, and the deviations to design around.

Polymesh Runtime Precompile

Call general-purpose Polymesh extrinsics from Solidity - create assets, register tickers, onboard identities and authorize external agents through a single fixed-address precompile.

Precompiles

How Polymesh exposes native chain functionality to smart contracts through pallet-revive precompiles - the address scheme, shared call semantics, and the list of available precompiles.

Runtime Calls from an EVM Wallet

Submit native Polymesh extrinsics from an EVM key such as a MetaMask account, by sending a transaction to the reserved runtime-pallets address - no smart contract and no precompile involved.