I took a look at the number of registered users https://steemyy.com/reg.php by running the following SQL:
mysql> select DATE_FORMAT(`ts`, '%Y-%m-%d') as datestr, count(1) from reg where password!='' group by datestr order by datestr;
+------------+----------+
| datestr | count(1) |
+------------+----------+
| 2020-05-08 | 2 |
| 2020-05-09 | 10 |
| 2020-05-10 | 3 |
| 2020-05-16 | 1 |
| 2020-05-17 | 1 |
| 2020-05-18 | 2 |
| 2020-05-19 | 1 |
| 2020-05-21 | 2 |
| 2020-05-22 | 1 |
| 2020-05-25 | 2 |
| 2020-05-28 | 2 |
| 2020-05-30 | 1 |
| 2020-05-31 | 1 |
| 2020-06-02 | 1 |
| 2020-06-03 | 1 |
| 2020-06-04 | 1 |
| 2020-06-05 | 2 |
| 2020-06-06 | 2 |
| 2020-06-08 | 1 |
| 2020-06-09 | 2 |
| 2020-06-11 | 4 |
| 2020-06-12 | 1 |
| 2020-06-13 | 9 |
| 2020-06-14 | 6 |
| 2020-06-15 | 2 |
| 2020-06-16 | 4 |
+------------+----------+
26 rows in set (0.01 sec)
Obviously, it is getting popular. For now, it is fine as the numbers are still quite small even it is growing. With my SP, I could claim around 50 free tickets per day, and with my current ticket number, this service can sustain itself in the next few months or years.
However, if, sometime in the future, this service is getting quite popular, and let's say more than 1000 user registration per day, apparently the number of the free tickets claimed will be a bottleneck. Let's say we fix this problem magically, and the number of the users increases to 1000 per second, then the main problem will be techincally on the scaling part - which can be solved by introducing a load balancer, and migrating data to non-relational database rather than MySQL.
With current design on steem blockchain, the free tickets can be claimed, but cannot be given to others. It would be great if we can trade the tickets, or delegate those tickets and in return are rewarded for account creation.
Every little helps! I hope this helps!
Steem On!~
Reposted to Blog
If you like my work, please consider voting for me, thanks!
https://steemit.com/~witnesses type in justyy and click VOTE
Alternatively, you could proxy to me if you are too lazy to vote!
Also: you can vote me at the tool I made: https://steemyy.com/witness-voting/?witness=justyy
点赞 ☕☕
[WhereIn Android] (http://www.wherein.io)
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
感谢,回赞
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
👏拍手
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
感谢,回赞
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
RC account creation tokens that can be transferred should be included in the next HF.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Yes, agree.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
One (not perfect) solution: https://hive.blog/hiveonboard/@hiveonboard/solving-the-scalability-issue-for-account-creation-no-more-hp-delegations-required
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Thanks for sharing.. I believe i 've read this .
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
This is a must feature.
Do we not have this in place from SMT HF code? I remember roadscape was considering this option by reading his replies before he left.
By the way, thank you for the great tools for steem. I find them very useful.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Thanks.. I don't know the SMT... people have been talking about it for years.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Very well deserved feature, i have voted you, and will vote you again and again.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Thank you.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit