Solidity API

_{SpanningERC20} token, including:

• ability for holders to burn (destroy) their tokens
• a minter role that allows for token minting (creation)
• a pauser role that allows to stop all token transfers

This contract uses {SpanningAccessControl} to lock permissioned functions using the different roles - head to its documentation for details.

The account that deploys the contract will be granted the minter and pauser roles, as well as the default admin role, which will let it grant both minter and pauser roles to other accounts.

Deprecated in favor of https://wizard.openzeppelin.com/[Contracts Wizard]._

bytes32 MINTER_ROLE

bytes32 PAUSER_ROLE

function __SpanningERC20PresetMinterPauser_init(string name, string symbol, address delegate) internal

Creates the instance and assigns required values.

function __SpanningERC20PresetMinterPauser_init_unchained(string name, string symbol, address delegate) internal

function mint(address receiverAddress, uint256 amount) public virtual

_Creates amount new tokens for to.

See {ERC20-_mint}.

Requirements:

• the caller must have the MINTER_ROLE._

function mint(bytes32 receiverAddress, uint256 amount) public virtual

function pause() public virtual

_Pauses all token transfers.

See {ERC20Pausable} and {Pausable-_pause}.

Requirements:

• the caller must have the PAUSER_ROLE._

function unpause() public virtual

_Unpauses all token transfers.

See {ERC20Pausable} and {Pausable-_unpause}.

Requirements:

• the caller must have the PAUSER_ROLE._

function _beforeTokenTransfer(bytes32 senderAddress, bytes32 receiverAddress, uint256 amount) internal virtual

uint256[50] __gap

This empty reserved space is put in place to allow future versions to add new variables without shifting down storage in the inheritance chain. See https://docs.openzeppelin.com/contracts/4.x/upgradeable#storage_gaps We use a standard of 50 storage slots. The amount referenced below is based on: 50 - numberOfClassMemberVariables.