Dear Polkadot community,
Thank you all for your support and votes on the approved <a href="151">Referenda 151</a>. I want to address an oversight regarding the multiple batch calls assigned to the "big_tipper" track, where I assumed individual limits were checked relative to the track limits. However, the total spending of the call is checked relative to the track limits. As the result, the referenda failed to execute.
Due to my oversight, the previous Referenda was submitted under the "Big tipper" track instead of "small_spender." To rectify this, I am resubmitting the proposal to the correct track. I apologize for any inconvenience this may have caused.
--------------------------------------------------------------------------
Dear Polkadot community,
Collators on System Parachains are provided with minimal rewards for block production and small incentives in terms of transaction fees. This reduces incentives for Collators to act in a favorable manner and they may also be inclined to under-resourcing their hosts to save costs. Collators should receive funding for the provision of their services. Ultimately, this should be provided by the chain in a preferably sustainable manner. Implementation of such a system is a long-term solution. In the medium term, funding for collators can be provided by the respective Treasuries in the form of a bounty. This allows funding to be pre-allocated and independently managed.
Based on <a href="https://kusama.polkassembly.io/bounty/20">Kusama System Parachains Collator Bounty</a>, and <a href="https://github.com/polkadot-fellows/RFCs/blob/7eb2193a1a82818c83be4501c4b2a1e6d343dedb/text/0007-system-collator-selection.md">RFC-0007: System Collator Selection</a>, this proposal is a short-term solution aiming to post-pay monthly operating costs of service providers until a more suitable solution (Bounty) is established.
<a href="https://docs.google.com/document/d/1KjThkBTp3nJBF4CAV-Jn8fA0PUrd2Lbhy7DOrVHISX0/edit?usp=sharing">Full Proposal</a>
The proposal aims to secure 6,075.79 DOT for Collators on the Polkadot System Parachains network for services delivered for the period of 2 months - 08-09/2023.
<img src="https://i.ibb.co/SxYzWvZ/Screenshot-2023-09-11-at-10-25-19.png" alt="" width="400" height="262" /><img src="https://i.ibb.co/t2pJHWM/Screenshot-2023-09-15-at-12-53-37.png" alt="" width="400" height="259" /><img src="https://i.ibb.co/NN0c7zG/Screenshot-2023-09-15-at-12-52-13.png" alt="" width="640" height="480" />
This discussion will be open for a period of one week before submitting the proposal onchain. We encourage the Polkadot community to review this proposal and provide any feedback or suggestions.
Thank you!
*Update 11/09: Parity Collators excluded from the funding proposal. Updated the document with new verified identities.

Send a batch of dispatch calls and atomically execute them.
The whole transaction will rollback and fail if any of the calls failed.

May be called from any origin except `None`.

- `calls`: The calls to be dispatched from the same origin. The number of call must not
  exceed the constant: `batched_calls_limit` (available in constant metadata).

If origin is root then the calls are dispatched without checking origin filter. (This
includes bypassing `frame_system::Config::BaseCallFilter`).

## Complexity
- O(C) where C is the number of calls to be batched.

- The previous referendum failed to execute due to an oversight.
- Collators on System Parachains should receive funding for their services.
- This proposal aims to post-pay monthly operating costs of service providers until a more suitable solution is established.
- The proposal aims to secure 6,075.79 DOT for Collators on the Polkadot System Parachains network for services delivered for 2 months.
- The community is encouraged to review the proposal and provide feedback.

#156 Polkadot System Parachain Collators - Tips - Referenda #151 failed to execute

No Active Proposals