@Councillors, [**motion 220**](https://polkadot.polkassembly.io/motion/220) is now up for vote! Note this is a `batch` call for two treasuries proposals by the Ryabina/Web3Alert team:

- [The first proposal](https://polkadot.polkassembly.io/treasury/136) aims to cover the completed development of web3alert.io: to provide Polkadot users with immediate access to on-chain data. Substrate integration allowing Polkadot and Kusama users to receive messages about on-chain events in Telegram and Discord messengers, totally customisable to the user’s needs. The proposal covers _only_ the Substrate module development (at councillors’ request). Deliverables, reasoning and budget can be found [HERE](https://polkadot.polkassembly.io/treasury/136). 

- [The second proposal](https://polkadot.polkassembly.io/treasury/137), and since web3alert.io is up and running for the community to use, aims to cover the maintenance of the application for the next 6 months. Budget and items covered (codebase updates, servers maintenance and user support) can be found on [the post](https://polkadot.polkassembly.io/treasury/137). 

Make sure to review and vote at your convenience! The team is here to answer any questions!

:
- Vote on motion 220: [**motion 220**](https://polkadot.polkassembly.io/motion/220) 
- Two treasuries proposals by Ryabina/Web3Alert team
- Proposal 1: Cover the completed development of web3alert.io (Substrate module development)
- Proposal 2: Cover maintenance costs for the next 6 months (codebase updates, servers maintenance and user support)
- Review and vote at convenience, team ready to answer questions

#220 Treasury Proposal: Web3Alert development and maintenance for the next 6 months

No Active Proposals