- Council/
- Motions/
- 232/
#232·Treasury Proposal: Anti-Scam Bounty Top-up
- Content
- AI Summary
I am opening a proposal at the request of the Anti-scan Bounty Curation team to top-up their bounties in order to continue with their initiative for the months to come, after the test period. Reasoning behind the proposal, along with budget, a report on all child-bounties opened and roadmap can be found on their post below.
Link to the original discussion post: here.
With this proposal we request a top-up to the Anti-Scam Bounty to continue funding the community initiatives that aim to protect users in our ecosystem from falling victim to scams.
The bounty expanded on the previous community initiative targeting scam sites that was ongoing for several months, by adding new tasks that aim to create a holistic solution that addresses the problem from several aspects, while bringing awareness to the community, and educating users of both the problems and the efforts to address them.
The Task to find and take down scam sites is still the flagship of the bounty, taking the lion's share of the rewards, but several others of the tasks are being worked on with good progress and we aim to have all of them completed/active by the end of September 2022.
All the details of the proposal, along with spending analysis, can be found HERE.
PLEASE NOTE YOU WILL NOT BE ABLE TO SEE THE BENEFICIARY IDENTITY ON-CHAIN (this is the address of the bounty, created once the bounty proposal is accepted) BUT YOU WILL BE ABLE TO CHECK THIS ON SUBSCAN.
- The Anti-scam Bounty Curation team is requesting more money to continue their initiative to protect users from scams.
- The bounty has tasks to find and take down scam sites, as well as educate the community about the problem.
- The team aims to complete all the tasks by the end of September 2022.
- More details about the proposal and spending can be found in the provided link.
- The beneficiary identity cannot be seen on-chain, but can be checked on Subscan.
- Business
- Call
- Metadata
- Timeline9
Cross-posting from Polkassembly for visibility:
Since it may not be immediately clear why this account:
13UVJyLnbVp9RBZYFwHYxa6GPKJ2SqkGg4Mo7jG7uLAbPkT8
is the beneficiary of this proposal, I thought to clarify it a bit.
This is a bounty account, as denoted by its identity
modlpy/trsrybt. The identity doesn't specify for which bounty is this account, so one needs to examine the extrinsics to determine this is indeed the account of the Anti-Scam Bounty.Each extrinsic of the account creates a new child bounty and transfers the value to a (new) child bounty account. From there the value of the child bounty is transferred to the implementer and the curator (if the fee is not zero), when it is claimed, 8 days after it has been awarded by the curator.
For example, this extrinsic created a new child bounty, as shown in this event, and transferred to the new child bounty account the amount of 100.17 DOT, which was the total value of child bounty 19, as seen here.
Then the child bounty was claimed in this extrinsic and the balance of the child bounty account was divided between the implementer and the curator, according to the value set when it was created and the fee that was set for the curator when they were proposed.
In a similar way, one can verify the rest of the extrinsics and cross-check them against the ones posted in the Anti-Scam Bounty comments.