Hey all -
I wanted to shed some light on how the new treasury flow should be. We will update our docs for sure 
RT3400- Treasury Proposal Flow [Before]
The following is a summary of the actions a team/person has to go through to get funds from the on-chain treasury before RT3401:
- Conduct a forum post to inform the community about their intentions and gather feedback. It was recommended that the Treasury Council publicly support the proposal via forum replies before moving to the next step.
- Do an on-chain treasury spend proposal. This would require the user/team to lock some funds (a % of the requested amount).
- The Treasury Council would vote to either approve/reject the spending proposal. If approved, the team would receive the funds, and the bond would be returned. If rejected, the team would lose the locked funds.
RT3401+ Treasury Proposal Flow [After]
Moonbeam uses the same Treasury pallet used by Polkadot. The Treasury module had some upstream modifications that led to changes in how the protocol handles treasury funds.
The following is a summary of the actions a team/person has to go through to get funds from the on-chain treasury after RT3401:
- Conduct a forum post to inform the community about their intentions and gather feedback.
- The Treasury Council will now create an on-chain action to vote directly on treasury spending via a Council proposal. Consequently, the team/person is not required to perform an on-chain action or lock funds.
- If approved, the user/team will receive the funds from the treasury. If rejected, the user/team will not receive any funds, but they don’t have any locked funds to lose. Hence, the Treasury Council is not really required to put the on-chain vote if they publicly disclose that they do not favor it.
Note that to ensure the Treasury funds are not locked, RT3401 will use the call treasury.spendLocal. For RT3500 onwards, the call treasury.spend will be used, as the previous one will be deprecated as of May 2025.
Happy to answer any questions 