Ted-Livingston on Definition Spends & Earns #152
Replies: 2 comments 11 replies
-
|
Thank you for responding, Ted. Your first question is How to define EARN and SPEND. Users can only do 4 things with their user wallets.
We also know the wallet address of the app. What counts are numbers 1 + 2. A SPEND always lowers the user balance. Transactions (tx) seen from user point of view: A user to user tx falls under 3 and 4. This way we can see the difference between real SPENDS / EARNS and all other transactions. That means that if we pull P2P tx into the KRE you open the door for massive gaming. The only way to stop gaming is to just reward SPENDS minus EARNS. Is a buy through an in app buy module an EARN? Is a deposit from an exchange an EARN? Is a SPEND anything that lowers the user balance? Is a User to User transaction a SPEND? Is a withdrawal to an exchange a SPEND? Is a tranfer from one app to another a SPEND? Your example of potential gaming
Not one time a number 1 or 2 ( SPEND or EARN ) was made. The next is your variation that instead of tipping in step 3, something is bought in app.
We don't have to rely on what a developer passes on to the KRE. We don't need a memo field. Everything is automatically arranged from the transactions on the blockchain. The memo field can again be used for what it is intended for... a memo. .................. What you get with this system is that you only reward the actual Economic Activity. That's why we need a 2nd fund for apps that are very important, but don't have Economic Activity. A buy module is very very important, but it in itself is no exchange of goods or services. It is a tool. Opening up the KRE for buy modules would mean rewarding deposits....and that, as shown above, opens the door for gaming. So the only logical thing to do is to make a 2nd fund and determine on a case by case base whether an app qualifies for it. In case of CODE it is very simple. However, we don't need e.g. 20 different buy modules. I admit it all sounds very strict, but for now it is necessary. |
Beta Was this translation helpful? Give feedback.
-
|
Hello Freedom. I think undermining the huge risks that comes with the flaws and gaming potentials of the spend based KRE would be a huge mistake. Just relying on the government and tax authorities to deal with bad actors is not smart. You mentioned no smart entrepreneur would do such a thing but we all know that in the history of the KRE there have been developers who have gamed the formula. These developers had ways to avoid taxes so its safe to assume they would do the same thing with the new KRE formula specially now that the new spend-based formula makes is SUPER easy to be gamed. |
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
-
Hi Ted, I've taken the liberty of copying your comments into this discussion.
ted-livingston
3 days ago
Hey Freedom. I appreciate you taking the time to put this proposal together. It gets me excited to see you and others leaning in on this, as I agree the KRE is the most important part of Kin. I hope we can all work together to explore these ideas and find the best solutions.
I have a few thoughts on your proposal, but I wonder if it might be helpful to take them one at a time. My goal isn’t to be pedantic, but to keep the discussion focused so that we aren’t trying to tackle multiple topics at once.
Perhaps my first question is around how you define “earn” and “spend”.
For example, is a buy through an in app buy module an earn? Is a deposit from an exchange?
For a spend, is it anything that lowers a user’s balance? If not does a user to user transaction within an app count? Does a withdraw to an exchange? What about a transfer from one app to another?
I think these definitions are important to both reduce gaming and create the right incentives.
For example, one way how I see gaming could potentially occur:
In this scenario it seems like user_account1 might look like it had a net spend of 1,000 Kin, resulting in a 300 Kin bonus for the developer, even though they are just moving money around programmatically. Perhaps even simpler, instead of tipping user_account2, the developer could perhaps just have user_account1 buy a digital good from the app. There likely wouldn't be any sales tax, as just because an app tells the KRE it made a sale, it seems they could tell their accountant they were just moving money around, which I don't think would be breaking any accounting rules.
What are your thoughts on this and how your proposal might protect against it?
Beta Was this translation helpful? Give feedback.
All reactions