Skip to content

Releases: bcnmy/nexus

Release v1.0.1

11 Dec 08:44
@filmakarov filmakarov
v1.0.1
fd4db09
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
Release v1.0.1 Latest
Latest

Nexus v1.0.1 Release Notes

Overview

Nexus is a suite of smart contracts for Modular Smart Accounts compliant with ERC-7579 and ERC-4337, developed by Biconomy. The system provides a flexible and secure framework for account abstraction with modular components.

Key Features

Modular Architecture

  • Module Types Support:
    • Validators (signature verification)
    • Executors (transaction execution)
    • Fallback handlers
    • Hooks (pre/post execution checks)
      Multi-type modules installation flow enabled.

Account Abstraction (ERC-4337)

  • Full compliance with ERC-4337 standard
  • Support for packed user operations
  • Flexible validation and execution flows
  • Built-in paymaster support

Security Features

  • Emergency hook uninstallation with timelock (1 day)
  • Secure module management system
  • Registry integration for module verification
  • Comprehensive signature validation

K1Validator Implementation

  • Secure ECDSA signature validation
  • ERC-7739 Support
  • Safe sender management

Module Management

  • Module type verification
  • Support for multi-type modules

Execution Modes

  • Support for multiple execution types:
    • Single call execution
    • Batch execution
    • Delegate call execution
  • Try/catch execution support
  • Pre and post execution hooks

Standards Compliance

  • ERC-7579 (Smart Account Module Standard)
  • ERC-4337 (Account Abstraction)
  • ERC-1271 (Standard Signature Validation)
  • ERC-7739 (Nested Signature Validation)

Gas Optimization

  • Packed user operations support
  • Efficient module management using sentinel lists
  • Optimized signature validation

Security Considerations

  1. Module installation requires EntryPoint or self-authorization
  2. Emergency hook uninstallation mechanism with timelock
  3. Validator requirements ensure account security
  4. Safe sender verification for signature validation
  5. Registry integration for module verification

Integration Guidelines

  1. Initialize account with valid EntryPoint
  2. Install required modules (at least one validator)
  3. Configure hooks and fallback handlers as needed

Dependencies

  • Solady library for core utilities
  • SentinelList for module management
  • ExcessivelySafeCall for secure external calls

Compatibility

  • Solidity version: ^0.8.27
  • EVM compatible networks
Assets 2
Loading