Repository files navigation

Account2 is a contract designed to accomplish three key features not yet enshrined in the Ethereum protocol.

Account Abstraction the ability to have an account that will allow a relayer to act on behalf of the account owner asmsg.sender. This will solve three major UX challenges experienced in the first allowing all transactions to be bundled in a single transaction (i.e.: the necessity for an approve transaction before a swap transaction). Next it will allow a relayer to sponsor the gas for a transaction which is a major UX hurdle for Ethereum adoption. Lastly, a controlling key that has been compromised can be replaced in a single transaction transfering all the asset held in theAccount2 account.

Economic Abstraction the ability to pay an Ethereum transaction gas fee in any ERC20 token. Economic abstraction allows the user to pay for transaction in any ERC20 they hold in theirAccount2.

Account Linking the ability to associate accounts heirachically with a single private key. Since theowner of an account can be a contract we set the owner to a rootAccount2 and all requests will begin in the rootAccount2 and will be forwarded to subordinateAccount2 accounts. Using singly linked design we can establish any level of heirarchy with minimum overhead for each hop.

As described aboveAccount Abstraction usingAccount2 allows the user to link multiple wallets and reassign ownership to create the desired structure.

A more complex example of how account heirarchical linking works inAccount2 can be seen in the following diagram

UsingAccount2 eachAccount2 can be called from the owner requiring only a single transactino from the rootAccount2. Each subsequent call is passed to the child from theowner where themsg.sender is theowner without the need to validate a signature. An example of the above described transaction can be seen in the following diagram.

Economic Abstraction in our design theAccount2 owner can specify the value necessary for abstracted gas payment in the signed metatransaction using the following values:

gasToken - anaddress for the desired ERC20 to make the transaction payment

gasTokenRatio - auint256 wad1e18 value that represent the ratio ofgas togasToken amount. For instance if the underlyinggasToken is $AAVE the owner wants to pay 1 $AAVE per 1 gas they would use the following formula1/1e18 (actual ratio math should account for precision)

After the completion of a transaction using theexecuteAsRelayer method in theAccount2 contract the amount of gas used for the transaction is calculated using the following formula and transfered to thetx.origin.

uint256 amountToTransfer = (gasUsed + 21000) * gasTokenRatio;

Allowances and gas costs are the two main drawbacks to the current design. Allowances are instances where tokens owned by theAccount2 contract are not reset when a transfer occurs. This is only an issue in instances where the owner transfers ownership to another owner as part of a sale.

Gas costs can be reduced through golfing of the contracts but still carry some overhead. An alternative might be to enshrineAccount2 in protocol to have effectively zero gas cost to initiate a transaction.

Setup

forge install

Building

forge build

Testing

forgetest

Deployment & Verification

Inside theutils/ directory are a few preconfigured scripts that can be used to deploy and verify contracts.

Scripts take inputs from the cli, using silent mode to hide any sensitive information.

NOTE: These scripts are required to beexecutable meaning they must be made executable by runningchmod +x ./utils/*.

NOTE: these scripts will prompt you for the contract name and deployed addresses (when verifying). Also, they use the-i flag onforge to ask for your private key for deployment. This uses silent mode which keeps your private key from being printed to the console (and visible in logs).

See the official Foundry installationinstructions.

Then, install thefoundry toolchain installer (foundryup) with:

curl -L https://foundry.paradigm.xyz| bash

Now that you've installed thefoundryup binary,anytime you need to get the latestforge orcast binaries,you can runfoundryup.

So, simply execute:

foundryup

🎉 Foundry is installed! 🎉

WithFoundry, all tests are written in Solidity! 🥳

Create a test file for your contract in thetest/ directory.

For example,src/Greeter.sol has its test file defined in./test/Greeter.t.sol.

To learn more about writing tests in Solidity for Foundry, reference Rari Capital'ssolmate repository created by@transmissions11.

Usingfoundry.toml, Foundry is easily configurable.

For a full list of configuration options, see the Foundryconfiguration documentation.

AGPL-3.0-only

• femplate
• foundry
• solmate
• forge-std
• forge-template
• foundry-toolchain

If you want to contribute, or follow along with contributor discussion, you can use ourmain telegram to chat with us about the development of Account2!

If the answer is not there:

• Open adiscussion with your question, or
• Open an issue withthe bug

This project is work in progress and subject to frequent changes as we are still working on wiring up each individual node component into a full syncing pipeline.

It has not been audited for security purposes and should not be used in production yet.

We will be updating the documentation with the completion status of each component, as well as include more contributing guidelines (design docs, architecture diagrams, repository layouts) and "good first issues". See the "Contributing and Getting Help" section above for more.

We appreciate your patience until we get there. Until then, we are happy to answer all questions in the Telegram link above.