Professional profile

• A professional should be able to have an anonymous professional profile that they can use to build up a reputation online. In the future that anonymous profile could create connections, transact with people and organisations but remain anonymous. An example of who may want to do this is a hacker who wants to conceal their identity whilst also offering a service. This could have regulation implications so would require more research and thought.
• A professional should be able to share their data where and how they want and also receive any benefits for that data if they are offered. If a professional wants to optimise for maximum value for providing their data to protocols and services they should be able to so.
• Determine which data people are comfortable sharing with protocols and DApps and which data should be kept private.

Treasury funding and finance tasks

• Collaborate with community advisors on recommended approach for storing and distributing project funds to project collaborators for projects where funding is successful.
• Consider any tax regulations that may impact approach of distributing funds. Collaborate to check sending funds and a policy of self reliance on declaring income is sufficient.
• Discuss with fund advisors how a project could move its previous fund data to the next one and provide the updates from the previous fund. A rolling funding approach would be an ideal setup to request smaller but more regular funding as progress is shown. This also allows people to be onboarded onto the project after any fund cycle. The target here is lower the upfront cost commitment to fund a project and to minimise the time a project team has to spend repeatedly trying to add data to raise funding in each treasury fund.

Community tasks

• Keep tasks specific and add updates to social channels when tasks are completed for transparency. For example, all task progress could be posted in a Discord chat channel and larger milestones could be posted on Twitter.