{"signature": "0x610f2aba50c649b9eb432251ae54885636fc7c25eb6a3b96c1c78030a9269e536d509da5ad9f1e5112bf13b55ae6fca3c08442597e4b54b47e80ebe3bea407421b", "application": {"round": "0xb91b59c91b09d127d269e53019f2420e8c2c7ce7", "answers": [{"type": "email", "hidden": true, "question": "Email Address", "questionId": 0, "encryptedAnswer": {"ciphertext": "ob+HIWqyL8MjW5h+MiK0N2VhzfSG0pov7Z4hv1lgaHl0EnMEGvmMyDlLJhtOAhdH", "encryptedSymmetricKey": "aa79bf795d423f4eab045bb205b699e00518d33bf774304d3cdc20e55f97415d809fc8054ef0903f0c4acfd8ecc0710b5e507698672ac234d7c982b7b432a6264e5ea8e537faa95d4599fa7c457a199f2715ffae14c4ffb17a84e2256e8c6e915270f08d6440fb3cbc7a55fd4ca6cb4e370060550fd7fb4c16d6f1425a47988000000000000000205013bf46bd9472274689def7bce50305d492dab557d322b4d0203c9ef3fa54acea5e79a9e6eca45a1fe2e602363a13a8"}}, {"type": "short-answer", "answer": "@estebanabaroa", "hidden": true, "question": "Telegram Handle", "questionId": 1}, {"type": "short-answer", "answer": "https://github.com/plebbit", "hidden": true, "question": "Project GitHub Repo", "questionId": 2}, {"type": "short-answer", "answer": "https://t.me/plebbit", "hidden": true, "question": "Link to your Public Group Chat", "questionId": 3}, {"type": "short-answer", "hidden": true, "question": "Have you participated in a previous Gitcoin Grants Round? If so, please name the rounds or link the builder profile associated with previous rounds.", "questionId": 4}, {"type": "paragraph", "answer": "Key Aspects:\n\n    Decentralized Architecture\n\n    Built on IPFS (InterPlanetary File System)\n    Uses peer-to-peer networking principles\n    Provides an alternative to centralized social media platforms\n\n    Open Source Development\n\n    Core codebase is open source and available on GitHub\n    Allows developers to audit, contribute, and fork the project\n    Encourages transparency and community involvement\n\n    Technical Innovations\n\n    Implementation of decentralized moderation systems\n    Development of peer-to-peer content distribution methods\n    Creation of cryptographic verification systems for posts and comments\n\n    Educational\n\n    Serves as a reference implementation for decentralized social media\n    Demonstrates practical applications of blockchain and P2P technologies\n    Provides learning opportunities for developers interested in decentralized systems\n\n    Community Tools\n\n    Development of APIs and tools for building on top of the platform\n    Creation of libraries and SDKs for integration\n    Documentation and resources for developers\n", "hidden": true, "question": "How does your project contribute to the growth of the OSS ecosystem? Please provide specific examples of how your application enhances or expands the current ecosystem.", "questionId": 5}, {"type": "paragraph", "answer": "Based on available information, here are the key features and differentiators of Plebbit:\n\nCore Features:\n\n    Decentralized Infrastructure\n\n    No central servers or authority\n    Content stored across IPFS network\n    Resistant to censorship and takedowns\n    No single point of failure\n\n    Privacy-Focused\n\n    No account registration required\n    Optional anonymity\n    Encrypted communications\n    No tracking or data collection\n\n    Moderation System\n\n    Community-based moderation\n    Subplebbits (similar to subreddits) can set their own rules\n    Cryptographic verification of moderator actions\n    Ability to fork communities if disagreements arise\n\nKey\n\n    Technical Architecture\n\n    Built on IPFS vs traditional client-server model\n    True peer-to-peer content distribution\n    No reliance on centralized infrastructure\n\n    Governance Model\n\n    No corporate ownership\n    Community-driven development\n    Open source and transparent\n\n    Economic Model\n\n    No advertisements\n    No user data monetization\n    Optional cryptocurrency integration\n    Sustainable through community support\n\nUse Cases:\n\n    Communities requiring censorship resistance\n    Privacy-conscious users\n    Decentralized content sharing\n    Alternative social media platform\n    Technical demonstrations of P2P systems\n\nLimitations/Challenges:\n\n    Earlier stage of development\n    Smaller user base compared to centralized alternatives\n    Technical complexity for average\n    Network effects challenges\n", "hidden": true, "question": "What features or use cases does your dApp/App present? How is it differentiated?", "questionId": 6}, {"type": "paragraph", "answer": "Based on my analysis, here are potential development priorities and funding allocations that could benefit Plebbit's ecosystem:\n\nSuggested Development Priorities:\n\n    Core Infrastructure\n\n    Improve network stability and scalability\n    Enhance content distribution efficiency\n    Strengthen security measures\n    Optimize IPFS integration\n    Develop better data persistence solutions\n\n    User Experience\n\n    Create more user-friendly interfaces\n    Develop mobile applications\n    Improve onboarding process\n    Add support for rich media content\n    Enhance community management tools\n\n    Developer Tools\n\n    Build comprehensive SDK\n    Improve API documentation\n    Create development templates\n    Provide testingd integration tools\n\nSuggested Grant Fund Allocation:\n\n    Technical Development (40%)\n\n    Core protocol development\n    Security audits\n    Performance optimization\n    Infrastructure scaling\n\n    User Interface/Experience (25%)\n\n    Client applications\n    Mobile development\n    Design improvements\n    Accessibility features\n\n    Community & Documentation (15%)\n\n    Technical documentation\n    User guides\n    Community management\n    Educational resources\n\n    Testing & Quality Assurance (10%)\n\n    Security testing\n    Performance testing\n    User testing\n    Bug bounties\n\n    Research & Innovation (10%)\n\n    Protocol improvements\n    New feature research\n    Scalability solutions\n    Integration possibilities\n\nKey Milestones:\n\n    Short-term (3-6 months)\n\n    Stable core protocol\n    Basic client\n    Improved documentation\n    Essential developer tools\n\n    Medium-term (6-12 months)\n\n    Enhanced feature set\n    Mobile app releases\n    Advanced moderation tools\n    Expanded API capabilities\n\n    Long-term (12+ months)\n\n    Full ecosystem development\n    Enterprise integration options\n    Advanced scaling solutions\n    Innovation initiatives\n\nSuccess Metrics:\n\n    Technical\n\n    Network stability\n    Response times\n    Storage efficiency\n    Security incidents\n\n    Adoption\n\n    Active users\n    Content creation\n    Developer participation\n    Community growth\n\n    Development\n\n    Code quality\n    Documentation coverage\n    Bug resolution\n    Feature completion\n\nGovernance & Oversight:\n\n    Regular progress feedback integration\n    Transparent fund allocation\n    Regular security audits\n    Open development process", "hidden": true, "question": "What are your plans for further development, and how will the grant funds be used to achieve these goals?", "questionId": 7}, {"type": "paragraph", "hidden": true, "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": 8}], "project": {"id": "0xd77bec3500a1b3e54ead391aeaad9a664f92643beaa8a50d4302bd67ef7949cf", "title": "Plebbit", "logoImg": "bafkreifvkkfu3do7o2wawba3my7rirune5yeyait44nv2hwqothv4uwjne", "metaPtr": {"pointer": "bafkreieddstoxh2kqbj2kk3zqehbnb4fcwycoue3xxghsqd6rta5st6bwy", "protocol": "undefined"}, "website": "https://plebbit.com", "createdAt": 1718559288527, "userGithub": "rinse12", "credentials": {"github": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..nGsFqY3Ebwcy7KM9uV6EMrLqcpZ-KtojQah-mYrcp1ilzrAjAFe-EH2zSTRDVKcK8SF3fgrmElurF0DSGA5IBw", "type": "Ed25519Signature2018", "created": "2024-10-23T15:46:13.225Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2024-10-23T15:46:13.225Z", "expirationDate": "2025-01-21T15:46:13.225Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xCed7E65e1da560bbdA16D308A63D12f91A4ca6B2", "hash": "v0.0.0:W+gqblm5KduyvVTbXMopqOMxTpC8Lvxu+sDW7N5QJ6s=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextGithubOrg#plebbit#98007027"}}, "twitter": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..zQGE0g6bpjnjUVhEHQWVLPgZr2VdGxaIm0MOeUnHu9eRa_nqt6ChLDd5S-5uOuMX3-Ygdo2Y2Fi_Xd88W9z0CQ", "type": "Ed25519Signature2018", "created": "2024-10-23T15:45:54.077Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2024-10-23T15:45:54.077Z", "expirationDate": "2025-01-21T15:45:54.077Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xCed7E65e1da560bbdA16D308A63D12f91A4ca6B2", "hash": "v0.0.0:6IyKMzPPSk3nnVB6MegFtMyAPjINWA/ypy1GtA66vww=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextTwitter#getplebbit"}}}, "description": "Plebbit is a protocol and tooling for creating decentralized forum applications like Reddit, Facebook groups, Discourse, etc. It's a pure P2P protocol, it doesn't use any central server, databases, public HTTP end point, DNS, etc. It uses parts of the IPFS and Ethereum stack to create everything it needs:\n\nIPFS for immutable data, like a published comment or a recent subplebbit page.\n\nIPNS for mutable data, like replies to a comment, upvote counts, new posts/comments published on a subplebbit, etc.\n\nIPFS pubsub for authors publishing comments/votes to a subplebbit and for the captcha challenge exchange between authors and subplebbits.\n\nENS for usernames, community names, and serving the client in browsers.\n\nScalability and fees\n\nA decentralized social media/forum has 2 problems: How to store the entire world's data on a blockchain, and how to prevent spam while being feeless. We propose solving the data problem by not using a blockchain for content, but rather IPNS and IPFS pubsub. Unlike cryptocurrencies that must know the order of each transaction to prevent double spends, social media does not care about the order of posts, nor about the availability of old posts.\n\nNote that we must still use a blockchain (ENS) for usernames and community names because those do care about doublespends and ledger history availability.\n\nIPNS\n\nThe IPNS name (also ENS name) is the name and address of the subplebbit, e.g. \"memes.eth\".\n\nPubsub\n\nTo publish a post to a subplebbit, a user would publish a pubsub message with a \"topic\" equal to the subplebbit's ENS name. This allows the subplebbit owner to reply with \"challenge\" and \"challengeverification\" messages signed with his ENS' public key that all pubsub peers can verify.\n\nCaptcha service over pubsub\n\nNondeterministic pubsub (like user generated comments) is susceptible to spam attacks that would DDOS it, as well as makes it impossible for moderators to manually moderate an infinite amount of bot spam. We solve this problem by requiring publishers to first request a captcha challenge from the subplebbit owner's peer. If a peer or IP address relays too many captcha challenge requests without providing enough correct captcha challenge answers, it gets blocked from the pubsub. This requires the subplebbit owner's peer to broadcast the result of all captcha challenge answers, and for each peer to keep this information for some time.\n\nNote: The challenge implementation is completely up to the subplebbit owner. He can decide to prompt all users, first time users only, or no users at all. He can proxy 3rd party services like Google captchas. He can use other challenge types, like a proof of stake/holding/payment of a certain token, a whitelist, invite list, etc.\n\nLifecycle of creating a subplebbit\n\nSubplebbit owner starts a Plebbit client \"node\" on his desktop or server. It must be always online to serve content to his users.\n\nHe generates an IPNS public key, and adds it as a TXT record to his ENS name, which will be the \"address\" of his subplebbit.\n\nHe configures captcha options, like how often and what kind of captchas to show.\n\nHe publishes the metadata of his subplebbit to his IPNS record. This includes subpebblit title, description, rules, list of public keys of moderators, etc.\n\nLifecycle of reading the latest posts on a subplebbit\n\nUser opens the Plebbit app in a browser or desktop client, and sees an interface similar to Reddit.\n\nHis client joins the public key addressing network as a peer and makes a DHT query for each address of each subplebbit he is a member of. The queries each take several seconds but can be performed concurrently.\n\nThe query returns the latest posts of each subplebbit, as well as their metadata such as title, description, moderator list and captcha server URL.\n\nHis client arranges the content received in an interface similar to Reddit.\n\nLifecycle of publishing a post on a subplebbit\n\nUser opens the Plebbit app in a browser or desktop client, and sees an interface similar to Reddit.\n\nThe app automatically generates a public key pair if the user doesn't already have one.\n\nHe publishes a cat post for a subplebbit called \"cats.eth\"\n\nHis client joins the pubsub network for \"cats.eth\"\n\nHis client makes a request for a captcha challenge over pubsub.\n\nHis client receives a captcha challenge over pubsub (relayed from the subplebbit owner's peer).\n\nThe app displays the captcha challenge to the user in an iframe.\n\nThe user completes the captcha challenge and publishes his post and captcha challenge answer over pubsub.\n\nThe subplebbit owner's client gets notified that the user published to his pubsub, the post is not ignored because it contains a correct captcha challenge answer.\n\nThe subplebbit owner's client publishes a message over pubsub indicating that the captcha answer is correct or incorrect. Peers relaying too many messages with incorrect or no captcha answers get blocked to avoid DDOS of the pubsub.\n\nThe subplebbit owner's client updates the content of his subplebbit's public key based addressing automatically.\n\nA few minutes later, each user reading the subplebbit receives the update in their app.\n\nIf the user's post violates the subplebbit's rules, a moderator can delete it, using a similar process the user used to publish.\n\nWhat is a \"post\"\n\nA post is an IPFS file for its immutable content, like timestamp, title, author signature, etc. Each post's IPFS file also contains its own IPNS name which links to its mutable content, like its upvote count, replies, etc. Each post is part of a linked list, i.e. it points to the previous post's IPFS CID.\n\nWhat is a \"subplebbit\"\n\nA subplebbit is an IPNS record updated every 5 minutes, it contains the latest post's CID, the title, description, the CIDs of the latest post pages sorted by new, hot, top, etc. It also contains the pubsub \"topic\" address to publish to it. Full schema available at https://github.com/plebbit/plebbit-js#schema\n\nUsing anti-spam strategies other than the captcha service\n\nThe captcha service can be replaced by other \"anti-spam strategies\", such proof of balance of a certain cryptocurrency. For example, a subplebbit owner might require that posts be signed by users holding at least 1 ETH, or at least 1 token of his choice. Another strategy could be a proof of payment, each post must be accompanied by a minimum payment to the owner of the subplebbit. This might be fitting for celebrities wanting to use their subplebbit as a form of \"onlyfan\", where fans pay to interact with them. Both these scenarios would not eliminate spam, but they would bring them down from an infinite amount of spam, to an amount that does not overwhelm the pubsub, and that a group of human moderators can manage. Proof of balance/payment are deterministic so the pubsub can block spam attacks deterministically. Even more strategies can be added to fit the need of different communities if found, but at this time the captcha service remains the most versatile strategy.\n\nConclusion\n\nWe believe that the design above would solve the problems of a serverless, adminless decentralized Reddit alternative. It would allow unlimited amounts of subplebbits, users, posts, comments and votes. This is achieved by not caring about the order or availability of old data. It would allow users to post for free using an identical Reddit interface. It would allow subplebbit owners to moderate spam semi-automatically using their own captcha service over peer-to-peer pubsub. It would allow for all features that make Reddit addictive: upvotes, replies, notifications, awards, and a chance to make the \"front page\". Finally, it would allow the Plebbit client developers to serve an unlimited amount of users, without any server, legal, advertising or moderation infrastructure.\n\n", "lastUpdated": 0, "projectGithub": "plebbit", "projectTwitter": "getplebbit"}, "recipient": "0x5Bc4FF33f86E0272be53Fa25861294489AB2FE2a"}}