since @scilio did not provide any references of his capabilities and past work done and is also completely unknown to the community a cautious approach regarding the request is advisable.
I agree. Both Points address the main concerns on both sides (unknown dev vs. whoever pays him) effectively:
Nr. 1. Cutting workloads into chunks would mitigate some of the risks on @scilios side. Imagine working 2 months straight on Grin code, turning everything in and being destroyed by Tromp because the code is deemed as “too complicated” and as a violation of the sacred minimization-principle.
Smaller milestones can avoid these potential problems.
Nr. 2: This would mitigate most of the risks regarding the development funds that are inherent when funding unknown devs.
In a typical work environment, the client/employer pays its employee in advance. However, he does so typically because he believes that the employee is up to the task. Such proof is typically done via resumes, job references, presentation of completed projects and so on.
@scilio is well aware of this fact which is indicated that he proposed by himself that he will do the work first and get paid later.
So i see it that we just need to define the concrete “chunks”/milestones, timeframes (which must not be too long, see Nr.1) and payment and we should be good to go.