{"signature": "0x9a6bdd2b2e399f81ebbff6fa8162d71a6a135cfbb7b4475570da186e3846aa0b45287b63bc06b3885fcb556973c9f2e39dd3444775838d636d2a37900ad474f11c", "application": {"round": "0xedb366e318fc2c94c16852ff2fb99a3f59db8cbb", "answers": [{"type": "email", "hidden": true, "question": "Email Address", "questionId": 0, "encryptedAnswer": {"ciphertext": "m4zeADd2AfOpaOWqfa1pwQFobyaTCHXkwWbIhyMxRNVB7pI21qm6nVZHdwzlkpym", "encryptedSymmetricKey": "ea6b3a13eebca7708e458c7aa28ca7d56feca956ec77428e6e1580243add643482e913ff0d9ff59a52796b0523034c0ef1a6a18d849a592046e8f1bc0a2e4c8ca9bdcdc64f651e44b809b44ae64ad1ec0485ebedf7e35bb823266e177a1530a4fcd813259933b5f3f5dfb075ca91439158d3925fba76f1bd44a3852fb84de883000000000000002067e14e686208659fd686b205de79ba6d8d8b3bb137d88df947c7b7ac95c9a49c6f2fbc510007f926565d4e5bbe499c86"}}, {"type": "short-answer", "answer": "Bootstrapped", "hidden": false, "question": "Funding Sources", "questionId": 1}, {"type": "number", "answer": "6", "hidden": false, "question": "Team Size", "questionId": 2}], "project": {"id": "0xa09573cb6ae35fd530b553de47f0749273edb30d48c72ca3960672937d2bfeeb", "title": "Formo", "logoImg": "bafkreihndv2guk6oogunhyngntdhlvtjox747meqbqnsxofbaovvtkloki", "metaPtr": {"pointer": "bafkreicxr4dpxg4eymyrfuyqnoofqnqa5ojl3tkyvzerkaq7mxgiz5g27u", "protocol": "undefined"}, "website": "https://formo.so", "bannerImg": "bafkreif2fmpa57vysfcf4yhqcfbgldwsyiamu5rsel36gymz5ky3r4tc5u", "createdAt": 1712148277295, "userGithub": "yosriady", "credentials": {"twitter": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..3lNJcWEIZUwdFsXExGjo2ZAy7vht0pbbW-jbtKMIIbWgbrLHgO13M6vutRKE-nR-gQLY0XZkTVuaf3hsQWFnCw", "type": "Ed25519Signature2018", "created": "2024-04-03T12:43:43.562Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2024-04-03T12:43:43.562Z", "expirationDate": "2024-07-02T12:43:43.562Z", "credentialSubject": {"id": "did:pkh:eip155:1:0x9CC3cB28cd94eB4423B15cdA73346e204f59a407", "hash": "v0.0.0:NvRfs2U2aD9sr0gs/ZyGsiUiWhd5sW672YmdX2xe3sY=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextTwitter#getFormo"}}}, "description": "We believe that crypto is in a great era of experimentation for applications and consumer facing products, and that analytics / growth tools are critical to their success.\n\nIn the early years, a wave of excitement about blockchain technologies and web3 applications drove a mad rush to capitalize on a new and wide-open market. Since then, web3 has started to mature, the dust has settled, and the speculators and hype-driven projects have gradually fallen to the wayside.\n\nIn their place, a wave of web3-native product teams are building in the space to generate meaningful, sustainable growth. In the process, teams are realizing that tried-and-true growth tactics of web2 can’t deliver the same results in web3.\n\nOnce users are on-boarded to a product, it’s critical to understand how they interact with it: \n\n- Who decided to participate, and what drove them?\n- Where in the product are they spending most of their time, and where should they be spending more?\n- Who returned to the product once over a span of a month, and who returned twenty times?\n- At which point in the flow do most users drop off?\n\nAnswers to these questions provide data-driven insights into future directions for the product, and how to keep customers happy.\n\nHowever, most Web2 growth strategies and tools start from the assumption that potential customers are known. **Web3 breaks this assumption as the majority of on-chain activity is pseudonymous.** We don't know who our users are in web3. Traditional web analytics use cookies, which are largely absent in Web3. This makes it difficult for web3 teams to identify demographics, user journeys, CAC, and conversion rates.\n\nIn addition, **much of web2 tools are ill-suited to the needs of the companies and projects operating within crypto and web3.** Marketing automation and customer engagement solutions like Hubspot and Klaviyo don’t account for on-chain activities and events. Product analytics and attribution platforms like Mixpanel and Amplitude lack blockchain and token data.\n\nWe're building **a no-code analytics tool** that removes the need for blockchain projects to hire an internal data team of SQL engineers that cost $150K+ annually  to produce actionable insights thereby saving them hundreds of thousands of dollars in labor costs and months of development time.\n\n**We believe creating this missing infrastructure piece will enable a new wave of web3 apps and services bloom.** ENS support gives web3 teams the full picture of their pseudonymous audience.\n\nLearn more at https://formo.so.\n\nHarness web3 forms, wallet intelligence, and onchain journeys to engage and grow your web3 community. ", "lastUpdated": 0, "projectGithub": "", "projectTwitter": "getformo"}, "recipient": "0x9CC3cB28cd94eB4423B15cdA73346e204f59a407"}}