The EVM instruction addresses memory-copying overhead. It is not a way to duplicate persistent storage or transfer token balances.

What the primary record establishes

EIP-5656, created on 1 February 2021 and marked Final, introduces MCOPY for copying EVM memory areas. Its arguments identify destination, source and length. Ethereum — EIP-5656, Final ↗

The specified semantics allow source and destination to overlap, with the effect of copying through an intermediate buffer. The gas calculation accounts for length and any necessary memory expansion. Ethereum — EIP-5656, Final ↗

What the distinction changes

That overlap rule matters when reviewing low-level implementations. A manually written copy loop can have different behavior if it overwrites unread source bytes.

The instruction concerns execution memory, not the persistent storage slots of an account. Copying bytes also does not transfer ownership of assets represented by those bytes.

What to check before drawing a conclusion

Compare like-for-like implementations and input sizes before claiming savings. Memory expansion and surrounding operations remain part of the total transaction cost.

The historical specification establishes an operation’s behavior, not a universal fee discount for an application. Review offsets, length and the data’s meaning alongside the opcode rather than treating a faster copy as proof of overall correctness.