Bastion

Inspiration:

Since there are limited ways to manage and control funds on Aleo at the protocol level we thought account abstraction and decoupling fund management from the user account would be an interesting idea to explore.

What it does

It provides users with multi-sig options, ability to create blacklist or whitelists and propose transfers with custom amount of signers.

How we built it

We iterated through the program multiple times to strike a balance between privacy and on-chain computation fees and and eventually came up with a standard for a private multi-sig proposal system to propose different operations and it can be reused by other projects (changing modes, transfers, blacklisting, adding signers, etc).

Challenges we ran into

We had a few problems trying to deploy programs through the leo wallet and testing our program, we also had a few challenges trying to utilize the Sharded state to its fullest potential.

Accomplishments that we're proud of

1-First account abstraction on the Aleo blockchain 2-Keeping identity of users almost entirely private 3-Ready-to-use features to allow a party to manage a shared account

What we learned

We learned a lot about how ZK proofs works under the hood and Leo programming language and its cryptography primitives.

What's next for Bastion

We are going to expand the project and explore adding additional features like setting Allowances and setting custom conditions for proposing transfer and also trying to optimize the program further to increase privacy and computation efficiency.

Also we are going to eventually fix the UI when the network and Leo wallet gets more stable.

Built With

• leo