Skip to content

Failure to deploy a contract with forge #6214

@LesnyRumcajs

Description

@LesnyRumcajs

Describe the bug

There is an issue deploying a contract with Forest - it's fine with a public glif node.

To reproduce

Use https://github.com/filecoin-project/fevm-foundry-kit (commit d28951515ee2dbeff4a42474a0c00d0b5dc7fe94)

❯ forge create --rpc-url http://localhost:2345/rpc/v1 --private-key $PRIVATE_KEY --broadcast src/basic-deal-client/DealClient.sol:DealClient

Log output

[⠊] Compiling...
No files changed, compilation skipped
Error: server returned an error response: error code 11: message execution failed (exit=[ErrIllegalArgument(16)], revert reason=[message failed with backtrace:
00: f010 (method 4) -- method expects arguments (16)
 (RetCode=16)], vm error=[ERROR: revert reason is not cbor encoded bytes])

Forest daemon also reports: WARN forest::rpc::methods::eth::utils: failed to unmarshal cbor bytes from message receipt return error: failed to decode params byte array

Expected behaviour

[⠊] Compiling...
No files changed, compilation skipped
Deployer: 0x901306B1FaCebD88A595Deccae07203d2B271D52
Deployed to: 0x4cda99D1c5b701F154c31eCC50367cE7e3746261
Transaction hash: 0x68a3abb1af89894bae5b2989ef33fad614778501af332151fb1b6abcff4d67c5

(this is the output using --rpc-url https://api.calibration.node.glif.io/rpc/v1

Screenshots

Environment (please complete the following information):

  • OS: Fedora 42
  • Branch/commit fe2c00d

Other information and links

It's probably worth checking out if lotus evm deploy works fine with the same contract (with Forest).

Metadata

Metadata

Assignees

Labels

Type: BugSomething isn't working

Type

No type

Projects

Status

In progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions