Fractal Plugins Workflow

[tbwebb22]

Fractal plugins are react code which initially will live on the fractal-interface repo. They serve the purpose of making it easier for users to craft transactions that will be executed by the DAO contract. These plugins may interact with multiple Fractal modules or other contracts on chain.

The workflow below documents the steps users will go through, and logic happening behind the scenes.

User actions are in italics.

1. User navigates to the transaction creation screen
2. User is presented a selection of available plugins and chooses one
3. User is presented a selection of actions that the plugin supports and chooses one
4. The plugin knows interface IDs of the Fractal modules that are needed for the selected action. It will then loop through all modules installed on the DAO, and create a list of modules that match this expected interface.
5. If there is one module that matches this interface, the plugin selects this module to interact with automatically. If there are multiple modules that match this interface, the user is presented with a list of these modules, and the user selects one.
6. The user is presented with any parameter options necessary for the action, and the user inputs the values.
7. The plugin crafts the entire transaction to be executed by the DAO.
8. The app checks if the user has the execute role on the access control contract.
9. The user is presented with a list of ways to execute the transaction. If the user has the execute role, one of the options will be "self-execute", and the user can execute the transaction immediately. This list will also include modules installed on the DAO that have the execute role. If the user selects one of these modules, this takes the user to the UI associated with the selected module, and the crafted transaction data is sent to this module component. The user may then continue through the module UI (for example creating a proposal on a governor module).

Open Question: A plugin that interacts with other contracts on chain that are not Fractal modules: How is the plugin aware of these? Are these addresses hard-coded into the plugin?

[adamgall]

@tbwebb22 i'm not sure about step 3. in my head, to start, a plugin is just one thing, which results in one (set of) transaction(s). What are you envisioning as the difference between a "plugin" and "actions" on a plugin

[tbwebb22]

An example of how I've been envisioning a plugin:

A plugin exists for interacting with Uniswap. This Uniswap plugin may have different actions on it, like "buy token", "add liquidity", etc.

[adamgall]

oh ok sure that makes sense

[adamgall]

Kinda nitpicky, but maybe step 9 should just be included as one of the options on the list of step 10.

[tbwebb22]

Updated with this change

[adamgall]

i guess what i meant there was

if the end user has EXECUTE_ROLE permission, and there are some modules that have EXECUTE_ROLE permission, the end user should be able to select "self" or "governor", for example.

[adamgall]

like, when "building the list of addresses that this transaction could be passed through", include "self" if "self" has EXECUTE_ROLE permission

[tbwebb22]

Ohh understood, updated

[adamgall]

Open Question: A plugin that interacts with other contracts on chain that are not Fractal modules: How is the plugin aware of these? Are these addresses hard-coded into the plugin?

For sure, I'd think they have to be.

But like, for the Uniswap example, nothing would need to be hardcoded. User input (token addresses, fee rate) can be used to determine the pool address, for example.