Ganache与Sepolia中abi.encode()结果不符且不符合预期的问题

问题复现步骤 #

• 在Ganache和Sepolia网络部署以下合约：

contract ABIExample {
    
    event EncodedData(bytes encodedData);

    function encodeAndDecode(uint a, uint[] memory b, bytes memory c) public  returns (uint, uint[] memory, bytes memory) {
        // abi.encode example
        bytes memory encodedData = abi.encode(a, b, c);
        emit EncodedData(encodedData);
        
        // abi.decode example
        (uint decodedA, uint[] memory decodedB, bytes memory decodedC) = abi.decode(encodedData, (uint, uint[], bytes));
        
        return (decodedA, decodedB, decodedC);
    }

    function encodePackedExample(uint a, uint b) public  returns (bytes memory) {
        // abi.encodePacked example types shorter than 32 bytes are concatenated directly, without padding or sign extension
        bytes memory packedData = abi.encodePacked(a, b);
        emit EncodedData(packedData);
        
        return packedData;
    }

    function encodeWithSelectorExample(uint a, uint b) public  returns (bytes memory) {
        // abi.encodeWithSelector example
        bytes4 selector = bytes4(keccak256("exampleFunction(uint256,uint256)"));
        bytes memory withSelectorData = abi.encodeWithSelector(selector, a, b);
        emit EncodedData(withSelectorData);
        
        return withSelectorData;
    }

    function encodeCallExample() public  returns (bytes memory) {
        // abi.encodeCall example
        bytes memory callData = abi.encodeCall(this.exampleFunction, (42, 123));
        emit EncodedData(callData);
        
        return callData;
    }

    function exampleFunction(uint a, uint b) public pure returns (uint) {
        // Example function for abi.encodeCall
        return a + b;
    }
}

• 调用encodeAndDecode(uint a, uint[] memory b, bytes memory c)方法，传入参数1, [6,8,1,3,5],0xff
• 观察EncodedData事件输出

实际输出 #

Sepolia网络事件数据 #

000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000001600000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000001200000000000000000000000000000000000000000000000000000000000000005000000000000000000000000000000000000000000000000000000000000000600000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000300000000000000000000000000000000000000000000000000000000000000050000000000000000000000000000000000000000000000000000000000000001ff00000000000000000000000000000000000000000000000000000000000000

Ganache网络事件数据 #

0000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000001200000000000000000000000000000000000000000000000000000000000000005000000000000000000000000000000000000000000000000000000000000000600000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000300000000000000000000000000000000000000000000000000000000000000050000000000000000000000000000000000000000000000000000000000000001ff00000000000000000000000000000000000000000000000000000000000000

预期结果（用户预期） #

00000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000030000000000000000000000000000000000000000000000000000000000000005ff00000000000000000000000000000000000000000000000000000000000000

问题解析 #

1. Ganache与Sepolia输出差异的原因 #

两者的差异并非abi.encode()的结果不同，而是日志的显示方式不同：

• Ganache直接输出了encodedData变量的原始内容，也就是abi.encode(a,b,c)的真实编码结果。
• Sepolia输出的是事件参数的完整ABI编码：由于事件参数encodedData是bytes类型（动态类型），按照ABI编码规则，需要先存储该bytes的偏移量（开头的0x20）、长度（0x160），之后才是abi.encode(a,b,c)的内容。

2. 用户预期结果错误的原因 #

用户的预期结果不符合ABI编码规则：
对于包含动态类型（uint[]、bytes）的参数，abi.encode()不会直接将动态类型的内容紧跟在静态参数后，而是遵循以下规则：

• 静态类型参数（如uint a）直接存储值。
• 动态类型参数（如数组、bytes）先存储偏移量（指向实际数据在编码结果中的起始位置）。
• 所有动态类型的实际数据统一放在编码结果的后半部分，依次存储长度和内容。

Ganache的输出才是abi.encode(a,b,c)的正确结果，Sepolia的输出是对事件参数的完整ABI编码，两者本质上是同一数据的不同展示形式。

内容的提问来源于stack exchange，提问作者shadow