We're maintaining an app registry to hold all the contracts deployed by a specific user.

Our workflow looks like:

• Deploy the contract
• Update the state with the deployed contract address
• Add the contract to the registry for the specific user.

We have our own deploy contract hook (useDeployContract), that deploys the contract (using async) and returns the address,

The implementation is as so:

import { ContractFactory } from 'ethers';
import { useSigner } from 'wagmi';

import type { Signer } from 'ethers';

export const useDeployContract = () => {
  const { data: signer } = useSigner();

  const factory = new ContractFactory(...).connect(signer as Signer);

  const deploy = async (args: any[]) => {
    const tx = await factory.deploy(...args);

    await tx.deployed();

    return tx.address;
  };

  return deploy;
};

Then, we have a state to hold the deployed contract address, and it's updated after calling the useDeployContract, but the default value is undefined and the prepareContractWrite holds the value.

const { config: contractConfig } = usePrepareContractWrite({
  addressOrName: REGISTRY_URL,
  contractInterface: REGISTRY_ABI,
  functionName: 'addDeployment',
  args: [address, deployedContractAddress],
  enabled: deployedContractAddress !== null
});

const { write: contractWrite} = useContractWrite(contractConfig);

Here, the config is never created, and isn't actually run by the useContractWrite. This dependency doesn't let executing the transaction to add to registry just after deployment by taking the user transaction approval.

Any idea on how I can achieve this and perform multiple transactions/reads at a time one by one, in a specific sequence.

(CC: @jxom @janaSunrise)