Hi All,

Two referenda were opened to test the use of batch calls as applied to Open Gov treasury spends.  The first was [referenda 58](https://kusama.polkassembly.io/referenda/58), this was issued on the Big Tipper track which has a spend limit of 33 KSM. The referendum tested two individual spends (8 & 2 KSM) both of which were within the maximum spend of the track and whose total spend was also within the tracks limits.  The second was [referenda 62](https://kusama.polkassembly.io/referenda/62), this was executed on the Small Tipper track which has a spend limit of 8 KSM.  This referendum was tested using two individual spends each within the maximum limit of the track (8 KSM) and with a total (8+8 KSM) exceeding the track's limit.

Both referenda passed and parties received funding.  The passing of these referenda provides us with some information:


**The good**

We (the community) now have added flexibility in the way that we can propose spends.  
   - We can for instance, proportion tips with a finder's fee
   - Group spends together to save on preimage and deposit fees *
   - Use this as a mechanism to directly allocate project funding to the respective major parties

\* - There is an approval risk when grouping spend proposals together. 

**The cautious**
With the good comes some caution, as seen with referendum 62 we can circumvent the total spend limits of a track, there by achieving the benefits of quicker approval times with lower thresholds.  

I believe that the good outweighs the bad and that the community can be that deciding factor whether referenda like 62 are allowed to pass or rejected due to perceived abuse.  It might also be a candidate for a bug fix.  What do you think?

I thank you all for participating in this test, thought it was not exhaustive the information was imo useful.

Regards,





- Two referenda were tested to see how batch calls can be used for treasury spends.
- The first referendum tested two spends within the spend limit and total limit of the track.
- The second referendum tested two spends within the spend limit of the track but exceeded the total limit.
- Both referenda passed and parties received funding.
- The community now has more flexibility in proposing spends, but there is also caution about exceeding spend limits.

#2151 Testing batch calls within OpenGov Treasury Spend tracks.