{"signature": "0x6d2fbd603d5a4a1cea08e50add55a52ee419e9c71dea0e1f2acae3145af2cbe64b0a3980e2b4be87ff24fbd20217dc623865f543fbe4ca71f8e26f6e06f5cbc41c", "application": {"round": "0x9e669c0a6e075f14ba9d9d98c3580ad67e20ec38", "answers": [{"type": "email", "hidden": true, "question": "Email Address", "questionId": 0, "encryptedAnswer": {"ciphertext": "kd9jaNOHkFJD2HdCRNsgDrdxhz493FuuckWriTjyXD7N/3mPxt3J/UYL2V6Ul1K7", "encryptedSymmetricKey": "6872d0c9a7a0bbf4152d478fc9b4da05345f2b66e3f63f2d050d0cf2f7835b76bae31ba051bdfd72cda3f766b98c4301b8c9a305c8ebf6135fc0f8cc8ebf768cad61c91f040f1fafcc1d8999aca9c67aa9b2dea1f0be8d05675a9df17a40afb66ca06c97f3dbb977ee868ea1891a4a1c5b4cd90a2ad4781224be04250e1264be0000000000000020a20309250480d1ff161cd0194b0b9cbb4725f3762e01d7842583088ab12e0699eb2cd4cc0a8cad4049512fa01e3e34a2"}}, {"type": "short-answer", "answer": "No", "hidden": false, "question": " Previous project funding sources (VC, grants, token sales, etc)", "questionId": 1}, {"type": "number", "answer": "4", "hidden": false, "question": "Team Size", "questionId": 2}, {"type": "short-answer", "answer": "0", "hidden": false, "question": "Total prior funding for project in USD", "questionId": 3}, {"type": "short-answer", "answer": "Idea phase", "hidden": false, "question": "How old is the project? (Months)", "questionId": 4}, {"type": "short-answer", "hidden": true, "question": "If you participated in past Gitcoin grant rounds using a different project payout wallet address, please share it here:", "questionId": 5, "encryptedAnswer": {"ciphertext": "zpWsmacqS25HntTGLOMECzIgwnZv86v5AAHvkvohV3s=", "encryptedSymmetricKey": "bb511df569d7b767a700c7e87ca6c8934a6098ae667f75bf8314292c7ae7aa1ec1a2fc1dcaace6350e1635886ea8a911ac9eb2da354e6c9edac6a70ea7733e970421793e932716f4c399cb898e81ce26d5ec6980c305abbc9d136ba2720e959194bcbb37576d0d9aa342388fc6e02b339345efb4f335e16b79f4ea5a08b1ff640000000000000020ebf5d4b14ea0c57db2e67c15fae498a0000218a507c2065a05f921ecbf955be0f98f44905d269b7a16b6cf95969b3493"}}, {"type": "short-answer", "hidden": false, "question": "Profiles or socials of other main team members publicly associated with project", "questionId": 6}, {"type": "multiple-choice", "answer": "Yes", "hidden": false, "question": "Have you read and confirmed your grant abides by the Program General Eligibility Policy? https://www.notion.so/tecommons/Eligibility-Policy-7cf5ff8c323149cf84011712f070f009?pvs=4", "questionId": 7}, {"type": "paragraph", "answer": "This will be a TE exercise to evaluate use of utility token to capture & grow the inherent and latent value in the TE ecosystem onto the existing $TEC token. If validated, a Proof of Concept can be designed and implemented.\n\nNote that scope of this study has been limited to internal usage within the TEC/TEA ecosystem. However, there is a potential for such a system to grow into a much bigger scope involving external projects catalysing growth of Token Engineering with TEC at its centre.\n", "hidden": false, "question": "How does your project contribute to token engineering?", "questionId": 8}, {"type": "paragraph", "hidden": false, "question": "Please share any new updates or milestones from the prior months", "questionId": 9}, {"type": "paragraph", "hidden": false, "question": "Anything else you'd like to share about your project, previous work, or other project affiliations? Anything you'd like to add that has not been covered?", "questionId": 10}], "project": {"id": "1:0x03506eD3f57892C85DB20C36846e9c808aFe9ef4:653", "title": "Research on a Utility Token for TE Ecosystem", "metaPtr": {"pointer": "bafkreihlwgktjuzk2a75y2serh4mim5ilx5ti37hzqrosxx7onuf27x7iu", "protocol": "1"}, "website": "https://docs.google.com/document/d/1Bl0YvMB7wdtXk9jvcXGPg2vNd2ZnnyQcUCbwNBggTLk/edit?usp=sharing", "createdAt": 1682019283924, "credentials": {"twitter": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..vRGLhKoJFbeQbkREaaDEqgjkMeEt38nRLH4BQAkuwBQs-X24cePvYQfRE-BBqZaKx81gNxto1oyU7d3Y6VYABA", "type": "Ed25519Signature2018", "created": "2023-04-20T19:36:37.390Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2023-04-20T19:36:37.390Z", "expirationDate": "2023-07-19T19:36:37.390Z", "credentialSubject": {"id": "did:pkh:eip155:1:0x7e1F8358943580724290277167B86ab4734752fE", "hash": "v0.0.0:xXaaK/a7msaKLIrd0WYXe2tOtUjLXELzSRTm1HB1MfY=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextTwitter#0xPravar"}}}, "description": "# Proposal\nResearch, design, model and simulate a utility token ($TECKY) by applying Token Engineering (TE) techniques to promote value creation in the TE ecosystem.\n\n# Premise\nThe research starts with the fundamental proposition that there is a lot of underlying value in the TE ecosystem (TEC & TEA) in the form of knowledge, skills, expertise etc. Can we design a token ecosystem to capture and further catalyse flow of value?\n\nThe principal objective of the utility token's design is to capture value generated by applying the TE knowledge & expertise within and outside the TE Ecosystem.\n\n# Design Considerations:\nThis study will be performed with the following design considerations in mind.\n\n**Build on the existing $TEC token**, which is already listed, to support the $TECKY token. $TECKY will not be listed on any exchanges and will only circulate within the ecosystem. $TECKY will be exchangeable for the existing $TEC with suitable conditions to curb debilitating speculation. It will be a means to drive the demand for $TEC token. \n\n**Dynamic supply**: The quantum of $TECKY will be dynamic and based on the volume of transactions so that $TECKY itself does not appreciate in value. During periods of excess transactions, additional $TECKY will be issued, and during deflationary times of excess, the excess liquidity will be taxed out.\n\n**Soul Bound Tokens**: We will consider using Soul Bound Tokens (SBTs) as part of the design. SBTs will not be purchased but will be issued to all eligible participants. Suitable assumptions will be made regarding SBTs as deemed fit during the study.\n\n**Reduced Configuration space**: We will make reasonable assumptions to reduce the scope of work to fit constraints of this study. However, the reduced configuration space shall still be representative of the larger scope.\n\n# Research Direction:\nAs a purposeful token, $TECKY should not only facilitate flow of value but also incentivise value retention within the ecosystem by utilising the services and resources available within the ecosystem. \n\nThe focus areas which will be further developed during the study are as outlined below:\n\n*Rewarding Contributors*: Contributors in any form could be rewarded with $TECKY based on group policies.\n\n*Support New Ideas*: Assess & evaluate project ideas emanating from members including study groups. Fund shortlisted projects in $TECKY to support development of the project in lieu of equity/project tokens. The $TECKY received by the project to be utilised for services within the ecosystem.  \n\nDevelop mechanism to capture perceived value creation potential of the supported projects in $TEC. Therefore, good projects will generate good value, which will be reflected in the price of $TEC. \n\n*Education*: Investigate how $TECKY can be used to incentivise TE students & facilitate higher participation in the TE Academy ecosystem.\n\n*Access*: $TECKY tokens to enable access to the ecosystem resources. For example, consultation with a expert or a case study etc\n\n*Attack Vectors*: The study will also identify possible attack vectors and incorporate suitable mitigation measures.\n\n*$TECKY: $TEC relationship*: Understand how introduction of $TECKY will impact $TEC with respect to the external markets.\n\n\n# Research Outcome: \nThe research will follow the TE principles and techniques for designing $TECKY. We plan to produce the following at the end of this exercise:\n\n1. Visual Map capturing value flows between stakeholders\n2. Machinations Model. If time permits, we will also look to develop a cadCAD model.\n3. Simulations to showcase feasibility of the design\n4. Recommended steps to be followed for implementation\n\n# Conclusion:\nThis will be a TE exercise to evaluate use of utility token to capture & grow the inherent and latent value in the TE ecosystem onto the existing $TEC token. If validated, a Proof of Concept can be designed and implemented.\n\nNote that scope of this study has been limited to internal usage within the TEC/TEA ecosystem. However, there is a potential for such a system to grow into a much bigger scope involving external projects catalysing growth of Token Engineering with TEC at its centre.\n\nTo conclude, this is an exploratory study that will aim to establish the feasibility (or infeasibility) of using a utility token to aid in growth of the Token Engineering ecosystem and Token Engineering as an applied discipline. \n\n# Project Duration\nWe expect this study to be performed over a period of 02 months.\n\n# Funding Requested\nWe are requesting $6000 for this study. This value is much lower than what would be typically charged for such an exercise. \n\n# Team\n\n**Rohan Sundar**\n\nToken Engineering Lead - Fyde Treasury\n\nRohan has studied Applied Mathematics and Statistics from SUNY Stony Brook, represented the United States at the 2012 International Supercomputing Competition in Hamburg, Germany where he worked specifically on network design. Previous work includes health tech and energy tech, as well as building border surveillance systems for the defense department with custom machine learning models. In the web3 space, he has had experience creating custom market making bots for high frequency trading, has worked on a handful of smaller NFT projects (e.g. MintingPress), and is one of the members and was a local host educators for Token Engineering Academy. He is also a contributor to TokenSPICE - an EVM agent-based token simulator.\n[Github](https://github.com/rsundar) | [Twitter](https://twitter.com/skelegrow)\n\n**Pravar Joshi**\n\nToken Engineer & ex-Founder in Cleantech with 12 years of experience in different domains. Alum of Entrepreneur First deep tech accelerator program. Graduate of IIT Bombay\n[Twitter](https://twitter.com/0xPravar) | [LinkedIn](https://www.linkedin.com/in/pravar/)\n\n**Jose Antony**\n\nToken Engineer | Financial Engineer | X-prize finalist\n\nJose brings with him several decades of experience in entrepreneurship and management. \n[Twitter](https://twitter.com/Kojak) | [LinkedIn](https://www.linkedin.com/in/joseph-k-antony1956/)\n\n**Keshav Chakravarthy**\n\nI'm a full stack developer with extensive experience integrating payments into ecommerce platforms like Shopify. Using Kafka message queues, I've implemented real-time notification systems for WhatsApp and email, ensuring timely delivery. I recently participated in the Encode Club Solidity Bootcamp in Q1 2023, which provided me with hands-on experience in developing smart contracts using Solidity. My graduation DeFi project involved creating a contract that leveraged Aave flash loans to generate profits. My current tech stack includes Elixir/Phoenix, and I have prior experience in Ruby on Rails. I approach challenges in a language-agnostic way, prioritizing functionality and efficiency to create adaptable solutions.\n\n[Github](http://github.com/keshav-c) | [LinkedIn](https://www.linkedin.com/in/chakravarthykeshav/)", "lastUpdated": 0, "projectTwitter": "0xPravar"}, "recipient": "0x7e1F8358943580724290277167B86ab4734752fE"}}