28. Smart Wallets and Account Abstraction

eBattery’s Web3 experience aims to let investors manage their economic rights securely without having to learn the technical details of the blockchain. Joining a station project, claiming the monthly profit share or transferring investment units should be understandable, verifiable transactions under the user’s control.

With traditional wallet use, users may be expected to protect private keys, choose a network, hold a separate asset for transaction fees and interpret technical signature messages. Placing all of these responsibilities on the user in the same way creates a significant barrier to use for a platform that aims to reach broad audiences.

eBattery’s smart wallet approach this experience Account Abstraction — abstracting the account with its architecture. The account's transaction approval, authority limits, fee payment method and recovery rules are handled in a programmable structure. While the user moves within an app experience they know, the authorization and record-keeping that investment transactions require are preserved.

This section defines the smart account architecture and security principles that eBattery uses as the basis for its Web3 phase. The aim of the structure is not merely to reduce the number of transactions. So that users can understand what they are allowing, limit the permissions they grant and keep control of their account is the foundation of the design.

28.1 Moving from a Web2 Account to Web3 Access

The eBattery user account is the shared access point for the map, route planning, community and other Web2 modules. Web3 access is linked to this account; however, signing up for the app does not by itself mean an investment account is opened or authority for financial transactions is granted.

When a user moves into the Web3 area, three distinct relationships are established:

Layer Core function
eBattery user account Managing the app session and user preferences
Investor e-ID Linking identity, investor eligibility and project access conditions
Smart wallet Managing onchain assets and authorized transactions

This distinction matters for both user experience and security. A person being signed in to the app does not mean they are eligible to join a specific investment project. Likewise, completing identity verification does not by itself allow transactions to be made from the wallet.

The move to Web3 proceeds as the user reviews the relevant service terms, completes the required eligibility steps and sets up the authorization method for their smart account. The wallet connection is linked to the user and investor identity through a verified transaction.

For users who want to keep using Web2, Web3 participation is not mandatory. Access to the map, community or Game Zone is not tied to opening an investment account, acquiring a digital asset or signing with a wallet.

Game points, charge credits, payment balances and investment assets also do not convert into one another during this transition. A shared user account does not mean that different economic functions are merged under the same balance.

28.2 ERC-4337-Based Smart Account Structure

eBattery’s smart wallet architecture, on supported EVM networks, the ERC-4337-based smart account approach is based on.

ERC-4337 allows an account's transaction validation logic to be defined by smart contract code. The user's transaction is submitted through a structure called a UserOperation. Bundlers carry these operations on-chain in an appropriate way, while the EntryPoint contract acts as a central protocol component in the validation and execution process. An optional paymaster can cover the transaction fee on the user's behalf.

From eBattery's perspective, the components of this architecture are positioned as follows:

Component Role within eBattery
Smart account Applying the user's signature, authority and execution rules
UserOperation Technically representing the transaction the user approved
Bundler Checking the transaction and submitting it onchain via a supported EntryPoint
EntryPoint Performing account and, where present, paymaster verification
Paymaster Covering the network fee within the defined policy
Account creation component Setting up the new smart account with the right initial permissions

A smart account does not have to be tied to a single signature method. The ERC-4337 ecosystem offers a structure that can support different signature methods, programmable account rules and fee abstraction scenarios. However, the behavior of features such as passkeys, session keys or recovery is designed separately in the account implementation used.

During eBattery account creation, signing authority, the recovery setup and active modules are verified together. A starting model built on creating an account with a wrong or temporary authority and correcting it later is not used.

The transaction signature is linked to the relevant account and network context. ERC-4337 requires the signature to be bound to the network ID and the EntryPoint address to protect against replay attacks. In addition, eBattery checks the transaction type, authority limits and application-level validity conditions.

The architecture is designed so as not to create unnecessary dependence on a single bundler service. The same transaction resubmitted through an alternative service does not create a second economic transaction. Account ordering and replay-protection controls are kept in place.

28.3 Passkey Sign-In and Transaction Approval

A passkey is an approach that authenticates the user with a cryptographic credential instead of a password. In the user experience, this can be completed with face recognition, a fingerprint or a local verification method supported by the device.

In the FIDO approach, passkeys use service-specific public-key authentication. There are types that are bound to a device or synced across devices through a suitable provider. When biometric verification is used, the biometric data does not become a credential sent to the service like a password.

At eBattery, passkey is considered in two separate usage contexts:

Account sign-in, lets the user open an app or web session.

Financial transaction approvalauthorizes a specific onchain transaction.

Although they appear within the same user experience, these two actions serve different purposes. A verification response produced for sign-in cannot be used as permission to buy an investment unit or to change wallet authorization.

WebAuthn ties the authentication response to the service context and the verification request presented. In eBattery's transaction approval, this request is bound to the transaction content, account, network and validity information. The relevant RP ID, origin and user verification checks are applied according to the supported contexts of the mobile and web channels.

For a smart account to accept a passkey signature, a suitable verification component is needed. OpenZeppelin's WebAuthn smart account documentation offers an example approach for checking WebAuthn verification responses in smart contracts. eBattery's technical choice jointly considers whether the signature algorithm and verification path used are supported on the target network, as well as their cost and security properties.

The ease of using a Passkey does not make the transaction summary unnecessary. Before approving, the user sees what they are buying, what amount will be spent and what authorization will be given. The device’s biometric verification window is not regarded as a contract screen that automatically shows all financial terms.

For this reason, eBattery treats the match between the transaction summary shown to the user and the content of the transaction being signed as part of its security design.

28.4 Shared Account Access Across the Mobile App and Web

An eBattery user can access the same investor account through supported mobile app and web interfaces. Shared access does not rely on devices downloading the same private key from the application server.

Account continuity is provided through the verified relationship among the user account, the investor e-ID, the smart account address and the authorized identity credentials. When a user signs in from a different device, they can see their portfolio and past transactions; for a financial transaction, they must also have access to the authorized signing method.

The trust relationship between mobile apps and the web domain is established through the relevant platform mechanisms. On the Apple side, associated domains and webcredentials association; on the Android side, Digital Asset Links configuration, are the technical elements of the credential link between the app and the service domain.

The following principles apply in the shared access model:

  • Signing in from a new device is not treated the same as granting new transaction authority.

  • Supported domain names and app identifiers are verified.

  • Adding a new signer is approved under the existing security policy.

  • The authority to view an account is separated from the authority to move assets.

  • Transactions from different devices belonging to the same user are managed through a shared account queue.

Whether a passkey can be used on another device depends on the credential provider and the supported sync or cross-device authentication features. For this reason, automatic and unconditional key portability across all operating systems is not assumed.

Likewise, a user account being able to access more than one network does not mean that the same smart account address or the same account setup exists on every network. Network and account relationships are shown to the user clearly; no automatic bridging is done between assets.

28.5 Gas Sponsorship and Paymaster Policy

Gas sponsorship reduces the need for the user to separately acquire the network's native asset for certain transactions. While the transaction looks simpler to the user, the network cost is covered by another party under the applicable policy.

eBattery's paymaster approach, is transaction sponsorship with a defined scope and budget. A sponsored transaction does not mean an economically cost-free transaction; what changes is who bears the cost.

Transactions eligible for sponsorship are determined by the user flow. Transactions such as activating a smart account or an eligible profit share claim may be assessed under the relevant policy. The support that applies to each transaction is shown on the confirmation screen.

The Paymaster policy controls the following areas:

Control area Purpose
Permitted contract and transaction types Preventing sponsorship from being used for unintended purposes
User and account eligibility Identifying accounts that can benefit from support
Per-transaction cost limit Limiting unexpected network fees
Periodic usage limit Managing the sponsor budget sustainably
Repeated and suspicious requests Reducing automated abuse
Validity period Preventing old sponsor approvals from being reused

Paymaster security is addressed together with verification, transaction simulation and abuse controls. ERC-4337 documentation also treats protecting paymaster resources against abuse and denial-of-service attempts as a separate security area.

Sponsor approval does not replace the user’s signature. A paymaster may cover the network fee; this does not grant authority to purchase investments or transfer assets on the user’s behalf.

When sponsorship cannot be applied, the transaction is not automatically continued by charging the user’s balance. The user is shown the new cost and the required approval is obtained. A technically supported alternative where the user pays is presented with the same clarity.

The sponsor budget is not covered, without explanation, from stations’ maintenance reserves or investors’ unclaimed profit shares. Which service budget the relevant cost belongs to is defined.

28.6 Session Keys and Limited Permissions

Session keys let the user grant authority that is limited in duration and scope for specific transactions. The aim is to reduce the constant use of the main signing method for repeated transactions while preserving control of the account.

These permissions are not a ready-made feature that ERC-4337 defines on its own. They are implemented within the account's validation logic or authorization modules. ERC-4337's relevant documentation also states that session keys are controlled by wallet-specific rules.

eBattery's session permissions are managed through an explicit consent record. This record may include the following limits:

  • The network and smart account it applies to.

  • Permitted contracts.

  • The types of actions that can be called.

  • Permitted assets.

  • Limit per transaction and in total.

  • Fixed or allowlisted recipient addresses.

  • Start and end time.

  • Number of uses and cancellation terms.

For example, a user may grant limited authority only to claim their profit share from a specific distribution contract to their own designated account. This authority does not extend to selling investment units, changing the recipient address, or approving spending under another contract.

No authority to move assets is granted for actions such as viewing the portfolio, reading reports or receiving notifications. Ease of reading is not built on unnecessary signing authority.

Limited permissions are not protected only by an allowlist kept on the application server. The relevant onchain transaction must meet the permission scope in account verification. In batch transactions too, every sub-transaction is checked; exceeding the limits through general-purpose calls is prevented.

The user can view and revoke active session permissions. For an onchain revocation to take effect, the relevant transaction must be finalized; signing out of the app alone is not considered to have removed all onchain permissions.

Token spending permissions are also tracked separately from session keys. Revoking a session permission may not automatically remove a spending permission previously granted to another contract. The security screen shows these two types of permission separately.

28.7 User Confirmation in Investment Transactions

In investment transactions, eBattery bases the user's confirmation on a transaction summary whose economic meaning is clear. Reducing technical complexity does not make the decision invisible.

Before the transaction, the user is shown the following information:

Transaction Key information on the confirmation screen
Launchpad participation Project, number of units, total price, fees and funding terms
Secondary purchase Unit price, total payment, periodic entitlements and exchange terms
Secondary sale Units sold, sale price, 1% commission and net amount
Profit share claim Period, gross entitlement, deductions, net payment and recipient
Spending permission Authorized contract, asset, limit and scope
Security change Signers to be added or removed and changed authorities

Transactions with significant economic consequences are not carried out relying only on an open app session. Appropriate re-verification is applied for actions such as purchases, sales, new spending permissions, signer changes and recovery configuration.

Technically, multiple steps can be executed in the same transaction group. For example, the required payment permission and the purchase call can be prepared together. The user is shown the combined effect of these steps; no hidden or unlimited authority is granted under a single approval.

Structured data approaches such as EIP-712 may be used for supported signed messages. This standard allows data to be signed with its type and field context, but it does not by itself guarantee replay protection or that the user interface is understandable. Transaction order, expiry, target contract and use case are checked separately.

ERC-1271 compatibility is considered for the verification of smart account signatures by other contracts on the platform. This way, the account can offer contract-based signature verification without depending solely on systems that expect a traditional private key signature.

Pre-transaction simulation helps show expected asset movements and possible errors. However, price, eligibility or contract status may change until the transaction enters the chain. For this reason, the price, amount and validity limits accepted by the user are also checked during execution.

28.8 Wallet Recovery and Device Change

Changing a device, recovering the app account and recovering the smart wallet’s signing authority are different processes. eBattery does not combine these cases under a single “forgot my password” action.

The recovery approach distinguishes three core scenarios:

The user gaining access to another valid signing method: A new device or new credential can be added to the account through an existing authorized method.

Being able to use the synced passkey on the new device: Under supported provider and device conditions, the same credential can be accessed again. This may not require creating a new signer on the account.

Loss of access to all normal signing methods: The independent recovery mechanism defined when the account was set up is applied.

eBattery's recovery design is approached so as to support mechanisms such as a backup signing method, pre-authorized recovery parties or a suitable multi-approval arrangement. Who can change signers under which conditions with the chosen method is explained to the user when the account is set up.

A recovery request does not create normal transfer authority. The request goes through the required verifications; waiting and objection mechanisms apply; and notifications are sent to existing security channels. If the user still has a valid signing method, they should be able to intervene against an unauthorized recovery attempt.

Access to an email account, or submitting an identity document to the support team, is not on its own treated as authority to move onchain assets. Identity review may only be one component of a predefined recovery policy.

It is also taken into account that a synced passkey may represent the same credential on more than one device. Signing a lost device out of app sessions does not necessarily invalidate the signing credential that device can use on-chain. Where needed, the account signer is replaced and the related session authorizations are revoked.

After recovery, investment units and past entitlements can continue in the same account. If a new address must be used, the economic rights and eligibility records go through a controlled transfer process. Past profit shares or period-end records are not duplicated on the grounds that a new account was opened.

When no valid signature or applicable recovery authority remains, gaining access to the app account alone cannot recover the wallet. For this reason, setting up a recovery arrangement is a core part of account security before investing.

28.9 Asset Control and Custody Model

The core design principle of eBattery's smart wallet approach is that the investor has meaningful control over asset movements. This control is not assessed solely by a “wallet owner” label shown in the interface.

The questions that determine the real control structure are as follows:

  • Who can produce the transaction signature?

  • Who can add a new signer to the account?

  • Who can complete the recovery process?

  • Who can change the account's code or verification modules?

  • Who can lift spending limits?

  • Who can transfer assets to another address?

The answers to these questions are the basis of the custody model. An account requiring the user's signature is not, on its own, a sufficient indicator of control if another party can change that condition through broad upgrade or recovery authority.

In eBattery's model, the authority to manage app sessions, provide paymaster sponsorship or verify investor eligibility is not automatically turned into authority to withdraw assets from the user's wallet.

Authority or service Its scope
User account management App access and preferences
Investor eligibility check Access to specific investment transactions
Bundler service Submitting the authorized transaction to the network
Paymaster service Covering the network cost of an eligible transaction
Wallet signing authority Approving transactions within account rules
Recovery authority Reorganizing access under predefined conditions

If the smart account is upgradeable or modular, the security impact of these authorities is shown separately. Updates that change control of the account are not treated like an ordinary app update. Controls such as user approval, multiple authorizations or time delays are clearly defined according to the account model used.

The investor’s wallet, the Launchpad escrow structure and the distribution pool are also separate structures. Money held in the escrow contract during funding is not a wallet balance the user can freely spend directly. Likewise, an unclaimed profit share is an economic right in the relevant distribution mechanism.

The permissioned transfer rules for RWA units are a layer separate from wallet control. Even if the user is the signer of their wallet, an investment unit can only be transferred to eligible recipients and under supported conditions. This feature does not mean that all of the account's assets are freely managed by the platform.

The custody explanation shown to the user reflects the technical and legal authority structure in use. The term "smart wallet" is not used on its own as a claim of full user control, institutional custody or automatic recovery.

28.10 Transaction History and Security Notifications

The final layer of the smart wallet experience is following transactions and security changes in a clear way. Users should be able to see not only their balance, but also the events that affect that balance and their account permissions.

The transaction history brings together the following information:

  • Transaction type and the related station project.

  • The network and smart account used.

  • Asset, amount and counterparty.

  • Fee terms approved by the user.

  • Network cost that is sponsored and cost covered by the user.

  • UserOperation reference.

  • The on-chain transaction reference, if any.

  • The actual execution result.

  • The relevant report, sale or profit share record.

Status tracking separates stages such as preparing, awaiting signature, sent, executed, failed and finalized. A bundler accepting a request does not mean the financial transaction has taken place.

Because a single on-chain transaction can contain several user operations, the top-level transaction record is not enough. eBattery checks the outcome of the user’s own operation and the expected asset movements. If a failed execution still incurred a network cost, that cost is not shown as an executed investment purchase or a sale commission.

Security history, on the other hand, is tracked separately from financial transactions:

  • Sign in from a new device.

  • Adding a new passkey or signer.

  • Revoking signing authority.

  • Creating and revoking session keys.

  • Granting or changing a spending permission.

  • Opening of the recovery request.

  • A change in the account module or security policy.

  • Suspicious transaction attempts.

Signing out of a device only tells the user that the app session has ended. If onchain permissions need to be revoked, this is shown separately and its finalization is tracked.

Notifications direct the user to the transaction details and the appropriate security step. Sensitive information such as a full private key, a passkey secret or recovery authority is not requested in a notification, a support message or an email.

Thanks to this integrity, eBattery’s smart wallet reduces technical detail while keeping economic and security responsibilities visible. By distinguishing between their access to the app, investment eligibility, transaction signing and account recovery authorities, the user can manage Web3 services within a single experience.

Search eBattery

Search for a feature, guide or topic.

Starting pointsFinding a charging station →Sample RWA project →Guides and news →