overflow funding model

[serapath]

@todo

• write down first draft of "overflow funding model"
• conceptualize funding model in more details

---

overflow funding (with similarities to npm fund)

1. use inflation tax to make datdots for users (when they provide services)
2. use deflation tax to raze datdots from users (when they use services)
3. all users pay a regular redistribution tax
4. quit the ecosystem to avoid being taxed
5. proof what software/dats people are installing and running on their system
6. split the regular redistribution tax based on used "software"
7. if no "software" is used or selected, at least datdot itself is selected
8. every "software" needs to include a maximum cap, after which the remains trickle to dependency softwares to reach their cap (=upper limit)
9. if all "software" reached their cap and datdots are left, it goes back to users who paid

also:

• keep it transparent (e.g. max cap's projects choose + tools people use and therefore fund, etc...)
• automate everything possible
• couple it with real attention/decision where people using apps means funding
• avoid disconnecting it from tools/products/services users appreciate
• avoid turning it into interesting poker like game (take the gaming aspect out of it)
• make funding model super simple and boring
• inflation based
• real-world-value pegged (storage)
• fixed-value-transfer (fixed service costs, e.g. validators, ... are paid via inflation)

ecosystem is created via datdot electron app which makes dat/datdot available in normal browsers for people to build apps (e.g. cabal, mapeo, pushpin, cobox, sonar, etc...) so they can start offering their "(d)apps" and earn for it and people can be entrepreneurial and make more apps (e.g. games) and like datdot itself, they will also use dependencies (e.g. hypercore, hyperswarm, substrate, ...) which get paid too and it creates a real and valuable ecosystem not doesn't stay just empty theory.