Challenge Submission Fails Despite Correct Treasury and Commander Updates in HigherOrder Level

[shubham562]

Description:

I have successfully interacted with the HigherOrder contract by deploying a hack contract. My hack contract performs the following steps:

1. Calls the registerTreasury(uint8) function with a value that triggers an underflow, effectively setting the treasury to a large number.
2. Subsequently, it calls the claimLeadership() function to update the commander to the address of my hack contract.

Both operations appear to work correctly, as the treasury value is updated as expected, and the commander is set to my hack contract's address. However, despite these changes, the challenge validation process indicates that the level has not been completed.

Steps Taken:

1. Deployed the Hack contract.
2. Invoked registerTreasury(uint8) with -1 to cause an underflow and update treasury.
3. Called claimLeadership() to set commander.

Issue:

The challenge submission process still reports that the level has not been cracked. I’ve double-checked my contract and the challenge requirements, and everything seems to be in order. Could you please assist in identifying why the challenge is not completing despite the expected changes?