@Fangting (@triny0111)

Table of Content

You have decided to write an ERC-6900 plugin that can be used by all ERC-6900 compliant accounts. That’s great!

But, where do you start?

You have come to the right place! In this guide, we will walk through how to write an ERC-6900 plugin by writing a multi-owner plugin together in Solidity.

Terminology

Here is a list of ERC-6900 terminology that we will reference throughout the article:

• MSCA: modular smart contract account that is compliant with ERC-6900.
• User Operation: an ERC-4337 term that is often used to indicate the context for an ERC-4337 transaction format where txs are sent to the EntryPoint contract first, who then calls accounts with user operation(s).
• Runtime: a term used to indicate the traditional transaction context, as opposed to the above ERC-4337 transaction format. Here, txs are sent directly to the smart contract, rather than from the EntryPoint contract via user operations.

Resources

An ERC-6900 plugin needs to implement required interfaces and abide by ERC-6900 rules for plugins. The reference implementation of ERC-6900 provides a nice BasePlugin and IPlugin, as well as plugin examples. Those are all good materials to help you understand how to write a plugin.

We will also release a set of dev tools in the coming weeks to make it extremely easy to write a plugin. Stay tuned!

When you are ready, let’s get started.

1. What is an ERC-6900 plugin?

An ERC-6900 plugin is a smart contract that provides up to three types of functions for an MSCA aside from its own functions.

• Validation functions. Functions that validate authentication and authorization for an MSCA.
• Execution functions. Functions that define the main execution logic of a function of an MSCA.
• Hook functions. Functions can be run before the above Validation functions, or before and after the above Execution functions, for whatever purposes.