Create and Post Transaction with Othent
Post a transaction on Arweave with Othent
Othent is library facilitating the onboarding of users from web2 to web3 through account abstraction. The authentication protocol offers a number of "wallet-less" functions for the same. Users can connect and interact with applications using web2 technologies like email accounts with the help of Othent.
The createAndPostTransactionWOthent
function enables interacting with a deployed contract based on the input parameters.
Basic Syntax
Ensure you have pop-ups enabled in your browser for the URL you'll be using this function in.
The function is called as follows:
Input Parameters
The following params are available for this function and they must be passed in as an object:
apiId: string
: Use of any Othent function requires anapiId
which can be fetched from othent.io. Towards the bottom of the linked page, theGet your API ID
button provides the same.othentFunction: string
: TheothentFunction
param informs the protocol's backend on the type of interaction to network. For thecreateAndPostTransactionWOthent
function, the required input is'uploadData'
.data: object
: Thedata
field is the data to be uploaded on the network. Currently, the function supports data uploads of typeFile
. This can be a file of any format.tags : array
(optional) : Tags can be added to any data for ease of indexing and querying. Every tag must be passed in as an object in the tags array. The syntax for adding tags is as follows:useBundlr: boolean
(optional) : Creates and posts the transaction using bundlr network. Only data type transactions can use this option. If the data size is under 100kB the transaction does not require any fees for processing through Bundlr.
The environment
does not need to be specified for createAndPostTransactionWOthent
as it only supports mainnet
interactions, currently.
Returned Data
The function call returns the following data:
success: boolean
: Thesuccess
status of the data upload request.transactionId: string
: The unique identifier for the upload request. As every upload request is a transaction, it has a correspondingtransactionId
associated with it for future reference.
Last updated