Option A: If the price falls, we dont pay out the contracts. In this case weve made a contract and burned the bridge with a contractor doing ongoing work. This makes our network unusable long term.
Option B: The proposal system could create unpredictable inflation based on the promises the network is making for USD based contracts.
Option C: We allocate in Dash to avoid all of these issues and dont support USD based contracts at all.
Option D: We give the foundation a budget to take Dash and convert it to fiat, then it keeps the fiat in a bank account. The contractors would contract with our foundation directly and this bank account would serve as a volatility buffer.
Option E: We allocate only X% of the budgets according to the historical volatility of the currency. This can be calculated by taking two standard deviations from the average price history for a long period of time, then figuring out a high and low price threshold. However, this will still result in contractors getting burned once in a while.
Paging TokNormal and BabyGiraffe

A: Not a great idea unless the contractors understand this possibility before starting work. This added risk would probably have the impact of increased costs but no burned bridges.
B: I really dislike this idea. Budgets should be capped to a limit. Going under is fine, going over and increasing output removes trust in the system.
C: I like this one the best, but obvious drawbacks are obvious.
D: This WOULD be a decent idea if it didn't dramatically reduce decentralization of the budget and project as a whole.
E: This is my second favorite after option C. Seems to alleviate the problems of option A.
my 2 cents.