# Signalling - Donor Drop Round Two: Web3Privacy Now 🎯 **URL:** \ **Category:** Proposal 🗳️\ **Created:** [23 February 2025 18:32 UTC](https://forum.namada.net/t/signalling-donor-drop-round-two-web3privacy-now/1555 "2025-02-23T18:32:43Z")\ **Posts on this page:** 1\ **Showing post:** 24
**Author:** ![Gavin](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.namada.net/gavin/32/16_2.png) [@Gavin](https://forum.namada.net/u/Gavin)\ **Post date:** [28 February 2025 13:46 UTC](https://forum.namada.net/t/signalling-donor-drop-round-two-web3privacy-now/1555/24 "2025-02-28T13:46:52Z")
## Idea: cPGF as a distribution schedule What if we **streamed the airdrop to recipients over the course of two months using cPGF?** There [isn’t a cPGF feature for streaming](https://github.com/anoma/namada/issues/4104) a total amount or have an end epoch, but I’ve thought of a work-around we can test. ### Work-around Launch two PGF proposals: one that enables cPGF (Prop1), another that disables that cPGF after two months (Prop2). How? We set each cPGF amount to be airdrop\_amount / 240 epochs in Prop1, and set a grace period of 240 epochs for Prop2. @brentstone, do you expect that this will work the way I have assumed it will? I [don’t see](https://forum.namada.net/t/mainnet-parameter-discussions-knowables-proposal/753/94) a maximum grace period parameter. cc @Super0086-code @cwgoes --- _[View the full topic](https://forum.namada.net/t/signalling-donor-drop-round-two-web3privacy-now/1555)._