Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: just devnet-fault error #3

Open
samlaf opened this issue Dec 17, 2024 · 3 comments
Open

bug: just devnet-fault error #3

samlaf opened this issue Dec 17, 2024 · 3 comments

Comments

@samlaf
Copy link

samlaf commented Dec 17, 2024

Running through README devnet steps on master branch.

$ just devnet-fault
./target/release/kailua-cli test-fault --registry-contract 0xd801426328C609fCDe6E3B7a5623C27e8F607832 --l1-node-address http://127.0.0.1:8545 --l1-beacon-address http://127.0.0.1:5052 --op-node-address http://127.0.0.1:7545 --proposer-key 0x47e179ec197488593b187f80a00eb0da91f1b9d0b13f8733639f19c30a34926a --fault-offset 1 --fault-parent 1 
2024-12-17T22:05:18.299097Z ERROR kailua_cli::fault: Failed to send faulty proposal txn: propose (send)

Caused by:
    server returned an error response: error code 3: execution reverted, data: "0x1ebb374b00000000000000000000000000000000000000000000000000000000000000fe0000000000000000000000000000000000000000000000000000000000000539"
@hashcashier
Copy link
Collaborator

Thanks for pointing this out.

This command seems to have two bad default values set in the justfile:

devnet-fault offset="1" parent="1" 

It should work if you call it without these defaults and use your own values as follows:

just devnet-fault BAD_PROPOSAL_OFFSET PARENT_PROPOSAL_INDEX

BAD_PROPOSAL_OFFSET is the 1-indexed position of the bad output in the proposal. It can be any value between 1 and your number of blocks per proposal.

PARENT_PROPOSAL_INDEX is the DisputeGameFactory game index of the parent proposal to extend.

@samlaf
Copy link
Author

samlaf commented Dec 19, 2024

@hashcashier thanks! Why was it working before and not anymore? Did something change in the contracts themselves, or just the CLI code?

@hashcashier
Copy link
Collaborator

Its code changed a lot for V2, and the fault inducer's logic was changed. Previously it just extended the latest proposal, but now you have to point it at a specific parent to extend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants