1. Performance - more executions can be processed by the network per second due to the unique nature of the Narwhal mempool

2. Decentralization - the theoretical upper limit of participating validators is higher than other PoS systems

Bullshark/Narwhal is already in production, with both Sui and Aptos using it for their networks. However, we are facing some challenges adapting it to our stack due to the privacy-preserving nature of our VM. These challenges have caused some unanticipated delays on our mainnet roadmap. The engineering team is currently working hard over the course of the next month on a new validator node implementation for running Bullshark/Narwhal for the next month. This node will allow for wider participation in the Aleo network consensus, starting with the 50 pre-selected validators and growing from there. Importantly, we still anticipate mainnet launch by the end of the year. Note that while this work is ongoing through August, there may be some instability on the current network. Our infrastructure and engineering teams will still provide support and respond to bug reports. However, since implementing the new consensus algorithm is the priority for the next month, we ask for your patience in the event of an unplanned network outage or other instability. Privacy is a critical human right in the digital age and is an essential prerequisite for an actually-secure internet. Thank you very much for being a great community as we count down the final months leading up to mainnet launch!

Core Engineering Updates
Merges:
snarkVM
https://github.com/AleoHQ/snarkVM/pull/1736: Introduce formal Rejected wrapper
https://github.com/AleoHQ/snarkVM/pull/1737: [Fix] Fixes verify_execution on functions that call closures
snarkOS
https://github.com/AleoHQ/snarkOS/pull/2474: Bump snarkVM to v0.12.6
https://github.com/AleoHQ/snarkOS/pull/2480: Filters out fee transactions from the unconfirmed pool
leo
https://github.com/AleoHQ/leo/pull/2427: [Feature] Support to_x_coordinate for groups
https://github.com/AleoHQ/leo/pull/2433: [Feature] Support ChaCha::rand_*
https://github.com/AleoHQ/leo/pull/2436: impl Mapping::contains, Mapping::remove

In-Progress
snarkVM
https://github.com/AleoHQ/snarkVM/pull/1727: [Feature] Introduce ArrayType
https://github.com/AleoHQ/snarkVM/pull/1728: [Refactor] Generalize register access
https://github.com/AleoHQ/snarkVM/pull/1738: Improve some doc about multiplication gadgets
snarkOS
https://github.com/AleoHQ/snarkOS/pull/2484: Bump snarkVM to v0.13.0
leo
https://github.com/AleoHQ/leo/pull/2439: [Fix] Fix issues related to flattening

There are many more merges and in-progress pull requests to check out. We recommend heading to https://github.com/AleoHQ for a full weekly review.

Core Engineering Updates Merges: snarkVM https://github.com/AleoHQ/snarkVM/pull/1714: [tests] Some negative instruction parsing tests https://github.com/AleoHQ/snarkVM/pull/1716: [tests] Some command parsing tests https://github.com/AleoHQ/snarkVM/pull/1718: Adds accessors for structs and records in Program https://github.com/AleoHQ/snarkVM/pull/1719: Fix program fetching in cost function snarkOS https://github.com/AleoHQ/snarkOS/pull/2461: [Feature] Basic REST endpoints for finalize scope https://github.com/AleoHQ/snarkOS/pull/2464: Update snarkVM to v0.12.4 leo https://github.com/AleoHQ/leo/pull/2426: [Feature] Casting via the as operator

In-Progress snarkVM https://github.com/AleoHQ/snarkVM/pull/1717: Add cost estimates for finalize fees snarkOS https://github.com/AleoHQ/snarkOS/pull/2469: Use a custom function to deserialize the IndexMaps in BlockLocators https://github.com/AleoHQ/snarkOS/pull/2474: Bump snarkVM to v0.12.6 leo https://github.com/AleoHQ/leo/pull/2427: [Feature] Support to_x_coordinate for groups

There are many more merges and in-progress pull requests to check out. We recommend heading to https://github.com/AleoHQ for a full weekly review.

Technology has dealt a tangible blow to protecting our privacy. Much of what individuals or organizations do is now in the public domain. Third parties control, store and use personal and corporate data, patterns, preferences and activities. Many new business models are based on the collection, organization and resale of our personal data.

What is the problem?

If you get something for free, then the product is you. Or your personal data is stolen from you and sold behind your back to digital corporations.

It is important to understand that personal data is not limited to birthday and city of residence. Correspondence, financial and medical data, geolocation tags, addresses, search histories, preferences and interests are not a complete list of information stored on the servers of these companies. At the same time, despite all attempts to protect virtual databases from hacking, you cannot rely on their reliability. According to a study by Gemalto, 2.6 billion different personal records were compromised in 2020 alone. On average 82 records every second.

A striking example is the high-profile case involving Facebook founder Mark Zuckerberg in the spring of 2018. For hours, Mark tried to explain how the personal data of more than 87 million Facebook users was used in the campaigns of Ted Cruz, Donald Trump and ahead of the UK’s Brexit referendum. It was a turning point — literally everyone started talking about the need to protect personal data.

Let’s think about how to counter the theft and trafficking of your personal data

Will the use of blockchain solve the problem of data security?

Blockchain technology can limit the impact of this privacy erosion while still providing personal information if it is needed for a case. For example, a user may store personal information on a blockchain and temporarily make it public in order to receive a particular service. Bitcoin and other digital currencies based on blockchain technology have demonstrated that reliable and transparent settlement is possible using a decentralized peer-to-peer network and a distributed public ledger of transactions.

But there is one problem. Blockchain was created as a way to store data forever. Alas, this is against modern privacy laws.

On May 25, 2018, the Law on General Data Protection Regulations was adopted. The General Data Protection Regulation is a new law that protects data security and strengthens control over information and data of individuals on digital platforms.

The question is why the dispute? What is the connection between blockchain and this regulation? The problem here is that if you read about the regulation, which is the General Data Protection Regulation, you will see that it is against blockchain.

In its current popular form, blockchain is not GDPR compliant. Information stored on the public network cannot be deleted, which means that you cannot give users the right to delete or edit their information.

However, many experts believe that the best way to avoid or comply with the General Data Protection Regulation is to use a blockchain that uses completely anonymous data.

Aleo is the first platform to offer completely private apps.

Aleo achieves this by using decentralized systems and zero-knowledge cryptography to secure user data online. At its core, Aleo offers users and application developers unlimited computing resources with absolute privacy, it can be said to offer personalized Web3 services.

Using zero-knowledge (zero-knowledge) cryptography, Aleo moves the execution of smart contracts off-chain to enable a wide range of decentralized applications that are completely private and can scale to thousands of transactions per second.

Another benefit that I couldn’t highlight is that Aleo created their programming language for formally validated zero-knowledge applications — Leo

Web developers publish their work to the Aleo Package Manager (PM), a registry that freely hosts and distributes commonly used code. With Aleo PM, developers can quickly import packages to build a new web application. We also released a new Teams feature that allows developers to work together, it will make it easier for developers to collaborate on complex packages like SHA256 or AES and easily publish their work for others to use.

To make it easier for developers to get started, Aleo PM has been integrated into Aleo Studio, the first IDE for private web applications.

With Aleo Studio, developers can now quickly search for and import new packages to use in their applications.

Aleo is a layer 1 blockchain that uses zero-knowledge cryptography to build scalable and private decentralized applications and is the first platform to offer fully private applications.

POS will ensure block accuracy, i.e. once a block is created, it will not come back. In this way, the best experience for application users will be provided. Because he won’t have to wait more than one block to think the transactions are final.

Compatibility with other blockchains will become much easier.

Some issues with decentralization will be resolved. Aleo moves to PoS mechanism, but the team retains the PoSW mechanism, Aleo network blocks will no longer be based on PoSW.

Normally, only a validator can receive a block reward in a PoS network, but the team has made a change: a portion of the block reward will be given to the verifier, so although Aleo has moved to PoS, the verifier can still be rewarded.

There are two main advantages of the PoS method: efficiency and energy savings. Efficiency means faster transactions, finalization, and better scalability. Finalization is the moment when a transaction is permanently entered into the blockchain.

There is no information about Aleo staking, but it can be assumed that it will be, like all POS blockchains.

How does Aleo solve the privacy dilemma?

At Aleo, zkCloud solves one of the biggest challenges facing blockchains today: the privacy dilemma.

For example, on a public blockchain, program execution takes place in a global “virtual machine” managed by each network node. This means that every node in the network must recalculate every step of a given program. It is safe to say that this is inefficient and also slows down speed and increases costs for the end user. Privacy options are limited because this VM must have access to the relevant information.

zkCloud Aleo overcomes these limitations by decoupling application execution time from blockchain-maintained state. Combined with the power of zero-knowledge proofs, this allows Aleo to provide full programmability and privacy, as well as high transaction throughput compared to the on-chain VM model.

Thanks to zkCloud, individual objects interact with each other through secure transactions.

While programs run on zkCloud with varying degrees of complexity, the only thing that nodes on the Aleo network ever see are the “shadows” cast by shielded transactions running on zkCloud. Because zero-knowledge proofs don’t reveal anything about their content when these nodes (or other third parties) see a secure transaction sent on the chain. In simple terms, you can see that something is happening, but no one knows the details, for example, who and to whom is transferring a certain amount. This can be found out if you intentionally open access.

In this article, we will explore the exciting future of zkML on the Aleo blockchain and its potential to reshape the landscape of data-driven applications.

The history of zkML (Zero-Knowledge Machine Learning) traces back to the early advancements in the fields of cryptography and machine learning. It emerged as a solution to address the privacy concerns associated with traditional machine learning models that required centralized data sharing. The development of zkML gained momentum with the advancements in zero-knowledge proofs and cryptographic techniques, paving the way for a revolutionary approach to combine the power of machine learning with privacy preservation. Today, zkML stands as a promising technology, offering individuals and organizations the ability to leverage machine learning while ensuring data privacy and sovereignty.

Privacy-First Machine Learning: Privacy is at the core of zkML, ensuring that sensitive data remains secure while enabling ML algorithms to extract valuable insights. By leveraging zero-knowledge proofs and cryptographic techniques, zkML allows data owners to retain control over their information while contributing to ML models. Aleo, a cutting-edge blockchain platform, provides the perfect foundation for implementing zkML, offering robust privacy features and scalable infrastructure.

Preserving Data Sovereignty: With zkML on Aleo, individuals and organizations can participate in ML initiatives without compromising their data sovereignty. Traditional ML frameworks often require data to be centralized or shared with third parties, raising concerns about privacy breaches and data misuse. In contrast, zkML enables data owners to maintain complete control over their information, empowering them to collaborate securely and derive value from collective intelligence without sacrificing privacy.

Enhancing Collaboration and Data Access: The zkML approach opens new avenues for collaboration and data access. By allowing participants to share their encrypted data securely, zkML fosters a privacy-preserving environment that encourages data collaboration among diverse stakeholders. This enables the development of ML models on a larger scale, unlocking deeper insights and more accurate predictions while respecting individual privacy rights.

Trust and Transparency: Aleo’s blockchain infrastructure adds an additional layer of trust and transparency to zkML. By leveraging the decentralized nature of the blockchain, zkML models and their corresponding training data can be audited and verified by network participants, ensuring the integrity and fairness of the ML process. This transparency not only builds confidence in the outcomes of zkML models but also fosters a more accountable and ethical approach to data-driven decision-making.

Empowering Data-Driven Innovation: With zkML on Aleo, we are entering a new era of data-driven innovation. Organizations can leverage ML algorithms on sensitive datasets without compromising privacy, encouraging the exploration of novel applications across industries such as healthcare, finance, and cybersecurity. From personalized medicine to secure financial analytics, zkML enables businesses to unlock the true potential of their data while respecting privacy regulations and building user trust.

Looking Ahead: As zkML continues to evolve, Aleo’s commitment to privacy and its powerful blockchain infrastructure position it as a catalyst for the future of machine learning. The combination of zkML’s privacy-preserving capabilities with Aleo’s robustness and scalability opens up vast opportunities for secure, collaborative, and ethical ML applications. With zkML on Aleo, we can pave the way for a future where data-driven innovation thrives while privacy remains intact.

Conclusion: The future of Machine Learning lies in the hands of zkML, a groundbreaking approach that harmonizes the power of ML with privacy preservation. Aleo’s blockchain platform serves as the perfect foundation for implementing zkML, providing the necessary security, transparency, and scalability. Together, zkML and Aleo have the potential to revolutionize how we approach data-driven applications, empowering individuals and organizations to unlock valuable insights while preserving privacy. The era of zkML on Aleo has just begun, and the possibilities are endless.

To know more, join now! Aleo Twitter Aleo Discord Aleo Website

Prepared by Colliseum

Aleo 6/5 Aleo gave a presentation at the Google Startup Campus in Seoul, showcasing Aleo’s cutting-edge technology and practical use cases for ZK.

Aleo 6/6 On June 15th Aleo began implementing the incentives. If you’re interested in participating in the Aleo ecosystem and getting personalized feedback from the Aleo team to keep your app competitive, you can do it now. This aspect of ecological deployment is very important to Aleo. Only a prosperous ecology can create more possibilities. Judging from the feedback information of Discard community, the popularity and activity of Aleo community are far beyond everyone’s imagination. At present, the number of Aleo certified in Discard community has exceeded 10W+.

5 million Aleo points to be determined ↓

Aleo 6/10 Aleo COO shares the potential of zero-knowledge proof in machine learning in the future. From the recent tweets and blogs of Aleo, it can be seen that the current fire of machine learning (such as ChatGPT, Midjourney) Aleo official attention is very high, and a number of blog posts are introduced, describing how zero-knowledge proof can play a role in the field of machine learning to solve the data privacy concerns and resistance to everyone.

Aleo 6/11

The offline meeting on June 11 indicates that the main network may be online in September and October. The next three test incentives do not have prover incentives, only deploy the application and validator incentives. There are 50 validators in the third test phase, and Aleo has pre-selected them from the previously submitted application forms and will announce the list in the near future. When Mainnet goes live, there will be prover incentives and more validators, details will be announced then. The prover algorithm does not change when the main network is online.

Aleo 6/13

Ambassador Program: The sixth Ambassadorial event will begin on July 7.

Aleo Bug bounty program https://www.aleo.org/post/announcing-the-aleo-bug-bounty-program

Deployment incentives https://www.aleo.org/post/announcing-aleo-deploy-incentives

Tools and infrastructure grant programs https://www.aleo.org/post/announcing-the-aleo-tooling-infrastructure-grants-program

Ho Chi Minh City, Vietnam, June 17 https://lu.ma/zkhausvietnam

Aleo’s zkGames: June 18, Oxford, UK https://lu.ma/zkmlbattleshipuk

Core Engineering Updates Merges: snarkVM https://github.com/AleoHQ/snarkVM/pull/1617: Updates to credits.aleo functions https://github.com/AleoHQ/snarkVM/pull/1627: Merge staging into testnet3** https://github.com/AleoHQ/snarkVM/pull/1628: Migrates and updates Ledger to check transactions and blocks with state https://github.com/AleoHQ/snarkVM/pull/1631: Removes terminator from Marlin, SonicPC and KZG10 https://github.com/AleoHQ/snarkVM/pull/1632: Removes PreparedVerifierKey from polycommit https://github.com/AleoHQ/snarkVM/pull/1633: Reduces the size of verifying keys https://github.com/AleoHQ/snarkVM/pull/1634: Removes circuit-specific setup https://github.com/AleoHQ/snarkVM/pull/1635: Remove unused components in Marlin https://github.com/AleoHQ/snarkVM/pull/1636: [Feature] Finalize Fees https://github.com/AleoHQ/snarkVM/pull/1640: Limits the number of write commands, updates finalize root to merklization https://github.com/AleoHQ/snarkVM/pull/1642: [Benchmarks] Finalize Instructions https://github.com/AleoHQ/snarkVM/pull/1643: [Feature] get.or_use https://github.com/AleoHQ/snarkVM/pull/1644: Add restriction on microcredits keyword https://github.com/AleoHQ/snarkVM/pull/1645: [Feature] Per Command Cost https://github.com/AleoHQ/snarkVM/pull/1646: [Fix] Execute and verify nested function calls https://github.com/AleoHQ/snarkVM/pull/1647: Updates hash opcode implementation https://github.com/AleoHQ/snarkVM/pull/1649: Enforces program IDs are lowercase https://github.com/AleoHQ/snarkVM/pull/1651: Refactors the verify methods to their own files snarkOS https://github.com/AleoHQ/snarkOS/pull/2426: Provide error messages when executing programs https://github.com/AleoHQ/snarkOS/pull/2428: Adds helper access to underlying modules https://github.com/AleoHQ/snarkOS/pull/2431: Don't use jemalloc by default for greater compatibility https://github.com/AleoHQ/snarkOS/pull/2434: Increases minimum hardware requirements for running a node leo No substantial updates

In-Progress snarkVM https://github.com/AleoHQ/snarkVM/pull/1648: Ensure there are no fee transitions in executions https://github.com/AleoHQ/snarkVM/pull/1650: Adds timelock capabilities https://github.com/AleoHQ/snarkVM/pull/1652: Adds cost solvers for transactions snarkOS https://github.com/AleoHQ/snarkOS/pull/2427: Updates snarkVM and migrates consensus logic to snarkVM leo https://github.com/AleoHQ/leo/pull/2410: Feat/updater

There are many more merges and in-progress pull requests to check out. We recommend heading to https://github.com/AleoHQ for a full weekly review.

Here are 5 things to do right now on Aleo Testnet3 (with instructions)

1️⃣ Deploy an Application on Aleo

Follow the instructions in this section of our developer documents:https://developer.aleo.org/testnet/getting_started/deploy_execute_demo/

2️⃣ Explore Aleo Projects

Find inspiration on what to build. This repository holds a collection of projects built on the Aleo Testnet: https://github.com/howardwu/awesome-aleo

3️⃣ Prepare your Ambassador Application

The next ambassador round will begin on July 7. Make sure to have your Aleo Resume ready to go. A template can be found by searching “Aleo Resume” in our Discord.

4️⃣ Dive into the Aleo Dev Docs

The Dev Docs are the perfect place to start mastering Leo and building private applications on Aleo. https://developer.aleo.org/getting_started/

5️⃣ Test out the Leo Playground

Eager to start using Leo right now? Try out the Leo Playground for some rapid, real-time coding: https://play.leo-lang.org

A:Yeah, right now, the the reason why strikes are immutable is that, in the underlying layer, basically fundamentally right, you don’t have mutability in the circuit. Now, we can give the illusion of mutability, but that requires some changes to the language, or just mainly changes to the language internals, so that we track which variables are mutated and then reassign them. This is something that’s certainly interesting, for the compiler team to, like, implement, I’d say over the other features that we have planned, this one kind of takes a lower priority. Mainly, you know, like stuff like a raise, like internal like, pass optimizations, those kind of things struck packing, this kind of falls beneath those. But this is certainly interesting. And you can do this by, you know, beefing up your compiler to track these sort of changes. But for now, to answer your question, it is immutable.

2.Q:When are programs with imports going to be deployable ?

A:As far as I know, when I run, like local beacon notes, I’m able to deploy programs with imports in them.

The one copy out is that you have to, like, deploy it so that you have one program that, so, like, you have to deploy it in the inverse order of your dependency graph. So let’s say, of a program A that inputs program B, you have to, deploy program B before deploying program A, if that makes sense.

Q: The program that imported 1st. It’s registry, the program ID does show up on my beacon note. But when I try to add the program that imports that program, what happens is that it just throws an error that has not been added yet. I believe Haruka did answer that. I have to sort of change the start was a code to 1st grab that from the note into, you know, before I use that. So I was wondering if that code needed to pull requests on our side.

A: That’s a great point. I do use my own sort of internal tools to deploy it. I think at the time being, you’ll have to do that. There is some work being done by our SDK team to just, like, make all this stuff super easy. So in this SDK, I’m not sure the extent of the support, but there might be all support already in there that will, you know, look at, you know, what programs that you’re trying to deploy, and then go use them directly. CLI, to, like, just grab that program or add it in, isn’t I don’t believe it’s a two it’s that involved. Or you can check Aleo tools here, or, like ALU decay and see if that CLI functionality there has, um, I support it. https://github.com/AleoHQ/sdk

3.Q: The recent announcement is a bit confusing. > there are no rewards for provers participating in Testnet 3 Phase III (which we are currently in). 1. Does that mean, it is incentivized only for validators but not provers? 2. I thought phase 3 will start once the validators selection has been done. Is there any update on that?

A:I really recommend just asking Aleo community channels for this stuff.

4.Q:Is it possible to deploy a smart contract via another smart contract? If yes, is it possible to calculate the address of the contract that hasn’t been deployed yet?

A:NO. I think deeper thought needs to go into how you make something like this.

5.Q:Is it possible to call a function of an another contract?

A:Yes, it is possible. Let me link you to some code that shows an example of how to do that, so you can find these examples in the LEO repository. https://github.com/AleoHQ/leo/tree/testnet3/examples/battleship The specific example that I’m linking is the battleship example. Then you click on the example subdirectory, and then you click on battleship. If you look through this program, and I’m linking it here in the chat, uh, it shows you how to make external calls to other, uh, to other programs, essentially.

6.Q：Is it possible to pack data and get it’s hash (like abi.encodePacked(…))

A：So right now, the current, up codes and implements like, you know, underlying support we have for like https://developer.aleo.org/leo/operators/#bhp256commit If you look at the LEO section in operators, you can see what we have for, like, B-H-P, peterson all these sorts of, you know, hash operations. What you’ll find is that we, and I think this is what the question is getting at, is that we don’t currently have the ability to take in, like, an arbitrary pack construct and put that in through the hash function. but this is certainly like features that we can work on.

7.Q: Is there a token standard in Aleo (Like ERC-20 on eth)?

A: There is not a token standard just yet. You can find some on github: https://github.com/AleoHQ/ARCs. There’s also another token program that’s used. https://github.com/AleoHQ/snarkVM/blob/testnet3/synthesizer/src/program/resources/credits.aleo you can look at a sample token program that’s used for credits dot Aleo. So this is the credits program, essentially, if I can find it.

8.Q:Is it possible to create a library which would be used in a smart contract?

A: This is certainly possible.What you could do is create a program that essentially, there are two sorts of functions that we have in leo. Essentially, you have transitions, which essentially um are composed of like a state transition. These are things that are externally callable that modify the state of your contract. There’s essentially like your atomic units of execution. Under there’s also, uh in Leo, the concept of functions, which are essentially like helper functions that you can define that just implement logic, that are then invoked by other transitions. And if you like to create, like a library, a contract, you would essentially define one program with a bunch of helper functions, and then define another program that use that imports the 1st program and just makes external codes to that 1st program.

9.Q:Hello, this is about the ambassador question. I see someone ask on Aleo community call. So for the selected ambassador, why not release their resume on discord? That may give direction to someone who are interested. And I think this may be very important for transparent.

A: this is the engineering office hour, so questions not related to engineering is best left to discord

10.Q:I have a question about escrow. So I was working on a program, which, I think most of the things that we have on block chains nowadays, like swaps, anything in defi, usually require a smart contract, or, in this case, a program, to own value in any way. So right now, the only way for us to own value is an Aleo, is that a program holds something in its storage, and it can be access or updated or transitioned through finalize. But the problem here that I’ve faced is that when, eg. we have a token program which issues tokens either a record, either through record or even as just holding a mapping on his storage, if another program wishes to sort of capture that value or sort of hold that value, that’s not really possible, because there are two options. So for records, it could consume it as in just input its input record and not output any other records? And for a storage, it could sort of import that program and cause function to decrease the amount of value that the person is holding in the stores of that program, the token program, but the program itself cannot actually hold value. And this uh makes it sort of impossible to create any sort of traditional like swaps on escrow or liquidity pools, which completely locks the defy a creation of the defi platform. I was thinking, we are, you know, we’re thinking about going maintenance on Aleo, and I was thinking, if anybody has come with something along those lines to solve this problem.

A: I’ll address the 1st. I’ll address programs owning records. So records are fundamentally, like a private construct. So the idea of programs owning records starts to create conceptual issues. So if a program owns a record, right? Who can spend it? How do you make sure that that spend is done privately? So the I’d say, in terms of programs owning records, there’s a bunch of questions that need to be answered, even more like, I’d say, theoretical questions that, we need to answer 1st, such that we’d be able to preserve the privacy properties of the chain now, with programs owning records, interacting with other programs on chain, mapping state, this is certainly something that needs to be improved. And the idea is that one thing that we are working on, or is like on our list, to finish out um to help facilitate this is essentially allowing support, like what we call, like, self dot parent and, it’s essentially what it’s going to be, is an opera that you can use to figure out who um to who invoked the call to another program. So thing on adding this opcode, you then now have programs that can be able to interact with each other and then own,or have or hold in other programs as well.

Q: So that’s only on the context of finalizer transitions.

A: This is only in the context of finalize.

Q: So for example, on my final and program, the other program is token. I can sort of in book that program transition and that program final. When that program final is triggered in that program self, that paren’t is my program?

A: It is your program.

Q: Through this, we could potentially give programs values in, e.g. that token program could say, okay, this uh, swap program holds a value ten, and that program is the only one that could possibly change that state.

A: There’s some a little bit of engineering work that needs to go into this. So just to make sure that, essentially your finalize ordering is done correctly.

11.Q: What’s the use case for running aleo client node?

A: the use cases, I think, is like, essentially like if you’re an application user, right, and you kind of want to run a full node, if you’re one of those people who like, feels that, like, you know, some people like, you know, when they have wallets, they run full nodes on their laptops. Certainly, like, if you’re more on the application side, if you’re actually, like, you know, running it back and for an application, you’d probably be running a prover. usually, like most people are okay with light clients. that being said, uh, we don’t really have, UH, or, you know, light clients is something that we are aim to support in the future. So it might be the case that in the beginning, for the very privacy centric that don’t want to use, um, 3rd party services, they would run the client note on their own.

Q: So is there anything that your client note can do right now or why can’t?

A: The answer on the top of my head is no. I think the provers functionalities of assumes the client notes functionality. But this is also a little bit out of my wheel house.

12.Q：So it’s the cast, a cast of cold, you know, not not that cats not cast into structure or record. Form you 16 to you 32, it doesn’t it is a plan?

A：So, personally, like, this is a, this is something that people have been asking for a lot. I have a couple of tickets and stuff that are and, you know, features that I’m resolving early on this week. the idea is to hopefully get casting between types, at the very least, upcasting, because that should be pretty easy.

In the wake of the forthcoming mainnet debut, Aleo perceives the essentiality of varied, sturdy tooling, and infrastructure to fortify the Aleo network. This new grants scheme is designed to propel their community to step in and aid in fulfilling this requirement by generating these foundational elements for Aleo’s system.🛠️

Boasting a whopping $1M USD in grant funds for the first round, Aleo cordially invites you to apply and commence creating in the third phase of Testnet 3.

Unique Privacy-centric Architecture of Aleo 🛡️ Due to Aleo’s distinctive privacy-centric design, the task of constructing much of this tooling and infrastructure is far from elementary. Hence, this grants program will be leveraged to evaluate superior-quality proposals and allocate financial resources to competent individuals or teams. 🕵️‍♂️

Aleo’s primary objective with the Tooling & Infrastructure Grants Program is to acknowledge and reward community members who engineer groundbreaking solutions on the Aleo network. There’s an incredible enthusiasm for the program’s launch and anticipation for the creativity that’s yet to be unveiled!

Scope of the Program 📚 The program encompasses all forms of tooling & infrastructure, with the exception of block explorers. Aleo encourages you to imagine and innovate without constraints, offering a few examples of useful tooling & infrastructure such as wallets (browser-based, mobile, desktop), Decompilers & Disassemblers, IDE Plugins & Linters, Fuzzers, GitHub Libraries, and WebHooks. 🧰

Aleo has committed to distribute the $1M USD only to grant proposals that are accepted. Every grant proposal will be carefully reviewed by a committee consisting of Aleo core team members who will decide on the allocation of funds.

Process for Submitting and Executing a Grant 📝 Interested in applying? The steps are quite straightforward: form a team or work solo, write a grant proposal using the provided template, and then submit your application.

If your proposal is accepted, the fun really begins. You’ll engage in a constructive conversation with a program committee member, adjust your proposal according to their feedback, sign the official grant letter, and get started on your project!

Aleo provides a systematic procedure to keep everything transparent and on track. As you accomplish each milestone, you’ll receive part of your total funding. Additionally, you’ll have a direct line of communication with the Aleo team for any queries while working on your grant.

Selection Process for the Grant Application 🏆 Applications are chosen based on the quality of the team, uniqueness of the project, and its potential impact on the Aleo ecosystem. Votes from the committee members decide the selection, with each member’s vote carrying equal weight.

The selection criteria are comprehensive, considering user experience, architecture, functionality, impact, and novelty. Aleo’s committee will continuously review applications until the funding is exhausted.

Wrapping Up 🎁 Aleo’s success is rooted in the innovation and skill set of their community. The Aleo Tooling & Infrastructure Grants Program underlines Aleo’s commitment to encouraging growth and rewarding developers contributing to the creation of a more diverse ecosystem.

If you’ve got a concept for tooling & infrastructure that could aid the network, this is a golden opportunity to build and receive funding.

Legal Requirements ⚖️ For information about requirements and eligibility for receiving funding through the Aleo Tooling & Infrastructure Grants Program, please read Aleo’s terms of service.

Art for Aleo 📢Official Links: Discord | Website | Twitter | GitHub

Community Announcements Community Call WEDNESDAY at 11:00 am ET w/ Anthony DiPrinzio Are you interested in hosting monthly community meetups? Fill out the form below! https://forms.gle/f6Ufs1XJVMvo2gp59 Ambassador program: The application form for Ambassador Round 5 is closed We have contacted our KYC provider to resolve an issue for selected ambassadors Aleo Deploy Incentives https://www.aleo.org/post/announcing-aleo-deploy-incentives Have questions? Please ask them ⁠🔬┃testnet3-support Tooling & Infrastructure Grants Program https://www.aleo.org/post/announcing-the-aleo-tooling-infrastructure-grants-program Nominate Alex Pruden to speak at #Mainnet2023 because AI needs accountability https://airtable.com/shrjUn6pObbnUtWtV The Privacy Playlist Music competition ⁠zkMusic Contest

Core Engineering Updates Merges: snarkVM https://github.com/AleoHQ/snarkVM/pull/1576: commit_to_group, hash_many (placeholder), hash_to_group, and hash_to_scalar opcodes https://github.com/AleoHQ/snarkVM/pull/1577: Fix atomic checkpointing https://github.com/AleoHQ/snarkVM/pull/1585: Fix transaction benches to include fees https://github.com/AleoHQ/snarkVM/pull/1589: Adds counter for num_nonzeros https://github.com/AleoHQ/snarkVM/pull/1592: Fix atomic checkpointing and rewinds https://github.com/AleoHQ/snarkVM/pull/1594: [Feature] Support group::GEN as an operand https://github.com/AleoHQ/snarkVM/pull/1598: Switches out VecDeque for Vec in checkpointing https://github.com/AleoHQ/snarkVM/pull/1600: remove required cli flags, support multiple arguments, update readme https://github.com/AleoHQ/snarkVM/pull/1601: Add a test case for cli argument parsing https://github.com/AleoHQ/snarkVM/pull/1608: Reduce sizes in merkle_tree benchmarks https://github.com/AleoHQ/snarkVM/pull/1609: Adds a prelude on the synthesizer modules snarkOS https://github.com/AleoHQ/snarkOS/pull/2401: Update license file, file headers, and badges https://github.com/AleoHQ/snarkOS/pull/2406: Revert "logs: deduplicate peer IP" https://github.com/AleoHQ/snarkOS/pull/2408: Update the MSRV https://github.com/AleoHQ/snarkOS/pull/2409: Merge the staging branch leo https://github.com/AleoHQ/leo/pull/2399: Bump/snarkvm v0.11.4

In-Progress snarkVM https://github.com/AleoHQ/snarkVM/pull/1584: Prevent addition overflow https://github.com/AleoHQ/snarkVM/pull/1586: [Feature] Permutation Check https://github.com/AleoHQ/snarkVM/pull/1587: [Feature] Permutation Assignment https://github.com/AleoHQ/snarkVM/pull/1588: A test to display local storage breakdown https://github.com/AleoHQ/snarkVM/pull/1590: Adds sanity check on function sizes https://github.com/AleoHQ/snarkVM/pull/1593: Unifies proving of Transaction::execute into two proofs https://github.com/AleoHQ/snarkVM/pull/1599: [nit] remove impossible SynthesisError::AssignmentMissing https://github.com/AleoHQ/snarkVM/pull/1606: Speed up VM::from via parallelism https://github.com/AleoHQ/snarkVM/pull/1607: Construct finalize_root from Transactions snarkOS https://github.com/AleoHQ/snarkOS/pull/2410: Update clap to 4.3 https://github.com/AleoHQ/snarkOS/pull/2413: Update snarkVM leo https://github.com/AleoHQ/leo/pull/2400: bump snarkvm v0.11.5

There are many more merges and in-progress pull requests to check out. We recommend heading to https://github.com/AleoHQ for a full weekly review.

Core Engineering Updates Merges: snarkVM https://github.com/AleoHQ/snarkVM/pull/1543: Refactors coinbase and snark in synthesizer https://github.com/AleoHQ/snarkVM/pull/1544: Moves Deployment, Execution, and Fee to the block folder https://github.com/AleoHQ/snarkVM/pull/1545: Moves Transaction executors to VM https://github.com/AleoHQ/snarkVM/pull/1546: Migrates finalize operation to the block folder https://github.com/AleoHQ/snarkVM/pull/1547: Introduce complete abstractions for Stack and Registers snarkOS https://github.com/AleoHQ/snarkOS/pull/2391: Reduce maximum handshake message size https://github.com/AleoHQ/snarkOS/pull/2392: Use blocking tasks for some heavy inbound operations https://github.com/AleoHQ/snarkOS/pull/2393: Feature-gate jemalloc https://github.com/AleoHQ/snarkOS/pull/2395: Jemalloc no default features https://github.com/AleoHQ/snarkOS/pull/2396: Deduplicate peer IP in logs https://github.com/AleoHQ/snarkOS/pull/2397: Enforce a 1s raw TCP connection timeout leo No substantial updates

In-Progress snarkVM https://github.com/AleoHQ/snarkVM/pull/1560: Document the DataMap map IDs https://github.com/AleoHQ/snarkVM/pull/1565: [Refactor] Refactors the synthesizer test framework https://github.com/AleoHQ/snarkVM/pull/1566: [Test] Test framework for program execution https://github.com/AleoHQ/snarkVM/pull/1568: update license from GPL to Apache 2.0 to promote contribution and broader use of this software snarkOS https://github.com/AleoHQ/snarkOS/pull/2399: change license from GPL to Apache 2.0 leo No substantial updates

There are many more merges and in-progress pull requests to check out. We recommend heading to https://github.com/AleoHQ for a full weekly review.

• Community Call WEDNESDAY at 11:00 am ET w/ Aleo CEO Alex Pruden

• Deploy Office Hours, May 15 at 2 pm ET

  • https://discord.com/events/700454073459015690/1105281821794652160

• Are you interested in hosting monthly community meetups? Fill out the form below!

  • https://forms.gle/f6Ufs1XJVMvo2gp59

• Ambassador program:

  • The application form for Ambassador Round 5 is closed

  • All selected applicants will receive a link to undergo the mandatory KYC process

• In light of the new announcement about deploying applications, we want to encourage participants to form teams to submit the best application

  • We’re hosting a virtual teammate matching on May 10th from 2 pm

  • If you’d like to participate in the virtual teammate matching, you must complete this form: https://forms.gle/832gKPUm6TdQBJCb6

• Pioneer the Future of Private Machine Learning with Aleo’s zkML Initiative:

  • Season One of Aleo’s zkML initiative launches May 12, and a total of 280,000 Aleo credits will be distributed

  • https://www.aleo.org/post/pioneer-the-future-of-private-machine-learning-with-aleos-zkml-initiative

Core Engineering Updates

• Merges:

  • snarkVM

    • https://github.com/AleoHQ/snarkVM/pull/1482: Update feat/client to v0.10.2

  • snarkOS

    • https://github.com/AleoHQ/snarkVM/pull/1494: Add test for multiple deployments in Speculate

    • https://github.com/AleoHQ/snarkVM/pull/1495: Ports rocksdb map impl into synthesizer

    • https://github.com/AleoHQ/snarkVM/pull/1496: Adds the db impls of each storage type

    • https://github.com/AleoHQ/snarkVM/pull/1497: Updates method names in map trait

    • https://github.com/AleoHQ/snarkVM/pull/1498: Refactor MemoryMap impls into memory folder

    • https://github.com/AleoHQ/snarkVM/pull/1501: Use BTreeMap in MerkleTree::update_many to enforce uniqueness

    • https://github.com/AleoHQ/snarkVM/pull/1503: [Feature] Increase limits for Finalize

    • https://github.com/AleoHQ/snarkVM/pull/1507: Atomic write checkpoints

    • https://github.com/AleoHQ/snarkVM/pull/1508: Switch from speculate to finalize operations

    • https://github.com/AleoHQ/snarkVM/pull/1512: Adds snarkvm-ledger back in

    • https://github.com/AleoHQ/snarkVM/pull/1513: Update version types to be consistent - u8

    • https://github.com/AleoHQ/snarkVM/pull/1514: Adds the deployment fee multiplier

    • https://github.com/AleoHQ/snarkVM/pull/1516: Adds Transaction::Fee type for rejected transactions

  • leo

    • No substantial updates

• In-Progress

  • snarkVM

    • https://github.com/AleoHQ/snarkVM/pull/1499: Catch usize conversion and Err more consistently

    • https://github.com/AleoHQ/snarkVM/pull/1502: [Feature] Add open_testing method to the storage traits

    • https://github.com/AleoHQ/snarkVM/pull/1505: [Nit] Merkle Tree Update

    • https://github.com/AleoHQ/snarkVM/pull/1510: Multi circuit proof integration

    • https://github.com/AleoHQ/snarkVM/pull/1511: [Fix] Reorder evaluation of finalize transitions

    • https://github.com/AleoHQ/snarkVM/pull/1515: A benchmarking framework for user-defined workloads

    • https://github.com/AleoHQ/snarkVM/pull/1517: Abstracts speculate and finalize with atomic_finalize

    • https://github.com/AleoHQ/snarkVM/pull/1518: Adds ConfirmedTransaction for accepted and rejected transactions

  • snarkOS

    • https://github.com/AleoHQ/snarkOS/pull/2373: Update block proposal to use finalize

    • https://github.com/AleoHQ/snarkOS/pull/2374: Filter bogon addresses from the peer lists

  • leo

    • No substantial updates

There are many more merges and in-progress pull requests to check out. We recommend heading to https://github.com/AleoHQ for a full weekly review.

Need help to find the best teammates?

We’re hosting a virtual teammate matching on May 10th from 2 pm - 5 pm GMT. During the event, you’ll have the opportunity to give a live 30-sec pitch that includes:

• Your name + professional background

• What kind of teammate you’re looking for

• What you’d like to work on

• How to get in touch

For example: “Hey everyone! My name is Annee, and I’m an experienced entrepreneur and marketer. My idea is SoftServe, an L&D platform for dynamic soft skills index. I’m looking for a developer and designer to help me bring my idea for SoftServe to life. My TG is .” If you’d like to participate in the virtual teammate matching, you must complete this form: https://forms.gle/832gKPUm6TdQBJCb6

— How Aleo can help protect data privacy in decentralized applications (dApps). — How Aleo will solve data privacy and information protection issues on the blockchain. — How Aleo can be used to develop secure and private dApps in medicine, finance and other industries where data privacy is a critical aspect. — How Aleo provides privacy and confidentiality at the blockchain protocol level, allowing users to control their data.

— How Aleo increases the amount of data stored on the blockchain by using data blending and other privacy protection technologies.

Also, these themes can be used to create different types of content, such as:

Articles and Blogs — Articles can be written about how Aleo wants to protect privacy data on the blockchain, and how developers can use the protocol to build secure and private applications.

• Videos — Create video tutorials and tutorials on how users can use Aleo to keep their data private and build secure apps.

• Presentations — Presentations can be created that demonstrate how Aleo provides privacy and data protection on the blockchain and how this can be important for different sectors such as medicine, finance and others.

• Infographics — Infographics can be created that explain how Aleo works and how it wants to protect sensitive data on the blockchain.

• Webinars and Podcasts — Webinars and podcasts are available where experts can learn how Aleo works and how it can be used to build secure and private applications.

• In addition, you can create content that focuses on success stories and projects that Aleo sets out to solve privacy and data privacy issues. Such content may take the form of interviews with app developers who choose Aleo and with their users who talk about how Aleo has helped them protect their data.

• In addition, contests and promotions can be held to attract new users to Aleo and draw attention to the protocol. For example, you could run a contest for the best application that uses Aleo to ensure privacy and data privacy, or act on attractive terms for developers who choose to use Aleo for their applications. — All of these ideas can help attract attention to Aleo, increase awareness of the protocol and its capabilities, and attract new users and developers to the Aleo ecosystem.

1. Ambassadors application opens on May 5th. The link to the form will be posted in ⁠📣┃announcements at noon ET! There will also be Twitter Space with Viv, and Santiago at 11 am ET that day!

2. Aleo Deploy Incentives are finally here: https://www.aleo.org/post/announcing-aleo-deploy-incentives (thanks to engineering team and especially Anthony!)

Boloney Presentation

1.Kryha is a Web3.0 studio, who have participated in the Aleo Grants program.

2.They’re working to accelerate adoption of ZK in games. In the future the team will even present ZK toolkit for game developers!

3.Boloney is a dice game with poker mechanics (kinda based on Liar’s Dice): https://boloney.io/ However, Boloney also is a Sandbox that can provide tools to introduce ZK into a dice game.

4.In the game there are used:

• Commit & reveal scheme

• Verifiable random functions

• Hash chains

5. At first, the game will only be available for ambassadors (from May 3rd to June 5th)! Boloney account will DM ambassadors their credentials (make sure to not lose it!) Ambassadors are welcome to try the game and leave their feedback in ⁠无访问权限 channel!

6.Within the game you can choose to play Quick Game (with 4 other people), or you can configure the game as you like. The most interesting mechanic is power-ups, you can choose the chance of getting each of them!

7.On the game site you can find the rules, little chat with players (during the game), and also the Contact page: https://boloney.io/contact

8.Boloney’s code is open-sourced, so you’re welcome to hack the code and give your feedback on GitHub as well: https://github.com/Kryha/boloney

9.Right now, you have to provide your private and public keys to play, but the next step on the roadmap is to make it possible to connect to Boloney via Leo Wallet without having to share the keys!

10.During the game all the computation is made off-chain. And then, after the round these computations get verified on-chain (this is the only on-chain activity).

11.No mobile version in the roadmap yet.

12.The team decided to settle to dice game instead of a card game (like poker), because implementing a decentralized card deck is very hard. It would require encrypting and decrypting cards each time you shuffle the deck. There are some solutions to do this, but they’re not scalable enough.

Thanks Kryha team for their fantastic work!

In-Progress   - snarkVM     - https://github.com/AleoHQ/snarkVM/pull/1481: [Test] Check that the number of mappings does not exceed maximum     - https://github.com/AleoHQ/snarkVM/pull/1482: Update feat/client to v0.10.2     - https://github.com/AleoHQ/snarkVM/pull/1487: Wasm parameter downloads snarkOS     - https://github.com/AleoHQ/snarkOS/pull/2337: Switch from warp to axum     - https://github.com/AleoHQ/snarkOS/pull/2349: Use generic instead of hard coded MapID for open_map     - https://github.com/AleoHQ/snarkOS/pull/2352: Bump snarkVM to v0.10.3   - leo     - No substantial updates

There are many more merges and in-progress pull requests to check out.  We recommend heading to https://github.com/AleoHQ for a full weekly review.

With less than two weeks to go before the start of the fifth round, would-be Aleo ambassadors don’t let up. Here are some tips to use the remaining time to make a good ambassador application:

Develop an ambassador application plan ‍ When you decide to try out for the Aleo Ambassador Program, develop actions for applying for the Ambassador program.

-Make relevant content plan in advance and check whether it is reasonable. -Allow time to implement the application plan and check for missed items.

• Complete within the specified time, in case of sudden emergency. ‍

Improve the quality of works Aleo has strict requirements for ambassadors. They value the quality of ambassadors very much. If you don’t meet these requirements, then your chances of becoming an ambassador are greatly diminished.

Please check your work carefully, the following aspects need to pay attention to:

• All information in the content is true;

• There are no typos in the text;

• The design adopts the style of Aleo brand. You can find it on this page;

• No more than two theme labels are indicated in the work.

Follow the official announcement Previous rounds of Aleo Ambassador programs are as follows:

• Open the application form;

• The official collects a certain number of applications to close the form (previously it was 1500); -Team check application;

• Publish the results.

The application time for ambassador is set on May 5th. Please pay attention to the official announcement to avoid missing the time or update of the application.

Do something important! If you have completed all of your planned tasks, or have time to complete them in the remaining time without any problems, then I recommend doing other important tasks.

Don’t go for quantity, try to do something more quality. If the piece is big and cool, even better, then you have a chance of being noticed, which increases your chances of being chosen as an ambassador.

1. Aleo points hold absolutely NO inherent value. Aleo Points are an added element of fun for the Ambassador Program but they are useless. Anything you read otherwise is incorrect.

2. All ambassadors will have to pass KYC as THEMSELVES. This is not a “one and done” situation. If you passed once, we will continue to KYC our ambassadors throughout the program, and in different ways to ensure that ambassadors really are who they say they are on KYC. It makes no sense to try to get around KYC because…

1a) you will get caught and immediately booted

2a) we will continue to do KYC checks that get increasingly more complicated

If you’re from a sanctioned territory (Cuba, Iran, North Korea, Russia, Syria, Crimea, Donetsk, and Luhansk Regions of Ukraine), please do not apply. You will not pass KYC.

1.The next ambassador requirement happens on May 5th. There will be some updates in the program, so the focus will not be on points only! 👀

2.Team is going to Consensus, so if there are any US-based ambassadors who'd like to attend, please DM Viv, or Nodari!

3.There's going to be a huge focus on IRL meetups and their consistency, Aleo team has also hired an event manager, anneep!

4.A great example of this IRL meetups is the one that DimaS organized in Kyiv! (and there's going to be a new one in Lviv soon!🚀 )

5.The testnet should be up and running today! There was a delay because of some issues with the Twitter API.

Demo from ProofCat:

The team is working on the ability to prove via web, so developers will be able to deploy/execute/run programs in browser!

There are 2 main focuses:

1. Making proving directly in browser possible.

2. Create a dev server (so you'll be able to deploy locally, or on testnet network, but use your browser as a front-end). This server is almost ready and will be published soon! And ProofCat presented us demo on it!

1.With the development server, you can make everything via Aleo SDK!

2.Note, that it's better to test your apps locally before deploying them on the network.

3.The server is created so you'll be able to talk with the network using HTTP requests and using language of your choice.

4.How the deployment goes:

1. Spin up your local network.

2. When you use leo build the program compiles down to Aleo Instructions. You should copy those and paste this bytecode into Aleo SDK, specify fee, and then deploy in your web! Just like this, the dev server does all the execution for you.

   3. Web page will show that deployment went successfully!

5.Note, that you can't deploy the same program more than once.

6.You can execute the program via Aleo SDK by pasting program ID there, specifying inputs, functions and private key.

7.This server shares some info, so please do not use it when making public API ❗

8.You can also send tokens via Aleo SDK.

9.If you'd like to see how Aleo is already working, definitely check out Demox Labs' Leo Wallet: https://www.leo.app/