Sending Transactions

Learn how to interact with the CLoud send transactions onchain.

note

To use embedded signers, first you need to authenticate your users. Follow the steps to set up embedded signers for your users with the embedded signer overview.

Quickstart#

1. Create a transactionIntent - Server side#

Create a request to your backend to create a transactionIntent. In the body of the request:

Include the player that signs the transaction.
Include the policy that interacts with the contract for gas. If non-existen the user will need to have gas tokens.
Include optimistic if you want the transactions to be confirmed faster.

Depending on the type of transaction you're creating you'll define interactions. The interactions field is an array of objects that contain the information of the contract to interact with, the function to call, and the arguments to pass to the function.

the interactions field contains the contract that has previously been added to Openfort.
the functionName defines the function to call from within the contract.
If there exist more than one function with the same name, the functionArgs will be used to determine which function to call.

command-line

curl https://api.openfort.xyz/v1/transaction_intents \
  -H "Authorization: Bearer $YOUR_SECRET_KEY" \
  -d player="pla_..." \
  -d policy="pol_..." \
  -d chainId=80002 \
  -d optimistic=true \
  -d "interactions[0][contract]"="con_..." \
  -d "interactions[0][functionName]"="mint" \
  -d "interactions[0][functionArgs][0]"="0x63B7...484f"

2. Sign the transactionIntent with the signer. - Client side#

Use the nextAction returned by the backend to sign the transaction with the embedded signer.

The transaction will be automatically signed and broadcasted by using the sendSignatureTransactionIntentRequest method.

const handleCollectButtonClick = async () => {
  try {
    setCollectLoading(true);
    const collectResponse = await fetch(`/api/examples/protected-collect`, {
      method: "POST",
      headers: {
        "Content-Type": "application/json",
      },
    });
    const collectResponseJSON = await collectResponse.json();
    if (collectResponseJSON.data?.nextAction) {
      console.log("config", config);
      const response = await openfort.sendSignatureTransactionIntentRequest(
        collectResponseJSON.data.id,
        collectResponseJSON.data.nextAction.payload.userOperationHash
      );
      console.log("response", response);
    }
    console.log("success:", collectResponseJSON.data);
    alert("Action performed successfully");
  } catch (error) {
    console.error("Error:", error);
  } finally {
    setCollectLoading(false);
  }
};

If you've integrated Openfort with another web3 library, you can also use that library's syntax for requesting a transaction from the client-side:

Library	Method
Ethers	Use the signer's `sendTransaction` method.
Wagmi	Use the `useSendTransaction` hook.

Examples#

NextJS Sample Embedded Signer

An integration with Google OAuth using Firebase Auth as a third party auth provider to create a non-custodial embedded signer.

Unity Sample Android Embedded Signer

An integration with Google Play Games using Firebase Auth as a third party auth provider to create a non-custodial embedded signer.

Unity Sample WebGL Embedded Signer

An integration with Openfort Auth with non-custodial embedded signer.