Skip to content

Side Effects #4

@boid-com

Description

@boid-com

The firewall should be able to trigger external sync/async events in response to specific requests.

Example: Users could deposit some "Gas Fees" into an account controlled by the node operator, when a transaction is pushed to the node operator node by an account with a balance, if needed, funds are pulled from their deposit to trigger a PowerUp for their account. This would simplify the user experience and remove the need for end users to worry about resource management on a per transaction basis. Just deposit some gas fees occasionally. There is some trust required on behalf of the node operator to only trigger PowerUps when necessary and also to use the funds to PowerUp the target account.

In the above example, The node operator needs to trigger a PowerUp and ensure the transaction is on-chain before triggering the action signed by the requestor, so it should be synchronous.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions