Not able to create WIPE and RETIRE contracts on guardian mainnet

[saharshkhicha18]

We are hosting our own instance of guardian service and we have deployed our own retire and wipe contract file ids using the process below

We have successfully deployed the contract files

Retire contract file identifier - 0.0.5539948
Wipe contract file identifier - 0.0.5540084

However when we try to create the Wipe and retire contract under the retirement section, we get the following error:

However on testnet there is no such issue. How can I fix this issue on mainnet?

[anvabr]

@saharshkhicha18 thank you for the detailed issue description, and sorry to hear you are experiencing problems. Could you please advise the version of Guardian that you are running?

[saharshkhicha18]

@anvabr we are using guardian version 2.23.1

[saharshkhicha18]

We have tried to create the contract using hedera SDK (0.0.5780884) and then import in guardian but it gives us a timeout on the import api call.

Further I am able to create a contract from wipe contract file id but when I try to create contract with the retire contract file id, the transaction_revert_executed error shows up.

[anvabr]

@saharshkhicha18 We've been unsuccessfully trying to reproduce this issue, for us everything seems to work if we follow the procedure. Can I check that after you deployed the contracts you have:

1. updated the corresponding settings in your .env.guardian
2. restarted guardian-service after the update of .env.guardian

For you reference, the configuration options in question look like this:

RETIRE_CONTRACT_FILE_ID="..."
WIPE_CONTRACT_FILE_ID="..."

Not performing one of both of these steps have triggered a similar error in our tests:

1715332903.734431241; payer sigs: 1; total sigs: 1; admin keys: 1; submit keys: 0; topic memo size: 14; memo size: 0; ]: TopicCreateTransaction
{
  id: '3bec8b2c-3293-4740-8f53-12d5e2d37c69',
  error: "Cannot read properties of undefined (reading 'clone')"
}

Can you please confirm everything is OK with your Guardian .env file?

[anvabr]

Another theory that we have is that it has something to do with gas limit. We are investigating. Just want to make sure the basics are right with the ^^^.

If the settings are done and correct and the problem occurs could you please increate the gas limit for the tx in the .env (active settings) file to see if this is the issue you are facing? Please add/edit the following settings and numbers:

CREATE_RETIRE_CONTRACT_GAS=6000000
CREATE_WIPE_CONTRACT_GAS=3000000

[saharshkhicha18]

We have tried adding the gas variables and still get the same error

[saharshkhicha18]

Everything in our .env file seems okay. We have set the INITIALIZATION_TOPIC_ID, RETIRE_CONTRACT_ID and WIPE_CONTRACT_ID correctly. Further we deployed our own file ids and tried with that but still end up with the same error

Retire contract file identifier - 0.0.5539948
Wipe contract file identifier - 0.0.5540084

Using the file ids above, we created a Wipe contract 0.0.5780884 and tried to import it but there was an error. Using the retire file id we were not able to create a contract as it responded with a CONTRACT_REVERT_EXECUTED

[anvabr]

@saharshkhicha18 we are looking further into this. Just to check please - did you definitely restart the service (containers etc) after you edited the files increasing the GAS limit? This is critically important, it would not work otherwise.

[anvabr]

Hello @saharshkhicha18, to follow-up on the above I don't believe everything is correct with your .env files. I recommended to set CREATE_RETIRE_CONTRACT_GAS=6000000 but looking at your last attempt - the actual setting was '2000000'.

This really looks like that either you did not set the variables correctly, or put the variables in the wrong file, or potentially confused retire and wipe contracts (they have different requirements for GAS usage), or (most likely) did not restart guardian-service after changing the settings. Please check.

To confirm, we have gone through the entire process step-by-step on the mainnet, here is the detailed breakdown:

1. using default GAS limit setting - got the insufficient gas error
   

2. GAS limit setting increased but it is not sufficiently high - getcontract_revert_executed error, however it is clear in the log that the GAS was not sufficient again
   
   

3. Increased GAS limit - all successfully executed.
   
   

[saharshkhicha18]

I was trying to deploy the contracts outside of the guardian service using hedera SDK where i used gas as 2000000. However on guardian we have set the env variables for gas but still get the same error.