But that’s the thing: The user doesn’t pay the system anything save for what the pay in fair exchange for space on the network. I really don’t understand what you’re on about when you talk about 100% taxation because I don’t know where that figure is coming from at all.
-
User exchanges computer resources for safecoin. That’s not taxation that’s an exchange. And one they have full control over to boot.
-
User trades safecoin for space on the network. That again is not taxation that’s an exchange.
The only point the network does anything like taxation is with PtD. And yes I am aware it’s a ratio. So the user doesn’t actually lose any safecoin but still it’s hardcoded in. What if the user wants to offer more or less? What if they want to offer it some other way? Frankly network developers are just another form of content producers but the content they produce is the network itself. It’s like the job security of cooks, plumbers and funeral directors. Yep, they all produce content and provide a service just like anyone else but it’s pretty much guarenteed EVERYONE will use it. But great job security doesn’t mean they aren’t providing content and a service just like everyone else. So the fundamental question isn’t how do incentivize developers as opposed to content producers but how do we create an app that can be used to incentivize content producers and other services because developers ARE content producers, just with awesome job security.
Tanstafl. The “network” doesn’t have a wallet. If the “network” is paying out then where is the money coming from? Answer? Everyone! There’s where the “obligation” comes in.
It’s an algorithm dude. It’s a decentralized network. The whole point is the have nothing but the user’s point of view. But let’s think of it like the network paying in exchange for resources. Developers contribute code which is a form of resources. If that’s the case shouldn’t it be variable on how much demand there is for work to be done on the SAFE network? Just like there is for farming? Lot’s of demand = higher rewards. Less demand = lower rewards.
How would you measure such demand? Measure the number of bug reports, patch requests, RFCs, APP idea submits, etc etc. You’re devs I’m sure you’ll figure something out. Build a “request a tech” button.
But also the same principle could be applied to artists and other forms of creativity as well. Build a “Request an Artist” button or “request a writer button” or measure the number of times that one posts on social media or something. How urgent is it for social media sites to get users? Very. Maybe not so much for the rest of us. But they’d be hitting that “Request Social Media posters” button a lot. How important is it to your average teenager how the events of a soap opera might play out… not so much. But to a bored housewife it might be just the ticket. So my point is design a system to measure relative value. The majority of people will be whacking that “Request a tech” button hard and frequently. We know that, it’ll need to be made of industrial strength rubber. But there will also be other buttons people will bang on that can measure reletive value. And from there the network could measure how much demand there is for any given service. Then you take these various service ticks and feed them into apps and voila you have PtD/P apps.