0x1ee1…b759

All memos sent from and to 0x1ee1…b759.

0x1ee13d3b…b759sent to0xdeae2abb…14eb2024-02-28·#19,327,042·0x27828bf7…ca6cc4

Annual DAO Funding RequestAs per the tomi Whitepaper, the DAO requests its annual development fund. This year the DAO has performed the following:  <ul> <li></li> </ul>  Tomi Army funding  <ul> <li></li> </ul>  Execution and delivery of SSI POC and specifications https://docs.google.com/document/d/1pKyaFHshtT8q9WybVMvaqBNwfqAOTcZc5YP7pR1uPdw/edit#heading=h.o2ezqmxbmjmv  <ul> <li>Staking for the TOMI tokens </li> <li>Separation of DOP from TOMI and partnership agreements </li> <li> Funding for specifications document, carrying out AMAs and expert consultations, participation as a sponsor in MetaFest, DevConnect participation, and writing of a DAO specifications document https://docs.google.com/document/d/1e-oqa1whRm8S0HjZ622woTdXrTFaZx95IMk_axK7RmI/edit?tab=t.0#heading=h.bwrh17agavzs </li> </ul> Therefore we request our annual funding to carry on of $10,000,000 in TOMI tokens.

0x1ee13d3b…b759sent to0xdeae2abb…14eb2023-08-06·#17,855,180·0x62b04f83…74ad6f

Tomi DAO Governance specifications<h1>Overview</h1> tomi is planning the upgrade of the DAO to manage the tomiNet, which will be released on May 15, 2024. tomi is creating an alternative network to the world wide web infrastructure with several important unique features, most importantly the governing body through a DAO and privacy storage network that makes it impossible for the network to be captured, censored or subjected to pressure from large entities. For a copy with better formatting: https://docs.google.com/document/d/1OpYksmPAXGKSyvUmrQIzcaEdr3hQLif8v85_oKsUPwc/edit <h1>Outcomes</h1> <ul> <li>Create overall DAO specifications for the tomiDAO within 3-6 months</li> <li>Launch tDAO version 1.5 in May 2024, including:</li> <ul> <li>Adequate functionality for management of the tomiDNS</li> <li>Integration with tomiPay / tomiSSI wallet for participation in DAOs</li> <li>Improved treasury management</li> <li>Basic metagovernance functionality</li> </ul> <li>Bring in at least 50 new active members of the DAO for participation in the various functions of decision-making</li> </ul> The funding for the proposal has both development and community management (marketing) costs associated with the creation of the DAO. Without qualified people to populate the DAO, the governance system cannot be executed. Furthermore, bringing in different people for the governance of the DAO will result in more thorough brainstorming and better overall specifications of the DAO. <h1>Overall strategy</h1> <ul> <li>Initial discovery stage will create a basic scope for the full DAO functionality with brainstorming of initial ideas of governance for each component.</li> <li>Each component will go through a design sprint (online or in person) which will result in a specification including user journeys and basic wireframes.</li> <li>Following the design sprint, DAO representative(s) and a development team will be assigned to develop the components according to the specifications. </li> </ul> Each phase of design will include: <ul> <li>4-6 expert discussions online, 90-120 minutes each</li> <li>2-4 AMAs with community, open discussions</li> <li>1-2 day in-person design intensive, located in a place where local experts are invited (eliminates travel fees except for hosts).</li> <ul> <li>Suggested locations: Tel Aviv, London, Barcelona, Berlin, Amsterdam. </li> <li>Possible alternative: side event prior to or following an industry event.</li> </ul> </ul> <h1>Funding</h1> The proposal requires multiple companies and individuals who will need to be paid out in crypto and/or fiat currencies. To reduce administration of payments, the DAO will approve a total funding budget of $TOMI 30,000 for the first phases of the budget, managed by a multisig wallet that allows the tomi team financial department (CFO) to create all funding requests, and the approval of DAO Owl or Camel will be required to approve the payout. While this creates a level of centralization, the wallet will be fully transparent and all community members can see the use of initial funding before approving additional funds to the wallet. <ul> <li>Initial budget: $TOMI 30,000</li> <li>Multisig with 2 / 3 signatures required:</li> <ul> <li>Dan (tomi CFO)</li> <li>Camel (tomi CTO)</li> <li>Owl (tomi DAO Official)</li> </ul> <li>For actual development, as each specification is defined, the development team (or multiple contenders) for that phase will submit a budget. </li> </ul> It is expected that additional funds will be needed for the execution of this proposal. After accomplishment of the initial milestones and the opportunity of the community to audit results, additional funding will be requested for the following milestones. This may be through the same mechanism, or through the nomination of DAO Stewards, if that is ready at the time. <h1>Timeline</h1> <h2>August 2023</h2> Initial discovery stage: Creation of the initial framework of the DAO. <ul> <li>Discovery phase:</li> <li style="margin-left:36pt;">Initial guidelines set out for the parts of the DAO with basic brainstorming of each section of the DAO: </li> <li>Specification phase:</li> <li style="margin-left:36pt;">DAO Design track at Metafest and sponsorship to create the basic DAO overview</li> <li style="margin-left:36pt;">2 experts at Metafest to represent tomi </li> <li style="margin-left:36pt;">Part time community manager/marketing support </li> </ul> <h2>Ongoing: Community development</h2> <ul> <li>Recruiting people to the tomi Discord for feedback and discussion</li> <li>Using content and message feedback keep DAO conversations going</li> <li>Hosting AMAs among the DAO thought leaders to get feedback</li> <li>Keeping the tomi community in the loop and working with the tomi marketing team to help promote work on different channels</li> </ul> <h2>Designing of specifications</h2> The specifications of the DAO will have two phases: one for the DNS DAO and the other for the meta-governance of the tomiDAO. Each phase of design will include: <ul> <li>4-6 expert discussions online, 90-120 minutes each</li> <li>2-4 AMAs with community, open discussions</li> <li>1-2 day in-person design intensive, located in a place where local experts are invited (eliminates travel fees except for hosts).</li> <ul> <li>Suggested locations: Tel Aviv, London, Barcelona, Berlin. </li> <li>Possible alternatives, side event prior to or after an industry event.</li> </ul> <li>Write-up of design specifications, including wireframes by UI designers and user journeys</li> <li>Ongoing community management</li> </ul> <h2>September-October 2023: DNS DAO design</h2> Each phase of design will include: <ul> <li>4-6 expert discussions online, 90-120 minutes each</li> <li>2-4 AMAs with community, open discussions</li> <li>1-2 day in-person design intensive, located in a place where local experts are invited (eliminates travel fees except for hosts).</li> <ul> <li>Suggested locations: Tel Aviv, London, Barcelona, Berlin. </li> <li>Possible alternatives, side event prior to or after an industry event.</li> </ul> <li>Write-up of design specifications, including wireframes by UI designers and user journeys</li> <li>Ongoing community management</li> </ul> <h3>Topics to be covered in the tDSN specifications</h3> <ul> <li>Content moderation and community guidelines</li> <li>Domain release</li> <li>Domain pricing</li> <li>Technical specifications</li> <li>Dispute resolution</li> <li>Security</li> <li>Abuse prevention</li> <li>Budgeting</li> <li>Membership</li> <li>Payments</li> <li>Revenue models</li> </ul> <h2>November 2023: Meta-Governance design</h2> <h3>Topics to be covered in the Meta-Governance discussions</h3> <ul> <li>DAO procedures</li> <li>Strategy for DAO</li> <li>Calls for proposals</li> <li>Treasury oversight</li> <li>Budgeting</li> <li>Marketing DAO</li> <li>Staffing for DAO </li> </ul> <h2>2024 and beyond </h2> Design of the R&D / development DAO is premature. The tomi team will still need to be the primary providers for coding and management of the code base through at least the first year of operation, starting in May 2024. Starting in December 2024, the DAO will begin design for the development DAO which will allow the community and DAO to take over the core development of the tomi technology, over the course of 2-3 years, as set out in the whitepaper. <h1>Deliverables</h1> Each phase of the work requires reporting and design documents that can be reviewed and commented on by the community. <h1>Cost Estimations</h1> Total Budget requested: 30,000 TOMI Budget breakdown: https://docs.google.com/spreadsheets/d/1wiHmDerfeX6Fv7VWGNg51nclbbH4QDiC7qWWQ56qkng/edit?pli=1#gid=1043847968 https://docs.google.com/document/d/1OpYksmPAXGKSyvUmrQIzcaEdr3hQLif8v85_oKsUPwc/edit <img src="https://miro.medium.com/v2/resize:fit:720/format:webp/1*lc97ujH9bBLzW376bnijGg.png" alt="undefined" style="height: auto;width: auto"/>

0x1ee13d3b…b759sent to0xdeae2abb…14eb2023-07-10·#17,664,385·0xe376f64d…a900f3

SSI wallet specification from walt.idFull Proposal is found at https://docs.google.com/document/d/14GIpTrl2ZgM4W1veachIQMSN-rWDAB9xISa6NU6_0AM/edit If there is a discrepency, the text below is the authority as this is what the DAO has passed. MAIN GOALS  <ol> <li style="margin-left:1.5em;"></li> </ol>  Specifications Create identity and wallet specifications enabling the implementation of holistic identity and wallets solutions for Tomi DAO’s ecosystem. The specifications will include data models, sequence diagrams, component definitions (etc.) to enable identity concepts like  <ul> <li style="margin-left:1.5em;">Decentralized Identifiers & Verifiable Credentials </li> <li style="margin-left:1.5em;"> Authentication and Data exchange protocols </li> <li style="margin-left:1.5em;"></li> </ul>  Privacy preservation techniques (e.g. selective disclosure)  <ul> <li style="margin-left:1.5em;">Trust Registries (e.g. for organizations, data schemas) </li> <li style="margin-left:1.5em;">NFTs and/or SBTs and related metadata storage</li> </ul> The specifications will result in an “identity flavor” that is aligned with Tomi DAO’s vision and goals and firmly based on open industry standards. 2. Proof-of-Concepts Alongside writing the specifications, we will implement Proof-of-Concepts (PoCs) to validate the specifications and ensure they can be effectively implemented in practice. Moreover, these PoCs can be used to showcase and test the use cases in practice 3. Potential future collaboration (beyond specs and PoCs) Based on the specifications and PoCs, we may develop a generic identity infrastructure as well as solutions for different use cases ready for use in production. The provided solution may enable the following capabilities  <ul> <li style="margin-left:1.5em;">For “Issuers” - The solution will enable the creation, signing and issuance of Verifiable Credentials to third party’s identity wallets. Also, the solution will enable minting of NFTs (e.g. based on EVM-chains via ERC-721) for on-chain identity use cases.  </li> <li style="margin-left:1.5em;">For “Holders” - The project will extend Tomi DAO’s existing wallet with identity capabilities (i.e. request, store, manage, present Verifiable Credentials, selective disclosure).</li> <li style="margin-left:1.5em;"></li> </ul> For “Verifiers” - The project will enable the request and verification of Verifiable Credentials and the verification of NFTs/SBTs from different ecosystems (e.g. Ethereum, Polygon, Near, Tezos, Flow, Polkadot parachains, Algorand, …) for use cases like authentication, data verification, token-gating, etc. In addition, the project will enable such verifications via existing identity and access management applications or tools (e.g. KeyCloak) thanks to an identity provider we will develop to ensure backwards-compatibility.   These generic capabilities enable any type of identity use cases such as the ones outlined in the beginning of the proposal but also other use cases where proofs and identity data is being issued, managed or verified. The core team will consist of the following people: Dominik Beron (CEO) Lead: Product & Distribution  <ul> <li style="margin-left:1.5em;">Serial entrepreneur and founder of walt.id </li> <li style="margin-left:1.5em;">Law degree (Mag/JD) and executive education (from University of Pennsylvania and Oxford) </li> <li style="margin-left:1.5em;"> Identity expert to high-profile clients (EU Commission, governments, multinationals) and top-tier consulting firms (e.g. BCG, McKinsey, Gartner, IBM, …) </li> <li style="margin-left:1.5em;"> Speaker at podcasts, conferences (e.g. EIC, Money20/20) </li> <li style="margin-left:1.5em;">Former advisor to the UN, Austrian Parliament</li> </ul> Philipp Potisk (CTO) Lead:Development & Community/ Support <ul> <li style="margin-left:1.5em;">Serial entrepreneur and founder of walt.id</li> <li style="margin-left:1.5em;">Software engineering, business economics degree (MSc)</li> <li style="margin-left:1.5em;">+15y of work experience in software engineering</li> <li style="margin-left:1.5em;">Built and led diverse tech teams</li> <li style="margin-left:1.5em;">Built large-scale software-solutions for inter/national clients (Verisign, Telekom Austria, Infineon, Siemens, etc.)</li> <li style="margin-left:1.5em;">Background in security, biometric passports and the corresponding inspection systems</li> </ul> Severin Stampler(Chief Architect) Lead:Architecture <ul> <li style="margin-left:1.5em;">Software engineering, business economics degree (MSc).</li> <li style="margin-left:1.5em;">+15y of work experience in software engineering</li> <li style="margin-left:1.5em;">Built and led diverse tech teams (from start-up to exit)</li> <li style="margin-left:1.5em;">Built large-scale distributed systems in the field of AI/ML (e.g. NLP), big data, data processing, analysis, and retrieval</li> </ul> Tamino Baumann Dev Advocate & Product Owner <ul> <li style="margin-left:1.5em;">+3y of experience in engineering</li> <li style="margin-left:1.5em;">Experienced dev advocate and customer success manager</li> </ul> Fatima Beron People & Ops (incl. SCRUM master) <ul> <li style="margin-left:1.5em;">Business and economics degree </li> <li style="margin-left:1.5em;">Ex-startup founder / COO (Impact Venture) </li> <li style="margin-left:1.5em;">Ex-Deloitte (Consultant)</li> <li style="margin-left:1.5em;">Forbes 30 under 30 (by Forbes US)</li> </ul> Kevin Burgman Development & Community <ul> <li style="margin-left:1.5em;">+5y of experience in engineering - incl. 2y in identity/SSI</li> <li style="margin-left:1.5em;">1st employee at walt.id</li> </ul> Mike Plotean Development <ul> <li style="margin-left:1.5em;">Software engineering degree (MSc)</li> <li style="margin-left:1.5em;">+8y of experience in engineering</li> <li style="margin-left:1.5em;">Background in AR/VR</li> </ul> <h1 style="text-align:justify;">Work Statement </h1> <h1>Approach</h1> This proposal follows a “tiered approach” by which the project is split into the following parts: <ol> <li style="margin-left:1.5em;"><ins>Specifications</ins> - Definition of specifications for an identity ecosystem built for Tomi DAO.</li> <li style="margin-left:1.5em;"><ins>Proof of Concept (PoC)</ins> - Implementation of PoCs to validate the specs and test use cases. </li> </ol> After this, we propose to develop an identity infrastructure ready for use in production - based on the specifications and PoCs. Methodology We develop PoCs (evaluate feasibility) which are built out for production. Hypotheses are verified in short sprints before committing deeply. Communication To streamline communication we suggest a common communication channel, particularly for the technical teams, such as Slack, Discord or e-mail. Reporting We will publish project progress (e.g. via our public roadmap) and can report directly to any oversight board. Risk Mitigation Quality assurance methodologies are used to ensure functionality of the developed components and compliance with project requirements. All components are developed including unit tests, where applicable. Continuous integration and deployment is set-up to ensure the build and deployment process is stable, and to facilitate regular UI testing on the deployed testing systems. <h2 style="text-align:justify;"></h2> Scope & Limitations The code (PoC, production system) can be deployed, run and maintained locally by the Tomi DAO or potentially any other third party (e.g. walt.id). User interfaces (front ends) or end-user applications (native mobile apps) will not be provided. However, walt.id’s experts can offer support to facilitate the development of applications and integrations. <h2 style="text-align:justify;">Timeline</h2> <h2>Execution of the work will take 2-3 months </h2>

0x1ee13d3b…b759sent to0xeaad6b20…4f5f2023-03-12·#16,811,958·0x089a4d1e…6981aa

Deepfake videos of Peter Schiff, Jerome Powell and Warren Buffet, with screenshot of their Metamask buying up USDC and DAI.