Thanks for starting this and all the ongoing work @aliyajypsy - it’s really awesome. @saintsal
A fee to apply may make it prohibitive for people to continuously re-apply, which I don’t think is great.
Are we all talking about an enrollment fee (i.e. paid once accepted to the mempool track)? If so, it could be helpful, especially if refundable. I like that it would go into a “scholarship pool”.
I don’t think it’ll give us infinite runway (one of the risks being we will need to take breaks occasionally) but $500 per fellow should help significantly.
Now, how do we implement this? Of course, my mind goes to FreeLearn. Though it doesn’t quite fit, for various reasons. It would be simpler to:
Write a mempool contract that can receive DAI (lock it in a Yearn vault for slightly more return + much more contractual complexity).
Allow anyone who sends DAI to withdraw what they send at any point.
Allow the Kernel multisig scholarship fund (we need to set up another multisig anyway, for better accounting, greater security etc) to sweep funds in the mempool at periodic intervas.
The third point is scary and not good design. However, if we communicate clearly once the mempool is closed that we will be sweeping funds in it to go towards fellow scholarships, and then do the sweep ~2 weeks later, just before we open apps again, that could be OK.
One advantage of this is that it also gives us a (partial) source of truth for an ACL. It is partial due to self-qualifying financial assistance. We could include another function for that, which just requires people to register.
However, (i) this still costs gas and (ii) if we use the mempool contract as an absolute SoT, then anyone can “register” or send 150 DAI and we would mistake them as being in the mempool track.