@Councillors, after the team received the feedback, regrouped and answered all questions, the **PolkadotSpace** has submitted an updated proposal that has been passed for Council. Specifically, based on feedback, the team **separated the RPC service proposal and the indexer proposal** and presented the new on-chain submission by removing RPC service from the equation. Please note that with the team's agreement, the motion contains a `batch` call: _approving_ the [updated proposal](https://kusama.polkassembly.io/treasury/217) and _rejecting_ the [previous one](https://kusama.polkassembly.io/treasury/209).

The full proposal, along with the budget and idea behind it, can be found here:
__________________________________________

"Thanks for all the existing support that we have. We have reached out to few councils members for feedback.

**Original Post:** [https://kusama.polkassembly.io/treasury/209](https://kusama.polkassembly.io/treasury/209)

The feedback that we got is to separate the RPC and the indexer into 2 proposals as they represents 2 different value chains. We agree and are resubmitting based on the feedback that we have received, removing RPC from the equation.

Currently, this value remained in the proposal:

A Content indexer so that when people searched for educational or articles related to Kusama and Polkadot, we are able to provide a categorization and filtering value to the search result. The target audience is anyone who are interested in the above and wants to join or provide a little touch of their Likes as part of the community feedback to the indexing mechanism. This can be a lurker, a content creator or a technical learner.

The above will help to gather the information done by many content producers that are being posted in so many repeated location and provided a relevancy.

The new proposal, which can be found in below link: [https://docs.google.com/document/d/1HVOfNDEVJ29KInEzDCIPzPBW9QzavI90HjI2b2jxW1E/](https://docs.google.com/document/d/1HVOfNDEVJ29KInEzDCIPzPBW9QzavI90HjI2b2jxW1E/)

We welcome feedback and improvement on the proposal, as at the end of day, the community will be part of us, will also be part of the scalable solution and the enrichment of the data and recommendations. We also want to offer transparency to the proposal. After all, this is supported and funded by the community.

________________________________________


Send a batch of dispatch calls.

May be called from any origin.

- `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 call are dispatch without checking origin filter. (This includes
bypassing `frame_system::Config::BaseCallFilter`).

# <weight>
- Complexity: O(C) where C is the number of calls to be batched.
# </weight>

This will return `Ok` in all circumstances. To determine the success of the batch, an
event is deposited. If a call failed and the batch was interrupted, then the
`BatchInterrupted` event is deposited, along with the number of successful calls made
and the error of the failed call. If all were successful, then the `BatchCompleted`
event is deposited.



- PolkadotSpace has submitted an updated proposal that has been passed for Council
- Based on feedback the team separated the RPC service proposal and the indexer proposal and presented two new on-chain submissions
- The motion contains a batch call, approving the updated proposal and rejecting the previous one
- The new proposal is focused on creating a content indexer to provide categorization and filtering of search results for users interested in the Polkadot/Kusama ecosystem
- Proposal and budget can be found here: [https://docs.google.com/document/d/1HVOfNDEVJ29KInEzDCIPzPBW9QzavI90HjI2b2jxW1E/](https://docs.google.com/document/d/1HVOfNDEVJ29KInEzDCIPzPBW9QzavI90HjI2b2jxW1E/)

#554 PolkadotSpace - Search Indexer (rejection of treasury proposal 209 and approval of treasury proposal 217)