FAQ

Frequently Asked Questions (FAQ) About Nexus

General Questions

Where does the name "Nexus" come from?

The name "Nexus" is inspired by the concept of a central connection point or hub. In the context of smart contracts, Nexus acts as a central platform that integrates various functionalities, providing a modular and flexible architecture for building and managing smart accounts.

How is Nexus used in real-world applications?

Nexus is designed to facilitate advanced smart contract interactions by providing a modular framework that supports various use cases. It is used in decentralized finance (DeFi), non-fungible tokens (NFTs), supply chain management, and other blockchain-based applications where secure and efficient smart contract execution is crucial.

Can I migrate my existing smart contract to Nexus?

Yes, you can migrate your existing upgradable smart contract to Nexus. The process involves calling the upgradeToAndCall function with the new Nexus implementation address and any required initialization data. Detailed steps for the migration process can be found in the Nexus Migration Guide.

Important

When upgrading from a non-ERC7579 compatible smart account, you will lose access to the modules already installed. You will need to install them manually or through the migration process when calling the upgradeToAndCall function.

What makes Nexus better than other Smart Accounts?

Nexus offers several advantages over traditional smart accounts:

• Modularity: Easily extendable with different modules to add or modify functionalities.
• Security: Built-in security features and robust validation mechanisms.
• Flexibility: Supports various execution modes, making it adaptable to different use cases.
• Gas Optimization: Designed with gas efficiency in mind, ensuring cost-effective operations.

Why ERC7579?

ERC7579 provides a standardized interface for modular smart accounts, promoting interoperability and flexibility. It enables the creation of smart accounts with interchangeable modules, allowing for easy upgrades and customization without disrupting existing functionalities.

Technical Questions

What are the types of modules?

Nexus supports various types of modules, each serving different purposes:

• Validators: Modules that validate transactions or operations.
• Executors: Modules that execute specific functions or transactions.
• Hooks: Modules that provide additional logic or callbacks during execution.
• Fallback Handlers: Modules that handle fallback scenarios.

Tip

Ensure that at all times, a validation module is present in the Nexus smart account to maintain security and integrity.

What is the difference between the different execution modes?

Nexus supports multiple execution modes to provide flexibility in how transactions are handled:

1. Single Execution:

   • Executes a single transaction.
   • Suitable for straightforward operations where a single function call is sufficient.

2. Batch Execution:

   • Executes multiple transactions in a batch.
   • Ideal for scenarios where multiple operations need to be performed atomically.

3. Default vs. Try/Catch:

   • Default Mode: Reverts the entire operation if any transaction in the batch fails.
   • Try/Catch Mode: Attempts to execute each transaction and logs any failures without reverting the entire batch.

Note

The executeFromExecutor function is specifically designed for executor modules, allowing them to handle both single and batch transactions with default or try/catch execution modes.

For more detailed information on executing and managing transactions in Nexus, refer to the Nexus GitHub repository.