Skip to content

ARC-TBD: Algo X EVM Accounts#375

Open
tasosbit wants to merge 2 commits intoalgorandfoundation:mainfrom
tasosbit:arc-smart-evm-accounts
Open

ARC-TBD: Algo X EVM Accounts#375
tasosbit wants to merge 2 commits intoalgorandfoundation:mainfrom
tasosbit:arc-smart-evm-accounts

Conversation

@tasosbit
Copy link
Copy Markdown
Contributor

@tasosbit tasosbit commented Mar 4, 2026

A LogicSig standard enabling EVM wallets to control Algorand accounts via EIP-712 signed ECDSA secp256k1 signature verification.

Abstract

This ARC specifies a LogicSig-based standard that allows any Ethereum (EVM) wallet address to control an Algorand account without requiring the user to manage a separate Algorand private key. A deterministic LogicSig program is compiled per EVM address by substituting the 20-byte Ethereum address as a template variable. To authorize an Algorand transaction, the EVM wallet signs the transaction ID (or atomic group ID) using EIP-712 typed structured data. The LogicSig verifies the ECDSA (secp256k1) signature on-chain using the AVM's native ecdsa_pk_recover and keccak256 opcodes, and approves the transaction if and only if the recovered Ethereum address matches the template owner. This approach requires no changes to the Algorand protocol and enables users of MetaMask and other EVM wallets to interact with Algorand dApps using their existing credentials.

@tasosbit tasosbit force-pushed the arc-smart-evm-accounts branch from 59c9edd to 2a895d3 Compare March 4, 2026 13:24
@tasosbit tasosbit force-pushed the arc-smart-evm-accounts branch from 2a895d3 to 973a222 Compare March 4, 2026 13:25
@tasosbit
Copy link
Copy Markdown
Contributor Author

tasosbit commented Mar 5, 2026

The implementation repo is here.

Some discussions have been started in the repo discussions board to keep things thematically grouped, as the flat discussions view in popular arcs can get very noisy. we can sync conclusions at a later stage.

EIP-712 Chain ID: Singular or per-network? Impacts generated addresses

Add Network to the EIP-712 signed message type?

Updated author username format in the document.
@tasosbit
Copy link
Copy Markdown
Contributor Author

tasosbit commented Mar 7, 2026

Opened a request to register chain ID 4160.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant