Aura Tech Stack

Aura Network is a high performance Layer 1 ecosystem with built-in modularity, leading the mass adoption of Web3 in emerging markets.

Aura Network Tech Stack

The Aura infrastructure landscape has been revamped to fully adopt innovation in user experience and sustainable economics. We can divide the landscape into 4 major planes.
Infra Applications
Mobile SDK
Foundation Contract Suite
Pyxis Smart Account
Fee Registry
Plugin Manager
Smart Account Module
CosmWasm Module
Other Cosmos Modules

Aura Daemon

The main Aura node client. As this is implemented using the Cosmos SDK, Aura inherits the stability and security of the Cosmos stack. It is also IBC compatible, making Aura capable of directly communicating with more than 80 other Cosmos chains. Apart from the default Cosmos modules, there are 2 other modules implemented by Aura:

Smart Accounts Module

The native account abstraction module that enables programmable accounts. A Smart Account is a smart contract that represents an user account on the blockchain. SAM accepts transactions from a client, determines if the client is interacting with its smart account, then forwards the transaction to the contract. This process is plugged into the normal transaction flow of Cosmos so that the account can also perform normal transactions without creating a separate logic flow.

Fee Enforcement

This is a native module that implements sustainable economic design that includes a new approach to charging fees, with fees being applied at the application level (fees on application revenue) as opposed to the usual way of only being limited to the blockchain layer (gas fees). Enforcement of this requirement, to our knowledge, has never been done among permissionless networks, and Aura will be pioneering its implementation. This can be understood as an income tax for dApps to contribute to the community pool as they are directly benefiting from the public infrastructure of Aura.

Foundation Contract Suite

A collection of smart contracts that are governance gated, highly privileged, and can directly communicate with Aurad to manage different types of transactions. Aurad has the SAM and Fee Enforcement Module serving as the entry point to different transaction logic. However, some particular logic paths are separated into a suite of highly privileged smart contracts so that we can have a more robust development architecture.We call this “Foundation Contract Suite” as they have an ecosystem-wide effect, and are implemented to directly complement the SAM and Fee Enforcement native module, rather than being implemented for independent DAPPs. There are currently 2 class of contracts:

Pyxis Smart Account

A collection of contracts serving the SAM. This includes a main smart account contract and a nimble architecture of plugins that can be easily enabled or disabled on demand.

Fee Registry

A collection of contracts that captures value from various dApps deployed on top of Aura.
The foundation contract suite provides a highly modular approach to ecosystem wide features like AA and tax structure. The aim of this architecture is to be able to swap out, upgrade, and add modules as the protocol develops and swiftly accommodate demands for new requirements or adjustments. Accordingly, the design consists of many granular single-purpose logic units, starting from a runtime upgrade (aurad) and pushing the rest of the logic to application level (contract).

Aura Software Development Kit

Client libraries for various dApps, web or mobile applications
AuraJS remains to be the most popular client side library for front-end (javascript) to interact with Aura. All logic on how to construct transactions that interact with EOA or Smart Account are abstracted away from the client side.
Native Flutter implementations for client libraries are also very important for the development of native mobile applications.

Infrastructure Application

The signature infrastructure applications developed by the Aura team remains the same with the addition of Aura Pay, a custodial infrastructure for facilitating Web3 onboarding. They are:
img_circle_logoAura ScanAuraJS remains to be the most popular client side library for front-end (javascript) to interact with Aura. All logic on how to construct transactions that interact with EOA or Smart Account are abstracted away from the client side.
img_circle_walletAura PayPay is a collection of centralized, opt-in key custodial services that abstract the transaction execution of an account on Aura. This is an advanced version of the Pay Master concept of EVM blockchain where the Pay part can be directly invoked from Web2 payment gateway while retaining the transparency of Web3.
img_circle_safeSafeThe native multisig tool for asset management and chain interaction of Aura. However, with the addition of smart accounts, a new version of Safe will be available to support this new account type.
img_circle_horoHoroscopeThe powerful indexing service that complements all dApps on Aura. Horoscope provides GraphQL interfaces and a powerful CLI tool for constructing sub-graph services. This remains the de facto data indexing pattern for dApp builders on Aura Network

Build Your DApp With Aura