The base protocol configuration, as it has been described here, underwrites credit-risk by charging members varying transaction fee rates, which correspond to the risk they introduce into the network. However, the standard configuration can be extended and modified for specific use-cases.
Networks servicing humanitarian or impact-driven use-cases could, for example, forgo transaction fees altogether, while funding the Reserve externally. This could be achieved by disabling the FeeManager's fee collection function and manually funding the Reserve from external sources. Another way to achieve this while maintaining the existing fee structure is for a third party to underwrite the network’s risk and then cover the fee proceeds for members.
Risk-sharing cooperatives could forgo individually priced fees, and levy a flat and equal fee on all transactions by all members. This could be achieved by charging just the static Base Fee that is set by the AssuranceOracle contract. Likewise, networks could decide to charge members holding positive balances fees in Stable Credits, instead of Reserve Currency units, and use this income to finance the Network Debt Account - instead of reimbursing members as it has been described in the Network Debt Account section.