OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Smart Contracts

Contracts — authereum

Authereum Contracts is a public, MIT-licensed repository of Ethereum smart contracts that support the Authereum account ecosystem, including proxy-based account logic, upgradeability, key permissions and relayed meta-transactions.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Contracts — authereum — OpenViST project profile in Smart Contracts.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use the repository when examining Authereum’s account-contract design or assessing whether its documented components fit an Ethereum wallet or application architecture.

Who it is for

  • Developers reviewing the contract architecture behind Authereum accounts.
  • Builders considering Authereum-compatible wallet or application components.

Documented uses

  • Inspect how Authereum account proxies connect to upgradeable logic contracts.
  • Understand the different permissions assigned to auth keys and login keys.
  • Review the documented flow for signed, relayed and batched account transactions.
  • Explore supporting ENS, firewall and account-module contracts.
Before you choose

Requirements & limits

The repository is public and identifies its license as MIT.

  • Accounts use user-owned proxies that point to upgradeable logic contracts; account state resides in the proxy.
  • Auth keys have administrative powers, while login keys are restricted to sending transactions.
  • The documented meta-transaction flow relies on signed messages being sent to relayers for broadcast.
  • The repository separates system contracts and supporting code, including tests that the README says are not deployed as part of the system.
  • JavaScript is identified as the repository’s primary language; the README describes Solidity contract components.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Review the Authereum contract layout and account design

Identify the roles of the repository’s contract directories and understand how Authereum accounts use proxies and logic contracts.

Before you start

  • Access to the public Authereum Contracts repository.

Steps

  1. Open the repository README.

  2. Review the Contract Design directory list to locate account, upgradeability, admin, ENS, modules, interfaces, libraries, tests, and utilities.

  3. Read Top Level Design Decisions to understand proxy creation, upgradeable logic, user-controlled upgrades, and the distinction between auth keys and login keys.

Expected outcome

A high-level map of the Authereum contract components and the documented account and key architecture.

Guide limitations

  • This is an architecture-review guide; it does not document contract installation, compilation, testing, deployment, or transaction execution.
  • The README states that test-directory contracts are not deployed as part of the system.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
16 October 2026
Original website title
authereum/contracts · Official homepage title · retained in its source language
How we review sourcesSuggest a correction