Prosper (@prosperfi_xyz): This article is meant to provide some clarifications regarding our recent airdrop campaign. The technical issue with our API at the verification time…

This article is meant to provide some clarifications regarding our recent airdrop campaign. The technical issue with our API at the verification time of final tasks, combined with the nuances in task requirement and reward claiming, added a lot of friction to the overall experience for all participants and even including winners—for which the team would like to apologize for the inconveniences caused to all the participants The community’s feedback is well noted for future campaigns—there is always room for us to improve and do better. Just to clarify, the total $300k prize pool in the Binance Wallet campaign can all be claimed normally by users (if you won a quota) on the Wallet app’s campaign page—those rewards are not manually distributed by the Prosper team. Before we finish this chapter and return to building Prosper, our priorities are: 1/ ensuring normal winners can claim their rewards; 2/ finalizing a remediation plan for relevant users affected by technical issues. 1/ Ensuring normal winners claim their rewards (from the reward pool as provided in the original campaign structure) First off, we have included below the lists of winning wallet addresses for each first-come first-served (FCFS) mission (users whose address are not on these lists but believe they have been affected by technical issue please read on to section 2) PancakeSwap (3,000 FCFS quota): link (https://docs.google.com/spreadsheets/d/1X0xID-_1oTq1n_wlhqfdKdO2fwu1gmAag3XeRMVnJdY/edit?gid=1429839358#gid=1429839358) Prosper dApp (3,000 FCFS quota): link (https://docs.google.com/spreadsheets/d/1X0xID-_1oTq1n_wlhqfdKdO2fwu1gmAag3XeRMVnJdY/edit?gid=0#gid=0) All-task completion (3,000 FCFS quota): link (https://docs.google.com/spreadsheets/d/1X0xID-_1oTq1n_wlhqfdKdO2fwu1gmAag3XeRMVnJdY/edit?gid=1329526398#gid=1329526398) Based on our checking so far - list of addresses that won at least one of the quotas above but still haven’t claimed their rewards: link (https://docs.google.com/spreadsheets/d/1X0xID-_1oTq1n_wlhqfdKdO2fwu1gmAag3XeRMVnJdY/edit?gid=205829365#gid=205829365) (non-exhaustive, will add to it as we discover more; may also not be updated after users have claimed) Second, we want to do a recap of the original campaign reward structure to clarify some ground rules (which was announced on our official X handle and on Binance Wallet’s campaign page at the start of the campaign). 🖼️ https://pbs.twimg.com/media/Gf-8rsUX0AA5DW1.jpg (As published on our campaign Notion page at campaign start + available from Binance Wallet app: https://prosper-fi.notion.site/binance-wallet-campaign) The table above summarizes all the types of prizes & number of quotas for each (all clearly stated at the start of the campaign). All missions have a cap on the number of winners—and with the exception of the first mission, all other missions are on a FCFS basis. A few important clarifications on the baselines: For the first mission: it’s a “chance to win” amongst all completed entries and the winner selection has been completed by the time of this article’s publishing. Users can check if they have won on their Binance Wallet campaign page For the FCFS missions: if you did not attempt to verify the completion of missions within the first couple of hours of 25 Dec 23:59 UTC, based on our records, you wouldn’t have been able to make it into the first 3,000 quotas We want to clarify this point because there’s an increasing number of inbound enquiries by users under the false impression that reward quotas are unlimited as long as they have completed their tasks For the FCFS missions: the set of winners for each mission can be different, i.e. you can be one of the 3,000 winners of mission 2 (task 4,5,6) but not the first 3,000 winners of mission 3 (task 7,8). So simply because you verified and claimed reward for say mission 2, this in itself does not automatically guarantee you a quota for the reward of mission 3 This was by design initially to create a bit more competitive tension amongst participants and allow more than 3,000 people to receive rewards—in hindsight, this might be something worth revisiting in future campaigns considering the potential confusion it might create 2/ Finalizing a remediation plan for relevant users affected by technical issues Context: What happened is that at / around 25 Dec 23:59 UTC, i.e., the earliest time a user could verify the completion of the staking mission (and by extension, claim the corresponding FCFS rewards), the sudden influx of traffic and requests temporarily overloaded our API throughput, and multiple users ran into errors when trying to verify mission completion on their Binance Wallet campaign page. (The liquidity mission, which also started verification at the same time, relied on a different API service provider and had been functioning normally) Understandably, users were keen to verify ASAP and many users made repeated attempts (i.e., “just keep clicking”) within a short period of time; immediately, the team worked on increasing the throughput with our API service provider, and we expanded the bandwidth roughly 70 minutes later, at which point a large group of users who had continued their attempts to verify throughout that period got through all at once—as a result it appeared that the “winning quota” for staking mission was all gone in a second. What we are trying to “remediate” for: While the nature of the campaign reward was always competitive / FCFS by design, we are fully empathetic of situations where users simply do not have a fair chance to compete for the chance to win, e.g., one of the most common cases we have received so far is: user made a few attempts right on the mark of 25 Dec 23:59 UTC, but seeing an error message, temporarily stopped their attempts to verify, and came back in a few hours realizing that all “winning quota” was gone. In the particular example above, if there wasn’t any technical issue in the first place, that user would have had their fair shot at being one of the 3,000 FCFS winners. Cases along the same spirit or principle would be what we consider as “situations where users didn’t get a fair chance” to compete for rewards due to technical issues on our end. And this group of genuinely affected users would be the primary focus of our upcoming remediation plan (i.e., compensation beyond the original prize pool of the campaign), which the team felt responsible to make things right for our affected community. **Important to note that submitting our previously shared Google form DOES NOT in itself qualify you to receive reward under the remediation plan. Our intention is to do a targeted remediation for addresses fitting the criteria based on verifiable data since all actions or attempts would have created either on-chain record or interaction on our logs—if you are aware that you didn’t do the task at all, or were simply too late to verify / claim, we would suggest not to file a case just to try your luck, as these would be easily weeded out and would not be a good use of your time. Remediation qualifying criteria & addresses: Disclaimer: while the team continues to do our best to identify all potentially affected wallets, given the sheer volume of enquiries, it is possible that we may have missed some edge cases. We ask for your understanding as this remediation plan is purely on a voluntary and best-effort basis (beyond what we have already distributed in prize pool as stipulated in the original campaign). It is also unrealistic to expect us to pay anyone and everyone who comes asking. A compilation of data was used as part of the review process, including user submissions from the Google form, data from the Binance Wallet team, relevant on-chain data, as well as task verification API interaction logs Reviewed over 1k valid form submissions + 3.5k addresses that had attempted to verify the “maintain staking” task within the first 2 hours of being able to do so (25 Dec 23:59 UTC - 26 Dec 02:00 UTC) Ended up with 558 qualifying addresses after review and analysis, taking into account various factors, including but not limited to: - On-chain reward claiming activity - Reward allocation data from Binance Wallet team - Task completion / fulfillment of task requirements (e.g., the “maintain staking” task) - Time of first attempt to verify “maintain staking” task Key qualifying criteria: - The wallet has fulfilled requirements of the “maintain staking” task (based on on-chain data and campaign rules); AND - Has made first attempt to verify the “maintain staking” task within first 2 hours of verification time (based on our task verification API interaction logs) - Note: Just to re-iterate this is not meant to be a handout for everyone—you would not qualify for remediation if you plainly did not do the task or did not attempt to verify within first 2 hours (a timeframe that one can reasonably expect to have a chance to win—as a matter of fact, the quota of 3k winners was filled within the first 90 minutes) Remediation award tiering: Tier 1 (347 addresses) This group potentially missed out on the staking tasks reward and a chance to compete for the all tasks completion reward Address profiles: - Completed PancakeSwap (PCS) tasks - meaning that if they could have verified maintain staking smoothly, could potentially have had a chance to win both staking tasks reward & all tasks completion reward - Note that winning PCS reward quota or not is irrelevant to the chance of competing for all tasks completion reward (condition to compete for all tasks completion reward is based on VERIFYING ALL TASKS, not getting reward quota for all other tasks) Remediation amount (preliminary—to be finalized by Tuesday): - Full amount of staking reward value: $9 in USDT AND - Discounted amount of all tasks completion reward value: $10 in USDT in the end, the reward quota was designed to be competitive and FCFS—hence, this is meant to be adjusted by possibility of winning) - So, $19 in USDT in total Tier 2 (211 addresses) This group potentially missed out on only the staking tasks reward because of technical issue (note that PCS tasks had no technical issue) Address profiles: - Received all tasks completion reward quota but not staking task reward quota - Received both PCS & all tasks completion reward quota but not staking task reward quota - Didn’t complete PCS tasks (PCS task verification had no technical issue) - this means that with or without staking technical issue, these wallets wouldn’t have had a chance to win all tasks completion reward quota; hence, potentially missing out on staking reward quota only Remediation amount (preliminary—to be finalized by Tuesday): - Full amount of staking reward value: $9 in USDT List of wallet addresses for community to check if they qualify: Tier 1: to be finalized by Tuesday Tier 2: to be finalized by Tuesday What will happen next: Now until Tuesday: Team is continuing to review and refine the tentative list of qualifying addresses Tuesday: announce finalized remediation plan & qualifying criteria / list of addresses 30 Dec update: preliminary criteria for qualifying addresses shared above, to finalize by Tuesday Friday (3 Jan): airdrop remediation amount to qualifying addresses