Add Bounty Context to Treasury Page

docs/learn/learn-guides-bounties.md

@@ -7,6 +7,8 @@ keyword: [treasury, bounties, guides, child bounty]
 slug: ../learn-guides-bounties
 ---
 
+import RPC from "./../../components/RPC-Connection";
+
 For these guides, you will use the [Polkadot-JS UI](https://polkadot.js.org/apps/#/explorer).
 
 :::info Notify the Polkadot Direction Channel
@@ -32,6 +34,16 @@ proposal as an OpenGov referendum, the bounty will show as "funded" at the end o
 [Bounties page](https://polkadot.js.org/apps/#/bounties). You can then proceed with assigning
 curators to the bounty.
 
+To minimize storage on chain in the same way as any proposal, bounties don't contain contextual
+information. When a user submits a bounty spending proposal, they will need to find an off-chain way
+to explain the proposal through for example [Polkassembly](https://polkadot.polkassembly.io/opengov)
+or [Subsquare](https://polkadot.subsquare.io/).
+[This template](https://docs.google.com/document/d/1-IBz_owspV5OcvezWXpksWDQReWowschD0TFuaVKKcU/edit?usp=sharing)
+can help as a checklist of all needed information for OpenGov voters to make an informed decision.
+
+Submitting a bounty proposal will reserve
+{{ polkadot: <RPC network="polkadot" path="consts.bounties.bountyDepositBase" defaultValue={10000000000} filter="humanReadable"/> :polkadot }}{{ kusama: <RPC network="kusama" path="consts.bounties.bountyDepositBase" defaultValue={33333333300} filter="humanReadable"/> :kusama }}.
+
 ## Assign a Curator to a Bounty
 
 Once your bounty is shown as "funded" on the main
@@ -80,7 +92,8 @@ bounty 17 refers to the Community Events Bounty, which has 183 child bounties.
 
 ![polkassembly-child-bounties](../assets/polkassembly-child-bounties.png)
 
-After a child bounty has been awarded and the {{ polkadot: 8 :polkadot }}{{ kusama: 4 :kusama }}-day
+After a child bounty has been awarded and the
+{{ polkadot: <RPC network="polkadot" path="consts.bounties.bountyDepositPayoutDelay" defaultValue={115200} filter="blocksToDays"/> :polkadot }}{{ kusama: <RPC network="kusama" path="consts.bounties.bountyDepositPayoutDelay" defaultValue={57600} filter="blocksToDays"/> :kusama }}-day
 delay elapsed, follow the guidelines in the video tutorial below to learn how to claim a child
 bounty reward. Note that the extrinsic to claim the child bounty reward is permissionless, and
 anyone can initiate the claim on behalf of the beneficiary.

docs/learn/learn-polkadot-opengov-treasury.md

@@ -116,3 +116,71 @@ requires a decision deposit of {{ polkadot: 10 DOT :polkadot }}{{ kusama:  0.33
 This track can be used for treasury spending requests up to
 {{ polkadot: 100 DOT :polkadot }}{{ kusama:  8.25 KSM  :kusama }} per referendum. Each referendum
 requires a decision deposit of {{ polkadot: 1 DOT :polkadot }}{{ kusama:  0.033 KSM  :kusama }}.
+
+## Bounties
+
+:::info Bounty Guides
+
+See the [bounty guides](./learn-guides-bounties.md) to learn about how to
+[create a bounty](./learn-guides-bounties.md#submit-a-bounty-proposal),
+[assign a curator](./learn-guides-bounties.md#assign-a-curator-to-a-bounty) to a bounty, as well as
+[creating and awarding child bounties](./learn-guides-bounties.md#create-and-award-child-bounties)
+and [claiming child bounties rewards](./learn-guides-bounties.md#claim-a-child-bounty-reward).
+
+:::
+
+### Parent Bounties
+
+Getting treasury funding through OpenGov, depending on which treasury track you submit your
+referendum, can be a long and uncertain process. This can be unideal, for example, for events'
+organizers needing to pay costs upfront or close to the event's date. Bounties solve this problem by
+allowing access to treasury funds once to fund multiple events later on through
+[child bounties](#child-bounties) (that is why bounties are also called _parent_ bounties).
+
+Parent bounty proposals aim to access treasury funds once to fund multiple smaller proposals later
+on without creating OpenGov referenda for each one of them. Bounties are managed by curators, where
+usually a curator is a [multi-signature account](./learn-account-multisig.md). Bounties can access a
+large amount of funds, so managing those funds with a multisig is a good practice to enhance
+security. Essentially, curators are multisig addresses with agency over a portion of the treasury to
+promote events, fix a bug or vulnerability, develop a strategy, or monitor a set of tasks related to
+a specific topic: all for the benefit of the
+{{ polkadot: Polkadot :polkadot }}{{ kusama: Kusama :kusama }} ecosystem.
+
+A proposer can [submit a bounty proposal](./learn-guides-bounties.md#submit-a-bounty-proposal) to
+OpenGov,
+[with a curator to be defined later](./learn-guides-bounties.md#assign-a-curator-to-a-bounty), whose
+background and expertise is such that they can determine when the task is complete.
+
+When submitting the value of the bounty, the proposer includes a fee paid to curators willing to
+invest their time and expertise in the task: this amount is included in the total value of the
+bounty. In this sense, the curator's fee can be defined as subtracting the value paid to the bounty
+rewardee from the total value of the bounty.
+
+Curators are selected through OpenGov referendum after the bounty proposal passes and need to add an
+upfront deposit to take the position. The deposit is calculated by multiplying the curator fee by
+{{ polkadot: <RPC network="polkadot" path="consts.bounties.curatorDepositMultiplier" defaultValue={500000} filter="permillToPercent"/> :polkadot }}{{ kusama: <RPC network="kusama" path="consts.bounties.curatorDepositMultiplier" defaultValue={500000} filter="permillToPercent"/> :kusama }}%,
+and it can range between a minimum of
+{{ polkadot: <RPC network="polkadot" path="consts.bounties.curatorDepositMin" defaultValue={100000000000} filter="humanReadable"/> :polkadot }}{{ kusama: <RPC network="kusama" path="consts.bounties.curatorDepositMin" defaultValue={3333333330} filter="humanReadable"/> :kusama }}
+and a maximum of
+{{ polkadot: <RPC network="polkadot" path="consts.bounties.curatorDepositMax" defaultValue={2000000000000} filter="humanReadable"/> :polkadot }}{{ kusama: <RPC network="kusama" path="consts.bounties.curatorDepositMax" defaultValue={166666666500} filter="humanReadable"/> :kusama }}.
+This deposit can be used to punish them if they act maliciously. However, if they are successful in
+their task of getting someone to complete the bounty work, they will receive their deposit back and
+part of the bounty reward as a fee payment for their job.
+
+Curators are expected to have a well-balanced track record related to the issues the bounty tries to
+resolve: they should be at least knowledgeable on the topics the bounty touches and show project
+management skills or experience. These recommendations ensure an effective use of the mechanism. A
+Bounty is a reward for a specified body of work - or specified set of objectives - that needs to be
+executed for a predefined treasury amount to be paid out. The responsibility of assigning a payout
+address once the specified set of objectives is completed is delegated to the curator.
+
+The bounty has a predetermined duration of
+{{ polkadot: <RPC network="polkadot" path="consts.bounties.bountyUpdatePeriod" defaultValue={1296000} filter="blocksToDays"/> :polkadot }}{{ kusama: <RPC network="kusama" path="consts.bounties.bountyUpdatePeriod" defaultValue={1296000} filter="blocksToDays"/> :kusama }}
+days with the possibility of being extended by the curator. Aiming to maintain flexibility on the
+tasks’ curation, the curator will be able to create child bounties for more granularity and
+allocation in the next iteration of the mechanism.
+
+### Child Bounties
+
+Child bounties are spawned from [parent bounties](#parent-bounties). Child bounties access funds
+directly from the parent bounty without going through an OpenGov referendum.