I re-read your proposal and thought about this some more. In general, I think there are a lot of things in the proposal that seem more complicated than necessary. In particular, the bit about trust networks. Now I do see this as a key part of your proposal, so I'm outright disputing it's necessity. However, I think it is a composite solution to several problems that didn't get enough ink individually. I think the discussion could benefit from discussing the individual issues before deciding on a technical solution.
The trust networks are integral to avoiding a pooling of resources. The pooling of resources like bitcoin does allows for singular points of attack against the network. A pool or two goes down and all of a sudden the network is vulnerable. Also, as far as the trust system goes, there needs to be a larger amount of trust spread out across more people, or else you make it easier to attack the trust. And since these are not many-to-one but many-to-many, every individual is resistant to attack individually, not as a group.
It is such a different design from bitcoin because it needs to address the problems in how the network operates. 51% computational attack is thwarted. Now there is a reasonable system of voting. Signature proofs of who is being dishonest. Easier for a new user to get in and start making coins. Much more information available as to how the network is operating. I designed this idea over the course of several weeks to finally come to what it is now. I mean if you see weaknesses, please point them out. A big one is anonymity, but trading all of these features for a bit less anonymity is worth it, imo. Anyone who buys in for cash can still remain separate and anonymous from the network as a whole.
The other thing I still don't grasp clearly from the proposal is the mapping back to quantities of electricity.
The 10kWh figure was used because that is what most closely resembles the amount of a single unit of the world's most popular currencies. It is mostly irrelevant other than to gauge a general magnitude of what one coin is worth. Like I said earlier, if the average user is using 300Wh, then it is closer to 15kWh. Perhaps I will drop using 10kWh since it may just lead to confusion.
The point sd brought up is certainly significant. I can only offer the obvious empirical evidence. Over time, all CPU's will use less electricity to do the same amount of work. As such, you need a (hopefully) auto-adjusting parameter that keeps the proof-of-work load constant in kWh.
The
amount of work is a non-issue, as difficulty will work similarly to bitcoin, just divided among the networks. The
amount of electricity used to perform work is the issue. And this is only a problem if everyone starts using energy efficient hardware. Not a likely paradigm shift any time soon with GPUs requiring bigger and better power supplies, more and more power connections, etc.
I see lots of proposed constants in your technical information. What I don't see is anyway to vary those constants over time. JohnDoe has a proposal based upon voting but this is your thread so I prefer to understand your ideas.
Ok, lemme go through the list. Block award should probably be a constant. Being able to find a block every so often on average should be a constant to determine difficulty. Network trusts having 100 wallets, well if we don't limit that then the system of trust is very limited. Losing 10 trust for not finding a block, up for debate but certainly must be some kind of number--certainly could be a trust module vote. Minimum computational speeds and minimum payouts--up to each network. Fees for utilizing the network, probably should be a constant, really makes no difference if it's not but then I don't know by what measure to get them. 64 character maximum on transaction message, probably should be a constant unless we want to bloat the blockchain with useless data.
I mean is there anything specific that you take issue with other than a number being constant? None of the figures above constrain the network into one hole that is incapable of future expansion.
I think you are probably right on the fixed transaction fee/tax concept. However, that means the elasticity of your model can expand as fast as it needs to, but it can only contract at a fixed rate. This gives me pause.
It can't expand as fast as it needs to. There will be expansion pains. Coins still take time. And it does not contract at a fixed rate, it contracts based on how much money is moving around. So it might take a little longer to get back to equilibrium, that doesn't mean it won't get there. It doesn't mean it will take years. People minting coins can't vote for the transaction fee because they will always vote it higher; it is in their own best interest, this should be obvious. If you have the network try to decide its own transaction rate, going higher in times of high supply (which would be awfully complex to determine from programming), then you will get people who will hoard waiting for
others to spend, or businesses that will raise prices to accommodate, or what have you.
For me, this has to be the nominal case goal for any cash alternative currency. Meaning, specifically, in the case where the currency value is stable (2c), if I'm transacting in coins (buying or selling), I'd better not be penalized for using money as a medium of exchange that is of course our main point.
What do you propose to support the network then? If there is no fee, inflation may go unchecked. If there is no fee, miners have no incentive whatsoever to mine. The network loses security. One can easily counteract the fee by joining a network trust, putting in your time, then moving on to a trust in cool-down mode and getting bonus encoins for the same amount of work (the 1/8th for 1/10th idea). Having people provide a secure, incredibly cheap, reliable form of sending money to anyone in the world in 30 seconds just simply can not be free
and stable.
If you attempt to program in determining whether or not we are in a 2a, 2b, or 2c phase of the economy, then you are asking software to know what's best for the economy instead of letting it work itself out naturally. That's quite the can of worms.
This *requires* that in cases (2c) and (2b) all transaction fees be refunded prior to bonus coins being awarded to so called miners. This is logically invariant no matter how much work a miner thinks they proved.
You'll have to explain this further because I'm not sure what you mean. The bonus is a reward for being a highly trusted member of the community and putting in a lot of effort to make the network secure. Sending a transaction does absolutely nothing for the network security, it is a service that the network provides. You propose that a service should be free because there are employees that get paid more than others? I don't follow the logic here. If miners don't get paid, what is the incentive to mine? You are thinking about this from one side only.
It is easiest to see in the stable (2c) case. If our coin value is stable, that means the appropriate monetary policy is to do *exactly* nothing. Do "no work" in the mass times distance sense. That doesn't mean nobody put in effort. It just means no work got done or should be rewarded. Why would we reward the people (do something) who just mathematically proved our best monetary policy decision is to do nothing?
Now you are really losing me here. Again, miners are providing the service, spenders are making use of that service (and not even paying the fee). When we are in 2c, most miners will be in a cool down mode, only creating enough coins to replace what has been lost. And in doing so, they are
securing the network.
Purchasing during *temporarily* inflated times is illogical/desperate. We want to reduce the number of coins flowing for too few, over priced, goods. That drives prices back down. The only way to encourage that is to tax the spenders, thus rewarding the savers. This is critical because, as I pointed out above, this is the least elastic of your monetary directions.
It is also, hopefully, the least likely. It means the economy has contracted, which no matter how you look at it, is not going to be good. Receivers paying the fee is not set in stone, so if that were to switch to the spender paying the fee, then this would be even worse for spending. Having the receivers pay the fee is a design decision I added to the proposal only a few days ago. It isn't set in stone. But I will think more on this.
An extreme contraction is a lot less likely than an extreme expansion, though imo. And a slow contraction
would be counteracted by the effects of a transaction tax. Again, businesses don't have to change their prices, so no one is actually buying anything at an inflated amount.