Open ck-convex opened 1 year ago
gitcoinbot
commented
1 year ago Issue Status: 1. Open 2. Started 3. Submitted 4. Done
The funding of 4000.0 USDC (4000.0 USD @ $1.0/USDC) attached to this issue has been cancelled by the bounty submitter
gitcoinbot
commented
1 year ago Issue Status: 1. Open 2. Started 3. Submitted 4. Done
Work has been started.
These users each claimed they can complete the work by an hour from now. Please review their action plans below:
1) hauwarh has started work.
I plan on collecting interesting datasets that focuses on assets, addresses, contracts, and transactions on the Ethereum using tools such as Dune Analytics, Forta, or Python, etc. 2) mohd-taqiuddin has started work.
I will collect data from Dune Analytics, save the datasets in a csv file, and upload all the datasets on GitHub. I have written a script to query the data from dune analytics, clean the queried data, and save it in a csv file. I will also collect data from other platforms and tools like forta. 3) abmtf has started work.
Inspiration Till now, BUIDL is not only a crypto meme that calls on people for building the blockchain and cryptocurrency ecosystem instead of passively holding, but also a future of work in the web3 world where people invest their time, money, efforts, and expertise to exchange for ownership or a piece of project or business in remote, permissionless collaboration and thus build their careers like portfolio managers.
As in the traditional business world, credit and reputation are still the cornerstones of web3 BUIDL, and more importantly. The reputation and its evaluation systems of web3 BUIDL help recognize and incentivize participants' contributions, which is crucial to the growth and sustainability of any web3 project or product. And we can see such examples of reputation systems as points, levels, titles, badges, certificates, and social tokens.
Nonetheless, there are problems existing in current reputation systems such as arbitrariness, inaccuracy, silo and fragmentation in the record, difficulties in verification and authentication, achievements that are easy to be falsified, modified, and removed by third parties, and reputation damage from the direct tokenization happened in some social tokens.
Proof of BUIDL Protocol or POB Protocol aims to provide an effective solution to those problems listed above.
What it does The POB Protocol is defined to be a decentralized workflow protocol for web3 BUIDL by which users issue, claim, submit, and verify tasks through smart contract and validator network and all data is stored on public blockchains and decentralized storage networks. Each workflow supports the Soulbound Token as BUIDL-based verification, which constitutes a verifiable reputation system.
How we built it The POB Protocol implements a Decentralized Verifiable Reputation Protocol, which enables users to acquire a web3 BUIDL reputation by participating in verifiable workflows without having to accumulate their reputation from any centralized and siloed infrastructure.
The POB Protocol can be divided into a stack of distinct interoperable layers as shown in Figure.
pob-stack-v2.png
Consensus Layer The POB Protocol has several components which require a blockchain-based consensus layer to provide guarantees that mechanisms in the protocol (validation, payment, voting, etc.) are immutable, irreversible, and can be carried out without the help of a central governing authority. We will use an existing EVM-compatible blockchain such as Ethereum, or Polygon for this purpose.
Storage Layer Other than core assets and states in smart contracts, the POB protocol stores data such as user submissions, workflow profiles, and other data on decentralized content-addressable networks such as IPFS or Arweave for permanent data storage.
Validator Network The network is grouped according to the type of task requested by the reviewer, with each group consisting of a number of validator nodes, each node providing the same functionality and specifications. When a task triggers the validator network to provide a service, the node will sign the result data according to the service content and then upload it to the data center. Within a certain period of time, the validator network gets the data from the data center and calculates the final data based on rule aggregation (BFT, or Byzantine fault tolerance). If the user has authorized the validator network, then the network will automatically authorize or deny based on the results. If not authorized, the user can get the reference data from the POB backend.
Validator requires to stake $POB, the native token of POB Protocol, to join the network and will be rewarded or slashed by the system based on its own validation performance.
Contract Factory The POB protocol uses a specifically designed Contract Factory to process workflows consisting of single and multiple tasks created by the protocol participants involved on-chain, combined with the work of the validator network to produce Incentive Token and Reputation Credentials as incentives and reputation validation.
Factory Contract - the decentralized workflows implemented by the POB protocol require using multiple smart contracts with similar functionality but different data, with factory contracts acting as units dedicated to producing contracts to represent and implement their workflow instances. Task - the basic unit that executes the workflow. The task can be created by all protocol participants, and the taker can only submit content on the task. The task contains information about the reviewer, the taker, and the flowing states. Workflow - a set of tasks that represent workflow instances and store some core rules data. Workflow is created and approved by the issuer, claimed, and minted soulbound token by the taker. Incentive Token - The POB protocol supports the protocol native token $POB, stablecoins such as USDT/USDC/DAI, and other ERC20 tokens as incentive tokens for accomplishing workflows. Reputation Credentials - The POB protocol enables takers to mint soulbound token as their reputation credentials for accomplishing workflows since reputation results from the social evaluation of a set of behavior or performance of a social entity by the counterpart. Marketplace The decentralized marketplace supported by the POB Protocol not only enables users to pay to use workflow templates developed by the protocol but also enables community developers to create task templates and workflow templates applied to different specific needs and scenarios for others to pay to use in order to prosper the protocol ecosystem.
Workflow Template - it is a mandatory option when creating a workflow, and it represents a specific application scenario for a workflow that users can get from open API or SDK powered by the POB Protocol in the marketplace. Task Template - user needs to select the task template when creating a workflow, which represents the type of tasks supported and which users can get from open API or SDK powered by the POB Protocol in the marketplace. DApp Store The POB protocol supports a wide range of use cases (described below) and encourages community developers to build DApps for a variety of different needs and scenarios using the combination of capabilities and markets provided by the protocol.
Participants There are four different roles of protocol participants as follows:
Builder - the participant who creates task templates and workflow templates for the Issuer to use, and provides the corresponding validation services for the task if needed. Issuer - the participant who publishes the workflow. The issuer requires to configure the workflow information and task information. Taker - the participant who claims the workflow. Only the taker can claim the workflow and submit the task. Reviewer - a participant who reviews and approves a workflow, either by the issuer or by a third party designated by the issuer. The reviewer can request verification from the validator network. Challenges we ran into We found that web3 projects have a trust issue when working with people, capital, and other projects and ecosystems. Especially when the way of our work became remote and decentralized, the trust and reputation between projects and people became an obstacle to reaching a truly permissionless build.
Most of the existing solutions are oriented toward recording the results of the user's completed work. On the one hand, there is no way to verify the quality and status of the user's completed work, and on the other hand, there is a lot of uncertainty about the reputation of the issuer of the results, which leads to no standardized way to verify the user's reputation.
Accomplishments that we're proud of We have finished developing a fully decentralized workflow protocol that can support almost all use cases from the architecture level, making the POB Protocol applicable to a variety of scenarios.
After the first MVP was developed, we immediately introduced our product to the outside world and were recognized by many customers, which also strengthened our idea that the POB Protocol is an indispensable cornerstone to support the building of the web3 reputation system and even the evolution of the web3 ecosystem.
At this stage, we have already applied the POB Protocol to some products, such as MetaJam Quest, and the DAO community's collaboration.
What we learned We put a lot of effort into pre-product design, which has helped us a lot in product development. The extensive design and verification made the protocol architecture more flexible and reduced rework.
We also learned a lot from the customer surveys. For example, the recruitment workflow was inspired by the prospective client to refine a more compatible recruitment workflow template from a real-world use case. This case made us realize that it's time to talk to more customers about cooperation.
What's next for POB Protocol After the initial design of POB Protocol architecture, we need to standardize, specify and quantify the definition of reputation, and hope to find a standardized solution for defining reputation through contact with different types of customers and demand exploration. Futhermore, we hope to support more scenarios, each of which has its own unique process and implementation method. In the process of communicating with different projects and builders, we will build more workflow templates based on POB Protocol to meet the needs of different projects and builders, increase the success rate of demand matching, and build the reputation of projects and individuals while making profits. 4) giraffekey has started work.
Data collection of NFT threat detection alerts using smart contract events and Forta API. 5) nahnoneee has started work.
I WILL COLLECT DATAS ABOUT SECURITY OF ETHEREUM NETWORK 6) fibrinlab has started work.
I will collect data from ethereum 7) hosseinghodrati has started work.
This project is based on the goal of compliance and authenticity of Ethereum transactions . 8) pfed-prog has started work.
Data Collection 9) tf0rs has started work.
Collecting data from Forta, Etherscan, Chainabuse, and Dune to analyze ice phishing activity. 10) tanas0 has started work.
This is a script to build a dataset based on the suspicious list of domains related to scamming (by ScanSniffer). The data currently collected is: IP addresses, text contents and most common words. Other interesting data could be: social medial links, emails, wallet addresses, hosting provider and domain name registrar... This data can be used to categorise scams (NFTs, ICOs, Fake Exchanges, donation campaign, airdrop, seed phrase theft...)
Please refer to the project's README for further details 11) denz-e has started work.
A proof-of-concept of how we can create a comprehensive dashboard tracking all NFT phishing scams. 7 events of differing severity and nature are included.
Learn more on the Gitcoin Issue Details page.
gitcoinbot
commented
1 year ago Issue Status: 1. Open 2. Started 3. Submitted 4. Done
Work for 4000.0 USDC (4000.0 USD @ $1.0/USDC) has been submitted by:
@ck-convex please take a look at the submitted work:
gitcoinbot
commented
1 year ago Issue Status: 1. Open 2. Started 3. Submitted 4. Done
The funding of 4000.0 USDC (4000.00 USD @ $1.0/USDC) attached to this issue has been approved & issued to @giraffekey.
Prize Title
Ethereum Data Collection Bounty
Prize Bounty
1st - 2250 USDC & 1 Vigilante NFT
2nd - 1250 USDC
3rd - 500 USDC
Challenge Description
In this bounty, participants will be tasked with collecting interesting datasets using tools such as Dune Analytics, Forta, Python, etc. Datasets should focus on assets, addresses, contracts, and transactions on the Ethereum blockchain. Although, data type and methodology are up to the participant, data collection should be focused in 3 areas: security, compliance, and authenticity.
For security, think stolen NFTs, phishing, malware, etc.
For compliance, think AML, sanctions, etc.
For authenticity, think copycat NFTs, copycat tokens, DID, etc.
Submission Requirements
Data collection can be done using the participant’s choice of tool. However, the data collection logic must be included along with the results to qualify. A description of the data collection process should also be included. Participants are encouraged to collect data on as many assets, addresses, contracts, and transactions as feasible to increase coverage.
Data can be submitted via Github, Dune, or any public platform. We will not open any unknown links or attachments.
Submissions not focused on security, compliance, or authenticity will be disregarded.
Participants are allowed unlimited submissions. Each submission will be counted individually and participants are eligible to win multiple prizes.
Judging Criteria
Submissions will be judged on the following criteria; however, judges will use their discretion in choosing winners:
Relevancy: Is the dataset relevant to the categories of security, compliance, and authenticity?
Quality of the data: Is the collected data accurate? Was the description clear?
Uniqueness of data: Did other participants submit similar datasets?
Coverage: How many assets, addresses, or contracts were covered?
Winner Announcement Date
Winners will be announced by October 6th, 2022.
Resources
Questions?
https://discord.gg/VcxcmvWbg6
Honest Protocol Resources
https://twitter.com/Honest_Protocol
https://www.honestprotocol.xyz
https://medium.com/@convexlab
Dune Resources
https://dune.com/browse/dashboards
https://discord.gg/UQZudmeg4F
Forta Resources
https://forta.org/ discord.gg/AA9kPUXExk