Overview

Currently, there are two methods available for creating a Gibwork task. The first method requires obtaining an API key, enabling you to deposit funds into a token account; however, this approach is limited to the SOL token. The second method generates a serialized transaction that must be signed and executed to create the task. This option is more versatile, as it supports not only SOL but also all other SPL tokens.

📘
Gibwork recommends using the serialized transaction method over the API Key method.

Create Task via Serialized Transaction

The preferred method for creating a task requires no authentication, ensuring a straightforward and user-friendly process. By utilizing the endpoint /tasks/public/transaction, you can specify essential task details, such as the task amount and the token to be used. Once the details are submitted, a serialized transaction is generated and returned. This transaction must then be signed by the designated payer and executed to complete the task creation seamlessly.

What's a Serialized Transaction ?

A transaction that has been constructed and encoded into a standardized binary format (Base64 in our case). This format contains all the necessary data to execute the transaction on the blockchain.

Gibwork uses serialized transactions to store the required instructions, accounts, signatures, and metadata necessary to fund and create a Task.

Create Task via Token Account

The alternative method to creating a task on Gibwork is via the usage of an API Key. The API Key can be generated following the instructions here: https://gibwork.readme.io/reference/authentication-1.

By utilizing the endpoint /tasks/public, you can specify essential task details. In response, you will receive a Token account. The funds (SOL) sent to this Token account will determine the amount displayed on the task. Failure to send funds to the Token account within the 10-minute window will result in the task being deleted.