The proposal wants to create sub handles from “Handle” domains. Handle is a service where the user can buy wallet domains and so change their wallet address for the wallet domain. Thus it allows you the send and get cryptocurrencies easier. The technicality is clearly described in the proposal and an demand from bigger companies in the Cardano ecosystem is reasonable. Therefore this proposal improves an already existing usecase which enriches the ecosystem. Thus it clearly matches the challenge strongly.

ADA Handle provides a custom and human-readable address through a standardized NFT, and in this proposal, the team wants to create a subhandle feature that enables user to manage/track different wallets that are connected to a root handle. The proposer provides clear description about the current problem, use cases from organizations to individuals, and details about the product itself (including subhandle formats). The proposal provides an improvement to ADA handle feature, which helps the community to provide more flexibility and transparency in the future, that supports the Cardano ecosystem growth.

Considering that many projects do need a sub-handle to the root $handle that they own for the project, this proposal clearly and effectively addresses the issue.

I am particularly happy to see that they have proposed to use both the NFT Metadata Standard (CIP-25), an NFT on the chain, as well as virtual NFT's using the IPFS-hosted JSON-formatted datasets.

This dual way of minting enables two options for projects, ISPOS, SPO's, and the like to come up with a solution that best fits their needs.

This is a very well laid out proposal.

As far as I know, the ADAHandle project is understood as a standardized NFT that developers and users can use to associate an address with a custom and human-readable address. The issue raised by the author here is that organizations need to purchase multiple native ADA processors unrelated to different billing addresses, and there is no guarantee that all the related Handles will be available. That is, they want to release multiple subHandles associated with their root Handles to specify a variety of tasks, but without the need to use dashes, underscores, or full stops. As a workaround for this problem, the proponent came up with a solution that is "SubHandles". This solution identifies most of the problems of the challenge. Because it improves and integrates new features for the ADAHandles platform on Cardano. This will attract more organizations and users; provide value to the ADA community and the broader ecosystem. The proponent described his solution in great detail and reasoned well. By providing specific examples and detailed analysis of 2 subHandles formats, which are NFT-based subHandles and Virtual subHandles. Besides, the proponent also mentioned the main risks that may be encountered when implementing this project. These risks are all related to NFT-based subHandles and Virtual subHandles. Each format poses different risks, but the team has identified solutions to reduce those risks.

This proposal was an absolute joy to read. You broke down an extremely complicated topic and made it completely approachable to someone that is not in the development side of the ecosystem. Having sub handles could completely change the way businesses issue email addresses! The utilization purposes for DAO's and other more centralized businesses is astounding! This proposal allows for the expansion on an already extremely successful part of the ecosystem, and your team has a proven track record of delivering brand new technology that works flawlessly. Funding in catalyst should be reserved specifically for projects building like ADA handle. It gives the ability to a company that already has proven itself to further fund technology that could vastly improve the use cases of blockchain, and specifically Cardano as an ecosystem. I cannot think of a better example of a proposal that I have seen in this entire fund.

ADA Handle is a project that provides human-readable address in Cardano. This proposal tackle the problem of creating the sub-handle standard. The proposed solution is to create a subHandle that will give people the ability to issue another name under their root handle. The proposed solution is explained in detail (using CIP-25 standard and IPFS for each solution). This project is aligned with the challenge settings, which is to improve utility in ADA Handle, which then would increase user adoption and future growth within Cardano ecosystem.

ADA Handle are proposing to introduce a subHandle change to the ADA handle standard that will mean that existing handle holders can take their handle as a root address and then create child handles for that root handle which are called subHandles. A number of examples are provided for how sub handles could be used such as from families, SPOs and organisations. The solution described outlines the usage of both virtual handles that are owned and maintained by the root handle as well as NFT based sub handles that can be issued by owners of the root handle. The main risks for sub handles that are covered is the issuing of an NFT sub handle and how this could result in issues where the root or sub handle holders change, the solution for this is to maintain a list of which sub handles are verified so that the NFT sub handles issued don't hold power in perpetuity. The demand for this proposal is well articulated and backed from existing users of the ADA handle standard which highlights that the execution of this proposal could create high impact within the community soon after its implementation. Due to this it looks very likely that this proposal could produce a high impact for the community in an solution that a growing amount of the community are using.

Ada Handle has provided a clear and concise description of the issue in their problem statement - a solution to organize different payment addresses and guarantee consistency across handles. It extends the set of features of Ada Handles, which is on the path to becoming the most adopted project within Cardano and the naming standard across the network. The proposal will therefore have a positive impact on the Cardano ecosystem as a whole by allowing a wider range and more imaginative uses for their existing solution. The proposal clearly articulates how it will add value to the handles, has a scaling plan, and propose innovative solutions to the problem (NFT-based and Virtual sub handles). This update will bring great value to the project, and allow it to compete on the crypto scene with the more known competitors by delivering a unique set of features. This proposal addresses the challenge effectively, thus I'll rate this proposal a 5/5.

The team has describes many metrics to measure the process of the development. They will make a third party audit to check that the code works. There are clear goals to check whether the application works. Overall it seems easily auditable.

The proposer provides their roadmap with phases, each contains its own tasks and goals. The team has tools and strategies to track their key metrics, using internal ERP software and holding daily meetings to track progress. The team included their website and GitHub page to provide regular updates. The team also provides their success indicator, where community adopts the subhandle standard, and clients can purchase multiple handles and subhandles with flawless process.

The proposer has stated the following:

• Our internal ERP software (ERPNext) with its Project Management framework that will allow us to monitor phase workflows.

• Daily standup meetings with the entire team to track individual progress and assist with specific tasks.

• Weekly & monthly reports to demonstrate what the team accomplished and determine the next tasks.

• External third-party audit that will check our work throughout the entire process.

With all of these in place, it should be relatively easy to audit the progress of the project.

However, I would have liked to have seen the proposer tell us if the daily standup meetings would be recorded in some form. To simply list it may mean an individual would need to listen in all the call or stand or sit in the meeting, or may mean that it will be recorded and easily played back for auditability purposes.

With that said, this proposal is very well laid out, the proposer have already successfully developed and deployed ADA Handle, have laid out that they will deploy a third party audit throughout the entire process, have laid out what completion will look like and have made auditability very simple for this proposal.

Auditing is a very important part of every project. With this proposal, the team prepared tools, tactics and strategies to track key metrics. However, I am of the opinion that the 3rd party audit really makes sense given the decentralization of the project? Is this auditor reputable? I think that the project can incorporate thanks to the community itself for auditing, it will be transparent and increase its decentralization. The latest information, work progress, weekly & monthly reports of the project will be continuously updated on the project's communication channels such as Twitter, Github, Disco, and Youtube… for the community to easily monitor and evaluate. If possible, the team should organize live streams to share about the project to increase interaction with the community. At the same time, the community will have feedback and make contributions to make the project better. The success of the project is very clearly defined. That's: all DApps, wallets and communities adopting the new Sub-Standard; Cast and release SubHandles, using them for validation, organization, and transparency; Mint portals and smart contracts work exactly as designed without any hitches; The new checkout cart works perfectly, allowing multiple Handles and subHandles to be purchased.

Your team has literally covered every base that I could think to rate in a proposal. The group you have working on this project are absolute gems and should be given continued funding to see this project all the way through. I love how transparent you guys have been as a community. You are always willing to take suggestions and ideas from the community and do your best to implement them in the safest, most effective way possible. Success for this project would look like the majority of projects adopting the handle standard, and the onboarding of traditional world businesses as a whole. Every day I discover a new DAPP that has integrated the handle standard into its code. Your team has made it an easy task to implement the features for the entire community to use, and a prime example of what every project should be on Cardano!

ADA Handle already proven themself to be transparent and always informing the community. This proposal includes link for their project website and GitHub repository. The team’s Twitter profile also take a role in transparency. KPI, metrics, and roadmap is also explained with goals and target. All in all, transparent project and would be straightforward to audit the progress of this project.

The proposal team have provided their Github profile in which you can see which repositories they have open sourced. In terms of tracking progress the team have listed their internal approach to how they handle monitoring progress but also have mentioned weekly and monthly reports and the external third party audit which is something the community will be able to audit themselves. Success for the proposal has details for the effective implementation of the subHandle standard. The clarity of the proposal is very high and very easy to follow and understand the exact intentions of the proposal and the reasons it is being proposed. In terms of improvement it would have been good to know more exacts on what will be open source from what is being developed and how that may benefit the community. This is both good on an auditing perspective but also as a community educational resource that speeds up other development efforts in the ecosystem.

The proposal provides a clear and detailled roadmap with milestones and a time horizon for achievement. The metrics that define success are presented and make sense - an app that works without issue, the standard is widely adopted by the community and actively used for authentication, organization and transparency. The team has explained how they will track the progress of the development of their project - using an internal ERP software, daily meetups, monthly and weekly reports and an external third-party audit.

The information provided is sufficient to audit the progress and the success of the proposal, and this is why I give auditability a 5/5 rating.