Skip to main content

FIPs

See FIP1 for more information: https://github.com/fuseio/FIPs/blob/master/FIPS/fip-1.md

What is a FIP?​

FIP stands for Fuse Improvement Proposal. A FIP is a design document providing information to the Fuse community or describing a new feature for Fuse Network. The FIP should provide motivation and technical specifications for the feature.

FIPDescriptionStatus
FIP-1Introduction and explanation about FIP'sDone
FIP-2Enabling delegation of fuse tokens to validatorsDone
FIP-3Lowering the stake to run a validator node to 100K FuseDone
FIP-4Multi validators, validators can run multiple nodesUndone
FIP-5Validators key splitting, validator will have separated keysUndone
FIP-6Bridge implementation should be changeable by votingUndone
FIP-7Tiny Ethereum Network transactions on end of cycleUndone
FIP-8Adjusting Block Rewards by the Validator's StakeDone

Supported EIPs

Ethereum Improvement Proposals (EIPs) supported by FUSE:

EIPDescription
EIP-150Gas cost changes for IO-heavy Operations
EIP-155Simple replay attack protection
EIP-160EXP cost increase
EIP-161State trie clearing
EIP-140REVERT instruction
EIP-211New opcodes: RETURNDATASIZE and RETURNDATACOPY
EIP-214New opcode STATICCALL
EIP-658Embedding transaction status code in receipts
EIP-145Bitwise shifting instructions in EVM
EIP-1014Skinny CREATE2
EIP-1052EXTCODEHASH opcode
EIP-1283Net gas metering for SSTORE without dirty maps
EIP-1344ChainID opcode
EIP-1706Disable SSTORE with gasleft lower than call stipend
EIP-1884Repricing for trie-size-dependent opcodes
EIP-2028Transaction data gas cost reduction
EIP-2929Gas cost increases for state access opcodes
EIP-2930Optional access lists

EVM Version​

Based on the implemented Ethereum Improvement Proposals (EIPs), Fuse chain is compatible with the EVM version up to and including the Berlin network upgrade. In addition, EIP-1559 is part of London network upgrade.

Ref: https://github.com/ethereum/execution-specs/tree/master/network-upgrades/mainnet-upgrades