ARC-0100 – Compliance Best Practices for Developers and Operators on Aleo The Aleo Network Foundation (“ANF”) as well as the broader community of users and developers has a vested interest in minimizing illicit finance and other extralegal transactions from taking place on the Aleo network. To that end, we set forth the following best practices for bridges and validators to help minimize risks and create a robust network for our infrastructure service providers, developers, and end users. The Aleo Network Foundation has consulted with experts in the field, industry groups, and our community to inform this proposal. The below are best practices for bridges and validators because they are the key gating mechanisms. We propose a set of criteria to require (i) a time lock on funds and assets brought onto the Aleo network, (ii) blacklisting of suspect bridges, actors, and accounts on Aleo, (iii) robust cybersecurity measures to block bad actors, and (iv) monitoring and enforcement mechanisms. While we will require these best practices of any grantee of ANF, we cannot implement these unilaterally as a provider of a decentralized network. However, we will employ incentives, ecosystem best practices, and promote tools like blacklists to minimize illicit finance and other illegal transactions on the Aleo network. Best Practices for Bridges on Aleo In the beginning, liquidity on Aleo will come from two sources: centralized exchanges and bridging protocols. We assume as part of this document that centralized exchanges are required to follow the compliance requirements in their respective jurisdictions. Therefore, the recommendations outlined below are designed to be implemented by decentralized bridge operators on the Aleo Network. The best practices for bridge operators on Aleo are:

Summary The following document is to provide a primer for participants in the upcoming Aleo audit contest. Specifically, what follows is: What is Aleo? Scope of the contest A brief overview of the codebase Instructions on how to get started Further references What is Aleo?

Zero Knowledge Cryptography Alex Pruden How to Follow along ...and please add suggestions or comments!

Aleo Economic Model Aleo credits are fundamentally what makes Aleo a decentralized, permissionless network. Aleo's consensus model is product of years of research and engineering effort, and integrates learnings from two previous testnets All of the below is subject to tweaks, not major changes </br> Please keep all of this confidential for now!

Aleo Tech Tree digraph hierarchy { nodesep=1.0 // increases the separation between nodes node [color="#154BF9", fontname=Courier, shape=box] //All nodes will this shape and colour edge [color=black, style=dashed] //All the lines look like this Zexe->{DeFi Identity Gaming MachineLearning} Gaming->{Casino TBS}

Summary Our goals for Aleo are: (1) finality in consensus, (2) incentive compatibility and fair distribution of tokens, and (3) prover availability and fair sequencing of transactions. I propose separating each of these out into different layers of the stack instead of trying to fit all inside of snarkOS. This will enable us to efficiently prioritize the key blockers to mainnet while at the same time simplifying the system as a whole. It also provides a tangible application idea and clear direction for Aleo the company, distinct from the Aleo network. Motivation Much of the work to this point has been focused on integrating these properties into a single library - snarkOS. This potentially presents an elegant solution but also introduces additional complexity and in my opinion, technical risk. Also, in trying to combine these elements, we may end up "diluting" some of them because we're trying to put too much on a single layer that "does everything" versus an integrated system of individual parts that focus on doing one thing well. The goal of this proposal is to present an alternative path to achieve these principles while mitigating technical risk and maximizing the likelihood that we achieve our timeline for end-of-year launch. Put another way, it maximizes the time and engineering resources that can be potentially spent on other important aspects of Aleo, such as Leo, a package manager interface, etc.

## Prize Description ## ### Summary ### Multiscalar multiplication (MSM) operations are essential building block for zk computations. This prize will focus on maximizing throughput/minimizing latency of these operations on client-type devices and blockchain-based VMs, specifically the WebAssembly (WASM) runtime. Optimization Objective (1-sentence) Compute the highest number of MSM operations in 1 second Hardware & Benchmarks