{"signature": "0x456953f7f7ce3f3ec24d2f750f83f59bb6547bfbe140065f1494c13aa773e65b214e88a31cedbcf8b451d8c1420bdbcd79c690a4d9652808e06d86a496034e8c1b", "application": {"round": "0x145052E87140b7309F6EE18Ba12fC187560d5D89", "answers": [{"type": "email", "answer": "leomarlo.eth@gmail.com", "hidden": true, "question": "Email Address", "questionId": 0}, {"type": "short-answer", "answer": "leonhardmarlo", "hidden": true, "question": "Telegram Handle We Can Use To Contact You", "questionId": 1}, {"type": "short-answer", "answer": "https://github.com/Lakat-OS", "hidden": false, "question": "Project Github Repo", "questionId": 2}, {"type": "link", "answer": "https://t.me/+BGvsUzF1ds80YmFk", "hidden": false, "question": "Link to your Public Group Chat", "questionId": 3}, {"type": "paragraph", "answer": "https://explorer.gitcoin.co/#/projects/0x29731d9ec0ae453f5a75430735ab1e20bb85dceb77892469da097aec4bfca54f", "hidden": false, "question": "Have you participated in a previous Gitcoin Grants Round? If so, please name the rounds or link the builder profile to prior rounds.", "questionId": 4}, {"type": "paragraph", "answer": "We build a protocol multi-branched git-inspired edit-centric publishing protocol whose data-layer is anchored in Ethereum (or EVM-compatible L2s).  ", "hidden": false, "question": "How does your project contribute significantly to the Ethereum network's infrastructure? Please provide specific examples and metrics if available.", "questionId": 5}, {"type": "paragraph", "answer": "We have spend some time discussing various solutions about using diversified anchoring, where merkle roots can be stored in any one of a given set of networks. Also we are thinking about social identity and key recovery concepts, where private keys are trustlessly spread across contributors of the platform and they are incentivized to return the information to recover the key. This is currently sought as a standalone feature. ", "hidden": false, "question": "Describe any pioneering development work in your project, particularly in enhancing privacy, interoperability, or user experience.", "questionId": 6}, {"type": "paragraph", "answer": "We believe that Ethereum ecosystem can be strengthened by diversifying its utility. Currently the utility is heavily skewed towards DeFi. Whilst solutions for decentralized publishing exist, they are either standalone blockchains like gosh, that are not leveraging the security and versatility of Ethereum, or they are token-centric DAOs that tokenize research products, but not the iterative process.", "hidden": false, "question": "What specific problems or challenges in the Ethereum ecosystem does your project address? How does your solution improve upon existing alternatives?", "questionId": 7}, {"type": "paragraph", "answer": "We have been pivoting towards a new approach: Users can interact with Lakat on multiple branches, like on git, that all share a set of contributors. Private keys can be recovered socially whereby the other branch contributors act as guardians and are incentivized to contribute to the recovery process. We aim to finish this piece in April/May and integrate it into the existing lakat-protocol. In May/June we update the user-facing interface build on top (as an extension) of media-wiki and disseminate in academic institutions over the summer and autumn months.", "hidden": false, "question": "Outline your project's roadmap and how the grant funds will be used to achieve your development goals.", "questionId": 8}, {"type": "paragraph", "answer": "By anchoring the data-layer of Lakat into Ethereum we diversify the applications that are rooted in the network. ", "hidden": false, "question": "How does your project contribute to the decentralization and security of the Ethereum network?", "questionId": 9}, {"type": "paragraph", "answer": "0x07c33D5C1F3f0dBd03d6Ba4C55F2B5277D1faF59, 1", "hidden": false, "question": "For any project deploying smart contracts on blockchain networks, please list all your deployer addresses and their corresponding blockchain networks. Use this format for each entry: [deployer_address], [chain_id]—for example, 0x123abc..., 42161 (This represents a deployer address on the Arbitrum network). Please include a separate line for each unique deployer address and blockchain combination.", "questionId": 10}], "project": {"id": "0x29731d9ec0ae453f5a75430735ab1e20bb85dceb77892469da097aec4bfca54f", "title": "Lakat 📜", "logoImg": "bafkreihdjgarsp6ictmenp34e3pxhipyxsmezsz72zdl7k4mehucoulz54", "metaPtr": {"pointer": "bafkreiewh3cgivau5vd3w7xen75xcc3g3ec26f6n5fwjhozy4wzn3hztt4", "protocol": "undefined"}, "website": "https://lakat.science", "bannerImg": "bafkreigjbwwijst4rmfkd75r5mqhazqk2e3gtezsdxawpdtflqvxscl3ay", "createdAt": 1699400223139, "userGithub": "leomarlo", "credentials": {"github": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..G8Y0tuUJDG-KVL5k8ojX_jugSvVy6OKX6K8gkU6B3NX3ChXxaVIMs2vG1hRVe0RJUPg3GFjZR85govtUpGd4DQ", "type": "Ed25519Signature2018", "created": "2023-11-07T23:35:25.436Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2023-11-07T23:35:25.436Z", "expirationDate": "2024-02-05T23:35:25.436Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xAbb9aC1F97FB9b40a538B41f7F5e3681d4495bE5", "hash": "v0.0.0:KwKw3/QIoe1SttCltXj9dUUyCYdXmW9QVYwBsKw18hI=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextGithubOrg#Lakat-OS#7916619"}}, "twitter": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..oruvFBAZm5G7DZgILqxJgaG8ADv_zuAA8n76vvI5mtFd1VzPx41MN5BavKZSBn7RQsdBedJB7tbhK0KAJemcCA", "type": "Ed25519Signature2018", "created": "2023-11-07T23:35:09.899Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2023-11-07T23:35:09.899Z", "expirationDate": "2024-02-05T23:35:09.899Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xAbb9aC1F97FB9b40a538B41f7F5e3681d4495bE5", "hash": "v0.0.0:fGWelrP5JEnyMXdMgiiRYp/2nfRzh5jQRM5XEd8l628=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextTwitter#__Lakat__"}}}, "description": "# An open and permissionless architecture for continuous integration academic publishing\n\nLakat is a base layer for a publishing system that promotes collaboration, pluralism, and permissionless participation. Lakat supports continuous integration of scientific research across multiple branches through a proof-of-review consensus mechanism. It integrates with the Ethereum ecosystem in several ways: Storage, tokens and proofs. The storage of content will be anchored in Ethereum through the ceramic protocol. Each branch has an option to interact with a branch token whose utility emerges from the usages within a branch. Proofs of data submission will be deployed as contracts on Starknet, a zk-rollup over Ethereum. Lakat's architecture allows for the necessary flexibility to grow and to allow for the integration of existing reputation systems and incentive structures or facilitate the development of new ones.\n\n## About \nPlease read more about the protocol on [the lakat.science page](https://lakat.science). We are a growing team of people enthusiastic about descentralized science. Our development currently focusses on building a client in Rust and an extension for mediawiki ([see our github repositories](https://github.com/Lakat-OS)). Our main code contributors are: @leomarlo, @Tconomist, @mkourehp and @kuzmaka (github handles). Please get in touch if you would like to join. \n\n## Roadmap\n- [x] Protocol Technical Specification (see the [whitepaper](https://arxiv.org/abs/2306.09298)).\n- [ ] Develop a Rust client that implements the specification (i.e. the traits in Rust-speak) \n    - [ ] Creation of a Branch.\n    - [ ] Storage of the Branch Data on the ceramic network.\n    - [ ] Proof-of-Review Consensus mechanism (See [whitepaper](https://arxiv.org/abs/2306.09298)).\n    - [ ] Integration of Branch Tokens.\n- [ ] Development of a Gateway to Lakat through a (see [mediawiki extension](https://github.com/Lakat-OS/mediawiki-extension)).\n- [ ] Test the flow with researchers from the field of Statistical Physics.\n- [ ] Release Rust client.\n\nThe development of the Rust client will take place in Q4 of 2023 and Q1 of 2024. The gateway is planned to be developed in Q1 and Q2 of 2024. Testing is done continuously, but field tests with academics will be in Q2 of 2024. We plan to release the Rust client in the beginning of Q3 of 2024.\n\n## Contact\n\nFind us on X (twitter): [Lakat](https://x.com/__Lakat__) \n\nContact us via e-mail: lakat.science✉gmail.com\n\nCheckout our Repositories: [Lakat-Os Repositories](github.com/Lakat-OS)\n\n---", "lastUpdated": 0, "projectGithub": "Lakat-OS", "projectTwitter": "__Lakat__"}, "recipient": "0x756C495c106d1eE204A4D43e4038a0c4CA89fE0c"}}