You are viewing a single comment's thread from:

RE: Recurrent Payments On Hive?

I know that Dan ran tests way back when and I would believe that there are others that have been run. However, doing stuff on a testnet or in simulation is one thing, real world is another.

I would think the cost of the RCs would go up, meaning each transaction would eat up more RCs requiring recoup time. People would still be able to transact but it might not be at the same level as when the blockchain is slow. However, I dont know about that being exactly true so if someone has more knowledge on that, please comment.

If Hive starts to get busy some people might be in for shock at how costly making a comment can be!

Certainly a concern. How it is handled is beyond me. I think I read, once upon a time, that the witnesses can adjust the RC levels to accommodate more activity. But that might be wrong.

I think a lot of what blocktrades is working on is meant to address the scaling issues. It all comes down to cost so if we can run the nodes with less memory, we can add more memory if needed for the same price as it was before.

Posted Using LeoFinance Beta

Sort:  

The variability in RC costs are most noticeable when you claim multiple account creation tokens - it's varied quite a lot in recent months for me, 3 times difference in cost - presumably when a bunch of other people have just created accounts it gets more costly for me to do so, since that's the most intensive activity.

I didn't know that about changing the RC levels.

I guess what ultimately limits us is how much data can fit in a three second block! That is finite after all.

If someone decided to publish their PhD in a block I think that would fill it up I worked out once - 100K words - but that's a lot of Custom Jsons or comments!

I guess in times of heavy load things would just not publish to the chain for those without sufficient HP.

Although I don't know how data load factors into all of this either come to think of it - as far as I'm aware in RC terms publishing a PhD costs as much as saying 'nice post'.

Posted Using LeoFinance Beta

Another thing, the fact that these conversations are taking place is beneficial. It means that people are not overlooking it, including the developers. Thus, scaling is at the forefront for a lot of people even though there is little need for that right now.

For that reason, I have a feeling solutions will be in place before it is truly needed.

Posted Using LeoFinance Beta

I think posts and comments have different RC values but I am not 100% certain. If not, you are correct.

I think one thing we will see is what Leofinance is doing. They are using their servers to cache the data and published on the blockchain's time. That means the user doesn't see the delay and is not affected by it. In the end, does it matter if something takes like 10 seconds to post if the front end operates in real time?

But these are all questions/discussions for people a lot more knowledgeable than me. I don't have enough understanding of how it all works.

Posted Using LeoFinance Beta

That caching solution is pretty elegant, it's a good idea!

I think part of the problem with the knowledge gap is that a lot of this is contingent, it all varies depending on what's going on - dynamic is probably the word I'm looking for!

Posted Using LeoFinance Beta

There truly are a lot of moving part. It is really interesting to keep digging through the different levels.

We are seeing a lot happening at one time. Some at the app level like with Leofinance and other things at the blockchain level.

I have a feeling that people are going to have a totally different view about both Leo and Hive in 6 months. This will be a completely different place.

Posted Using LeoFinance Beta