metadata: {"signature": "0x3d2eb60a33dcec6b759314e896aa541fe68a9c072fd876e3ffe70c3b9443d5a027f765fde12f016125005df74e33d1da496776795674e250dd1c7ab72d2251551b", "application": {"round": "0x5b95acf46c73fd116f0fedadcbedf453530e35d0", "answers": [{"type": "email", "hidden": true, "question": "Email Address", "questionId": 0, "encryptedAnswer": {"ciphertext": "pc/feYVQ3WC9ffg2UgkIplLrAJci1FygdIHsGLjHzF26T+74mHFlnsYyCycyzihk", "encryptedSymmetricKey": "7ef63a212f4c61982c99e4d45f5d3a54f9892cad575020f39d1df230843fb8d40c5438dcba2677c7ce8d2c098b619b1234fc635419b711aa7dccf9f3dbe8487c7bc0728cca358ce62dd7f2a76bc6d1b87d2ca6177df4dbb08ec1d2a7d1b3638d671f8e653ef91e0417b351221dfa314ddcd3d2fe9f832677db67d71cd19419e80000000000000020aa990153aab870fafa4a67a067c76901da8b68b693c7e1fcee58423f770b0f3d0097eb5ce3baab6658a4c7563a9e4799"}}, {"type": "short-answer", "answer": "None", "hidden": false, "question": "Funding Sources", "questionId": 1}, {"type": "number", "answer": "3", "hidden": false, "question": "Total team size", "questionId": 2}, {"type": "paragraph", "answer": "Twitter: @arvinatwild", "hidden": true, "question": "Profiles or socials of other main team members publicly associated with project", "questionId": 3}, {"type": "paragraph", "answer": "We are planning to serve more communities (already reached out to some), and will expand the usage of our SBTs, such as verification.", "hidden": true, "question": "What are you planning to continue building for your project after Zuzalu? ", "questionId": 4}, {"type": "paragraph", "answer": "We are a project that's born to serve all kinds of communities, and trying to reverse tokenize the communities which are now having token-related issues. We want to use DID-based paradigm to help communities grow better.", "hidden": true, "question": "How does your project and future plan align with the Zuzalu mission? ", "questionId": 5}, {"type": "short-answer", "answer": "No", "hidden": true, "question": "Did you win a hackathon prize at Zuzalu?", "questionId": 6}, {"type": "paragraph", "answer": "No", "hidden": true, "question": "How much funding have you received and does your project have any other funding sources?", "questionId": 7}], "project": {"id": "10:0x8e1bD5Da87C14dd8e08F7ecc2aBf9D1d558ea174:950", "title": "SoulFrag", "logoImg": "bafkreihwdvmbd7cjc55uq63o4nvvvawgu3dy5a7caghchorbyhghixeq3m", "metaPtr": {"pointer": "bafkreidvebepwhrvttia7kjmbr2dd6f7faiybpuejxgmuz7grdhjjpeime", "protocol": "1"}, "website": "https://soulfrag.xyz", "bannerImg": "bafkreihandqjduvhm4swn64olhqagjmgz42vqplcm4xa42t3x32ozbrtua", "createdAt": 1692015061283, "credentials": {}, "description": "SoulFrag.xyz\n\nSoulFrag, the first DID-Based SBT System that aims to construct the cornerstone of human reputation for every individual and community.\n\nTwitter: https://twitter.com/SoulfragHQ\nGithub: https://github.com/DIDHQ/soulfrag\nAbout SoulFrag: https://www.soulfrag.xyz/about\n\nMore Description Below\n\nIf such a reputation system is based on addresses instead of DIDs, there are mainly the following problems:\n\n1. Private key leakage problem:\nThe current common practice for us when joining a Web3 community, is to create an EOA (Externally Owned Account) wallet. Such a wallet will give full ownership of the wallet to the user, and the user needs to take full responsibility for the security of the wallet. This type of wallet will prompt the user to manually record the mnemonic phrase (a form of private key) on paper. If SBT is bound to the address, once the user's private key is leaked, it means that all of reputation information that can represent this person will also be leaked, and anyone else can use these SBT information to impersonate this person. And the person whose identity information has been stolen has no possibility to make any remedy.\n\n2.  Poor readability of addresses\nImagine we are socializing with others in a community. When we introduce each other, we use a long list of address names generated by the wallet. At this time, it is difficult for us to associate such an address with the person we actually interact with. Only when we interact with the custom names of others, can we easily identify the objects we are interacting with. Here is where the Decentralized Identifier is at work in the DID equation we gave above. It allows us to identify each other.\n\nIdentifiers (understood to some extent as our real-life names) do more than just allow us to easily identify each other. We also bind our personal emotions to the name in the process of interacting with a person. When we see the name again later, we will automatically bind our emotions, trust in this person, and other psychological activities to the name. in addition. In real life, we also use forms such as \"he is a so-and-so person from such-and-such organization\" to introduce a person. DID's sub-account (SubDID) feature also supports us to do such things. For example, if an organization registers organization.bit / organization.eth, then he can distribute sub-accounts similar to arvin.organization to members of the organization, so that when members display their identities and reputation information outside, they will have a stronger sense of belonging, and it is easier for others to remember relevant information about this person.\n\nWe designed and developed such reputation management tool: SoulFrag - Soul Fragments that defines you.\n\nConsidering that SoulFrag is a DID-based reputation system public good, we support two DID infrastructures: .bit and ENS. Both DID systems support sub-account distribution (SubDID), and each has its own characteristics.\n\n.bit is a barrier-free decentralized naming system that aims to provide accessible DID-based solutions for everyone and every community. At the same time, the sub-account distribution system supporting .bit is relatively complete, and the gas fee is almost zero when using it. It is the DID infrastructure that SoulFrag will first support. ENS is a classic DID service on blockchain, and currently has a large number of holders.\n\nRegardless of whether the user is using a .bit identity or an ENS identity, all functions of SoulFrag can be used.\n\nVarious SBT categories:\n\nThere are currently three main different reputation (SBT) types for SoulFrag.\n\nCredit: \nThis is a stackable type of reputation. For example, the community needs to distribute points to record the contribution of members, or some gamified communities use it to record the experience of members; this kind of SBT can record some quantifiable behaviors with numerical values.\n\nBadge: \nIt is also the type of reputation that we use most often in our lives. This type of reputation is similar to a certificate, used to prove who someone is, what they have done, etc.\n\n\nUpgradable:\nDifferent levels can be set for this type of reputation. Members who have been assigned this type of reputation can clearly see which level of reputation they are currently at. Some gamified communities can use this type of reputation to define a clear personal growth path for members.\n\nWhen we designed these three different reputation types, we did not make too many preassumptions about how the community would use these three reputation types. What we hope to create is a foundation for an identity-based reputation system, and we will provide tools on top of this foundation for everyone to develop more complex tools and functions on top of it.\n\nBuilding a Public Good\n\nWe hope to uphold the open source and open spirit of the Internet and the public goods spirit of the Ethereum ecosystem. Therefore, SoulFrag will always be a:\n- Open source product; everyone can use it and make changes based on it.\n- Decentralized product; not owned by any company or institution.\n- Public goods; free for all to use and build more complex tools and functionality on top of it.\n- Permissionless; no permission from the development team is required to use SoulFrag.\n\nA Credible Neutral System\n\nThe credible neutrality of the system is one of the blockchain spirits we valued the most when designing SoulFrag. We hope that such a reputation system can make the reputation issued universally credible, and ensure that the process of issuing universal reputation is fair and neutral. Any user with a .bit or ENS account can quickly and freely introduce their own community on SoulFrag and design their own reputation system. These reputations can also be read and used by other applications (such as Voty).\n\nOne of the most considered and discussed issues in some community-related management tools in the past is the question of \"social or code\". For example, there are communities that deem only on-chain voting is effective. When designing SoulFrag, we hope to design a strata reputation suite. Anyone can simply map different reputation types to a piece of code on a decentralized storage facility, and contribute to the community in daily community activities Reputation distribution by members is no longer entangled in whether it should be on-chain or not, whether it is code-based or social-based.\n\nIn fact, we believe that among the many community tools, there are still too few tools that can be trusted and neutral. Few tools can implement the consensus and rules in the community to the code level. We hope to start from SoulFrag and start to code and trace personal reputation. When the reputation in SoulFrag is distributed, it can also be designed in the form of multi-signature distribution to ensure the decentralization of reputation distribution rights.\n\nBased on the above considerations, all SoulFrag data will be stored on Arweave (a permanent decentralized storage network).", "lastUpdated": 0, "projectGithub": "DIDHQ/soulfrag", "projectTwitter": "soulfraghq"}, "recipient": "0xa9E1BAE837d0D3b5879a69550d7C387Ce57aD753"}}