📜Scenarios

What are Scenarios?

Ignite Scenarios are a powerful and flexible feature of the Igniter module, designed to provide users with the ability to create customizable, event-driven workflows for managing wallet access.

By utilizing Ignite Scenarios, users can create a wide range of access management scenarios, from simple key generation tasks to complex, multi-step processes involving signature creation, key rotation, and conditional logic. This flexibility allows you to optimize the balance between security and accessibility, tailoring the wallet access management process to your specific needs and requirements.

Scenario Types

Tookey Igniter supports various types of scenarios. Here's an overview of the different types of Ignite Scenarios:

1. Cron: These scenarios are triggered based on a predefined schedule, allowing you to automate repetitive tasks or schedule future events. This is particularly useful for key rotation, regular updates, and other time-sensitive operations.

2. OnchainRequest: OnchainRequest scenarios are initiated by an external request from a user or another system, stored in a supported blockchain. This type of scenario is ideal for on-demand operations such as signing and transactions resulting from blockchain interactions. For example, building cross-chain bridges or transferring DAO voting results from one network to another.

3. Monitor: Monitor scenarios monitor data feeds for changes and trigger tasks based on predefined conditions. This is useful for reacting to events or changes in external data, such as price fluctuations or other market-related events. This is especially useful for oracleizing and/or committing intermediate results to the blockchain (such as the results of GameFi games). Temporary Unavailable

4. Keeper: Keeper scenarios are designed to maintain a specific state or perform ongoing tasks within the system. These scenarios are ideal for ensuring the stability and consistency of the wallet access management process, as well as for monitoring and maintaining other aspects of the infrastructure. Temporary Unavailable

5. Webhook: Webhook scenarios are triggered by events from external systems, allowing you to seamlessly integrate your wallet access management processes with other applications or services. This is particularly useful for automating responses to specific events, such as granting access in response to a user request or generating a signature following a successful transaction.