You are viewing a single comment's thread from:
RE: HF20 Update: Restoring Continuity
There is one very important problem.
The transfer of funds and the power-up should not consume rc and should not have a minimum demand of rc.
Now I can't power up.
I think you make a great point. There have been some suggested attack surfaces with free transactions, but with the holding costs involved in powering up, you could still be right. For now, at minimum, there is baseline RC based on having an account. This RC will regenerate and allow any account to powerup given enough time passing (approximately a few hours).
In the blog you mentioned mana and RC as a solution to double voting. Why didnt you just use delegated SP's with the receiving accounts SP in a weighted average manner relative to their stakes? I mean in the old system all transactions had 0 cost. It was free to interact now you pay...
The old system had the same type of invisible bandwidth costs. Instead of Resource Credits, it was referred to as Bandwidth.
Sure but that was ample. Why not set all RC costs to 0 and drop the limitation 1 by 1. First for comments and see how many are supported tweak the RC. Add another parm. Why all at once?
That's simply wrong. There has always been a cost to transacting here, but most people didn't know about it. But minnows who used Steem during its most active state remembers bandwidth, because it also prevented them from using the blockchain too much. So not much has changed, except that "bandwidth" is not renamed to "Resource Credits", and the algorithm for distributing it has changed a lot.
As we all move ahead in 'oneness..."Reversing Forward. Future Is History"
In addition to powering up, unsigning witnessses and changing witness settings should also be RC-free, viz the current issues with @netuoso.
That would open up a potential attack to the blockchain though, where people with malicious intentions could spam witness votes and unvotes in order to clog it up. I think having free witness changes would open up a lot more trouble than it's worth.
Not witness votes, witness settings. Someone with malicious intent would have to be running a witness.
We still have free API reads anyway, so it's not like anyone's going to have a hard time DDOSing things. And if there aren't enough resources to go around for writes, reads become another huge problem.
Ah, alright. I must have misread/misunderstood your original comment then. Sorry! But it makes more sense now, and I do agree that witness setting or unassigning witnesses should be free from RC cost.
As we all move ahead in 'oneness..."Reversing Forward. Future Is History"
As we all move ahead in 'oneness..."Reversing Forward. Future Is History"