Biconomy Infrastructure Upgrade

[SarahSync]

Description

To ensure continued compatibility and access to the latest account abstraction features, we must upgrade our Biconomy infrastructure. This involves migrating from existing account versions to the latest Nexus or MEE standards by the end of February.

User Story

As a System, I want to operate on the latest Biconomy infrastructure so that our transaction processing remains secure, gas-efficient, and compatible with upcoming Modular Execution Environment (MEE) updates.

Goal: Complete the migration of all smart accounts and transaction flows to the latest Biconomy version before the February 28, 2026 deadline.

Acceptance Criteria

GIVEN the system is already utilizing Nexus accounts
WHEN infrastructure updates are applied
THEN the system must be updated to the latest MEE versioning standards following the MEE Versioning Guide.

Tech Details

• Account Type Audit: Verify the current account implementation version in the codebase to determine the correct migration path (V2 → Nexus vs. Nexus → MEE).
• SDK Update: Update the Biconomy SDK to the latest version compatible with Nexus/MEE.
• Smart Account Factory Update: Update the factory address and implementation logic for deploying new user accounts.
• Validation Modules: Ensure existing validation modules (e.g., ECDSA, Session Keys) are compatible with the new modular Nexus architecture.
• MEE Implementation: If applicable, configure the Modular Execution Environment to support cross-chain or complex execution logic.

Notes/Assumptions

• Deadline: This is a hard deadline set for February 28, 2026.
• Documentation: All changes should reference the official Biconomy Migration Documentation.
• Infrastructure Parity: Both staging and production environments must be synchronized on the new infrastructure before the deadline.

[sundayonah]

Biconomy V2 → Nexus Migration

Migration path

We are currently on Biconomy V2 (SimpleAccountFactory, INFINITISM 1.0.0 in the aggregator). We will migrate V2 → Nexus, then align with the latest MEE versioning per the MEE Versioning Guide.

---

Acceptance criteria

GIVEN the system is already utilizing Nexus accounts

After audit i confirmed the system currently uses Biconomy V2/Infinitism. We will complete the V2 → Nexus migration first so the system operates on Nexus, then apply the latest MEE versioning per the MEE Versioning Guide.

WHEN infrastructure updates are applied

When we apply the infrastructure updates: Nexus/MEE bundler and paymaster endpoints, Nexus factory and implementation addresses, paymaster payloads, and any SDK or config updates in the aggregator.

THEN the system must be updated to the latest MEE versioning standards following the MEE Versioning Guide

We will update to the latest MEE versioning standards (e.g. MEE 2.1.0 or 2.2.1 per the MEE Versioning Guide), including correct implementation/bootstrap addresses, preservation of accountAddress for existing accounts, and required validator and factory updates.

---

Tech details

Account type audit

The system uses Biconomy V2/Infinitism (SimpleAccountFactory at 0x9406Cc6185a346906296840746125a0E44976454, paymaster smartAccountInfo: INFINITISM 1.0.0 in the aggregator). The migration path is V2 → Nexus, then MEE versioning.

SDK update

We will use the latest Biconomy SDK compatible with Nexus/MEE (e.g. AbstractJS and any account packages) for migration scripts or future SDK use. In the aggregator we will update bundler/paymaster usage to Nexus/MEE (endpoints and payloads) so all transaction flows use the new infrastructure.

Smart account factory update

We will replace the current V2 factory address and deployment logic with the Nexus factory and implementation from the Contracts and Audits page for our chains. New accounts will be created as Nexus; existing V2 accounts will be migrated in-place per the V2 → Nexus guide, preserving addresses.

Validation modules

We will ensure existing validation (ECDSA owner, and session keys if used) is compatible with the Nexus modular architecture, following the validator setup in the Biconomy migration docs and AbstractJS documentation.

MEE implementation

We will configure the Modular Execution Environment to the chosen MEE version (e.g. 2.1.0 or 2.2.1) per the MEE Versioning Guide. If cross-chain or complex execution is required, we will enable and configure it per the official Biconomy documentation.

---

@SarahSync