metadata: {"signature": "0x43c06fb3fe5b3118e5343732b8d848943f9565cdff0f41d8c1a4fdc60ad4caf10a03d975a9085ab0195a6c58f8e0d8c2f9047a1e7db71ed77e965a5e35042ee81b", "application": {"round": "0xc1cffd1845deee83ab44cae123738a854593bcd2", "answers": [{"type": "checkbox", "answer": ["Developer Tooling"], "hidden": false, "question": "How does your project contribute to the advancement of the Arbitrum ecosystem?", "questionId": 0}, {"type": "paragraph", "answer": "Our automated procedures trigger on-chain events, such as transferring payments or issuing attestations, on the Arbitrum blockchain. This integration enables Web 2.5 organizations to incorporate on-chain actions into their daily operations, paving the way for new blockchain use cases.", "hidden": true, "question": "Describe your previous work or plans related to the Arbitrum ecosystem. How does your project strengthen Arbitrum's foundational infrastructure, improve developer efficiency, or accelerate the adoption of novel applications?", "questionId": 1}, {"type": "paragraph", "answer": "We automate on-chain transactions and create attestations for on-chain data tracking. Our goal is to become the first on-chain CRM.", "hidden": true, "question": "If applicable, describe how your project leverages Stylus or Arbitrum Orbit Chains. What unique capabilities or use cases does this enable?", "questionId": 2}, {"type": "paragraph", "answer": "Our team implemented a retroactive platform for ", "hidden": true, "question": "Describe your team's expertise in your chosen focus area within the Arbitrum ecosystem. Include relevant experience, publications, or past projects.", "questionId": 3}, {"type": "short-answer", "answer": "https://gap.karmahq.xyz/project/microflow-1", "hidden": true, "question": "Please provide a link to Karma GAP, where you are tracking and reporting on milestones.", "questionId": 4}, {"type": "paragraph", "answer": "", "hidden": true, "question": "List any contract addresses with the associated network(s), EOAs, or deployer addresses your project has deployed.", "questionId": 5}, {"type": "paragraph", "answer": "No", "hidden": true, "question": "Have you received any previous grants or support for your work in the Arbitrum ecosystem? If so, please provide details and estimated funding amounts.", "questionId": 6}, {"type": "dropdown", "answer": "Yes", "hidden": true, "question": "Please confirm that you have read and agree to comply with the ethical standards outlined in the eligibility criteria, including Gitcoin's Quid Pro Quo policy (https://support.gitcoin.co/gitcoin-knowledge-base/gitcoin-grants/general-questions/what-is-our-quid-pro-quo-policy)", "questionId": 7}, {"type": "paragraph", "answer": "No", "hidden": true, "question": "Do you have any potential conflicts of interest to disclose? If yes, please provide details.", "questionId": 8}, {"type": "paragraph", "answer": "Pattern flow is previously known as Microflow. We are in the rebranding process. ", "hidden": true, "question": "Would you like to share anything else about your project, team, or vision for the Arbitrum ecosystem that wasn't covered in the previous questions?", "questionId": 9}], "project": {"id": "0x35f798b08521bbe3b812c2805be2d99b299eb1624111283ad7567e38baf901a6", "title": "Pattern Flow", "logoImg": "bafkreigibh4zp34ic2rahlstx6gbk7egrsz3m3bj37sqktkft2aabphiuu", "metaPtr": {"pointer": "bafkreigxhb56kmx3ler6vm7g5gglvm655faoayakhxb7pinz3dwphuroze", "protocol": "undefined"}, "website": "https://www.patterns.community/", "bannerImg": "bafkreigptatvd2hg665lnaei6iz25fzpw2prw3ewqlv6njhzf2tp3tnpfy", "createdAt": 1722361157882, "credentials": {"twitter": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..wZVYOJH_5s62HvQoqCX070HZGXd9rVN7ZcYBi6LIeGrRQvjcYVBSieVwzOx4aDznPNLSWRQyHXrjKL_h9guUBg", "type": "Ed25519Signature2018", "created": "2024-07-30T17:36:33.705Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2024-07-30T17:36:33.704Z", "expirationDate": "2024-10-28T17:36:33.704Z", "credentialSubject": {"id": "did:pkh:eip155:1:0x08E3f287AdBA42A26904919917Bc7907f1f0df18", "hash": "v0.0.0:jbFblUlrLSGAg3drjiQ8fU8zUpieJMlL0/PMtqHVGCs=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextTwitter#pattern_global"}}}, "description": "# Pattern Flow\nI still remember my first day joining a DAO. I was bubbling with excitement. The idea seemed groundbreaking: an organization born in the digital world, where every step, from making decisions to getting things done, would be smooth, automatic, and transparent.\nInstead of a regular bank account, everything was in a smart contract. A Discord server took the place of traditional offices. All the processes were digital and secured by the power of blockchain. These new digital groups promised to be places where people could unleash their creativity, free from the usual limits of traditional organizations.\n# Problem\nWell, I thought I was joining something really cool and new, but man, was I wrong. Shortly after I started, I realized these new organizations had way more problems than I anticipated. Here's what I ran into:\n**Super Slow:** Instead of a fast, smooth online system, everything moved like molasses. Too much communication back and forth and simple choices that should have taken minutes dragged on for days or even weeks. It was like being stuck in the world's slowest drive-thru.\n**No Real Rules:** Trying to set up and stick to standard ways of doing things was nearly impossible. Without clear guidelines, it was chaos - like trying to organize a kid's birthday party with no plan.\n**Doing Everything the Hard Way:** I thought bots would handle the boring stuff. Nope! Some contributors should spend hours doing repetitive tasks manually. Jumping from one tool to another which could be easy to mess up - exactly what I thought these new orgs would avoid.\n**Not Better, Often Worse:** The biggest letdown to me was the fact that our fancy new org wasn't just failing to defeat regular companies - it was often less effective. It's like we tried to build a better mousetrap and ended up with a cheese dispenser. \nIf digital orgs are not helping us to do things better, what\u2019s the point then? Why are they buried under a ton of challenges despite their revolutionary potential?  I felt like I'd bought a ticket to the future but ended up in a time machine stuck in reverse. \nThis experience has led us to believe that we need a radical rethinking of how DAOs operate, which is the origin of this proposal. \n\n# Solution\nTo address these inefficiencies, we designed a new process automation management system. Our Pattern Flow platform allows DAOs to define a journey and create a procedure using both manual and automated steps. This ensures that every business item follows the same steps without forcing the admin into full automation. The semi-automated process enriches the workflow by removing tedious tasks while giving the admin the flexibility to include necessary manual tasks or skip steps as needed.\n\nTransparency is another key component of our dashboard. With Pattern Flow, both users and admins have full visibility. Users can see their current position in the process and the actions required to reach their final destination. Additionally, the DAO can monitor everything happening within the organization and delegate the management of different business items to specific individuals. By unifying these processes, we not only create a transparent and immutable track record of events but also lay the foundation for a reputation mechanism. This mechanism allows individuals to prove their track record and gain more privileges based on their reputation.\n\nCurrent traditional organizations heavily utilize ERPs and CRMs, creating a unified one-stop shop to streamline their day-to-day interactions and activities. In contrast, DAOs are scattered across Notion, Discord, and various Web3 tools, and numerous contributors manually manage everything. While the idea of Web3-friendly enterprise software might seem futuristic but it is the ultimate CollabTech tool that can unleash the full potential of internet native organizations, Pattern Flow aims to bridge this gap with its semi-automated process builder. This reduces manual work and accelerates processes within DAOs.\n# Case Studies \nHere are some case studies to better outline the idea:\n\n### Nonce DAO Post Voting Flow\nCurrently, after the voting, an admin is required to manually add the winners to a spreadsheet, create an attestation for proof of participation, use Safe to create a transaction and chase down signers to finalize the transaction. \nThis process suffers from a low compilation rate and lack of transparency, and it heavily relies on the admin\u2019s tedious work. \nWith Pattern Flow, we can automatically index the winners from Prop House, create their on-chain reputation using EAS and off-chain records in Google Sheets, and finally fire an optimistic transaction on Safe. This will create the utmost transparency for DAO. The admin can interfere as needed, and winners can track their own profiles through each step of the process.\n\n### EthSafari Sponsors Agreement Flow \nIt starts with potential sponsors submitting a form on the website, which feeds into Notion for tracking. The team then negotiates packages, updates the sponsor\u2019s status in Notion, and creates a tailored contract sent via DocuSign for signatures. Post-signature, an invoice is manually generated from Google Sheets, with payment options in cryptocurrency or fiat, followed by KYC verification using Fractal-ID. Once payment is confirmed, the EthSafari team ensures sponsors receive all benefits, including website logo updates, social media posts, and newsletter features.\nThis process requires extensive manual back-and-forth, in addition to all the pain points mentioned in the previous flow. Although it is obvious that not every step of the process can be automated (e.g., negotiation), it can benefit from automation and transparency.\nWith Pattern Flow, we can automatically index the sponsors. Let the admin add the key details in the manual step defined for negotiation and then automate the rest using attestations, automated invoices, and contract generation while keeping all off-chain records, such as Google sheet and Notion, up to date at all times. \n# Commercial Viability\nOur goal is to cover as much ground with as little components possible, doing so helps us to deploy funding effectively and have enough integrations that can help multiple businesses streamline various procedures and use cases. Doing so, will significantly reduce our need to develop over time without hindering customer experience thus resulting a commercially sustainable project. Moreover, Pattern Flow will significantly reduce cost on the business by eliminating unnecessary work and helping contributors to deliver impact effectively. Businesses can support us by paying for new integrations. \n# Threshold\nThreshold funding needed to bring Pattern Flow to life: 500$\nThis will help covering the cost for developing remaining automation steps and integration building blocks needed to create a complete flow.\n# Delivery Timeline\nWe are looking at launching the first version of our platform by October 2024.\n", "lastUpdated": 0, "projectGithub": "pattern-tech", "projectTwitter": "pattern_global"}, "recipient": "0x2e57674Ea14FA08A6DDa865dd139cE3924ab5951"}}