Skip to main content

FAQs

Do I need a smart account for every Ethera flow?​

No. Some Ethera flows use direct wallet transactions, while others execute through smart accounts and UserOperations.

For example:

  • Sepolia to Rollup: ETH funding uses a direct wallet transaction through ComposeL1Bridge
  • Rollup to Rollup: Bridging uses smart accounts on both rollups and a composed cross-rollup payload

When a flow requires smart accounts, the Ethera SDK handles smart-account creation and management automatically. From the user perspective, the connected wallet still signs the flow normally.

Why does the Sepolia to Rollup flow not use smart accounts?​

Because that route starts with a direct bridge transaction on Sepolia and follows the deposit and finalization path into the rollup.

For Sepolia to Rollup funding, the wallet submits a normal call to ComposeL1Bridge on Sepolia. The destination-side delivery then happens through the bridge settlement path on the rollup, so the source transaction does not require a smart-account execution layer.

This is different from Rollup to Rollup, where Ethera uses smart accounts and UserOperations as part of its cross-rollup execution model.

What is the difference between my connected wallet and my smart account?​

Your connected wallet is the primary user-owned account. A smart account is a contract-based account that Ethera can create and use for flows built around Account Abstraction.

Depending on the route, Ethera can use one, the other, or both. A direct bridge call can come straight from the connected wallet, while a cross-rollup flow can use the wallet for approval and the smart account for execution. In those flows, the connected wallet remains the primary user-owned account where assets typically originate and are ultimately received, while the smart account acts as the execution layer that coordinates the transaction flow across chains.

Why do some explorer pages show value = 0 for a successful transfer?​

This is expected for smart-account flows that submit UserOperations through the ERC-4337 EntryPoint. The explorer value field reflects the outer execution envelope, while the actual ETH movement happens inside the smart-account calls carried by the UserOperation payload.

For example, this Rollup A transaction shows value = 0 on the outer transaction even though Ethera still moved ETH successfully.

Direct Sepolia to Rollup funding does not behave this way, because the wallet sends a normal Layer 1 bridge transaction.

Do I need a paymaster to use Ethera?​

No. A paymaster is optional.

Paymaster support can improve the user experience for smart-account flows, but it is not part of Ethera's coordination model and it is not required for atomicity. Direct wallet transactions, such as the Sepolia to Rollup ETH funding flow, do not use a paymaster at all.

Do smart account addresses match across Rollup A and Rollup B?​

Yes, when you create them with the same multiChainIds configuration in the Ethera SDK.

multiChainIds is an optional parameter on useSmartAccount(...) that tells the SDK to create one smart-account identity across multiple supported chains. When Rollup A and Rollup B are included in the same array, the SDK derives the same smart-account address for both rollups.

In practice, that means the account can execute on both rollups while keeping one shared address.

// Create one smart-account identity that can execute on both rollups.
const smartAccountQuery = useSmartAccount({
  chainId: rollupA.id,
  multiChainIds: [rollupA.id, rollupB.id]
});