Hiveland | Nodes, Layout & More
This post it is created by @doze
Hive Ecosystem Nodes
SPK Network Node
We configured our @spknetwork node however we currently don't have enough Larynx to be one of the network validators.
Anyway, we are somehow contributing to the network being decentralized by more nodes.
Hive Engine Node
We've configured and got our node running and we've already tested the requests part.
Right now, we can't set our node as a witness for two reasons:
We are using the same IP that we were using on the first node that we configured to test with the user @ptmaker and HE does not allow registering more than one node with the same IP even if we turn off the previous one and remove the registration from it .
The server we are using is a basic server which is what our funds allow and we noticed that it takes some time to get completely updated. When we are going to launch the first version we will have a better server, something that at the moment cannot be handled by the team and we will even have to go ahead with a proposal to the DHF.
Layout
We started to programing the website main page layout for white and dark theme.
Take in consideration displayed token data it is not real, it's just data for our test.
The next step will be to develop the layout for the individual token page and do a lot of tests booth pages using different mobiles and laptops so see if everything works well.
Tokens Classification
Currently exists more than 600 tokens on Hive Engine but not all the tokens are "real"
tokens beacuse exists several tokens that have no supply.
Since this project main goal is to give clear and well-organized information and that we will rely on the creators of the communities/tokens to help us get as much information as possible we have decided that tokens by default will not be automatically displayed on the site. They only became visible on the site after we had reviewed all the information about them.
In this way we can guarantee the quality of the information that we will make available.
Want to help us to improve?
All suggestions all most welcome.
Follow us to weekly updates
Later on we intend to submit a HiveLand proposal to DHF to be funding and help our project and development.
All suggestions all most welcome.
Follow us to weekly updates
Later on we intend to submit a HiveLand proposal to DHF to be funding and help our project and development.
@hiveland.dapp! The Hive.Pizza team manually curated this post.
Learn more at https://hive.pizza.
Congratulations @hiveland.dapp! You have completed the following achievement on the Hive blockchain and have been rewarded with new badge(s):
Your next target is to reach 50 upvotes.
Your next target is to reach 200 upvotes.
You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word
STOPCheck out the last post from @hivebuzz:
Support the HiveBuzz project. Vote for our proposal!
It's looking really good! =) Exciting times.
About this:
Hmmm. I was pretty sure it would be possible by just changing ports, but maybe there is something I didn't forsee. Reach me on Discord if you wish and we can chat about it. Either way, the 2nd stuff is a showstopper if you don't have enough few GB's (4 to 8) of memory and lots of IO for example.
We asked on the Hive Engine discord and they said it was not possible.
At the moment we are using that node for our developments but we cannot register as a possible Hive Engine witness.
Regarding the quality of our current server, it is clear that when it goes to production we will need a better one to be able to handle requests from our platform and the node update as efficiently as possible.
Is Larynx miner token can be delegated?
I am not planning to sell nor planning to run node. I think there were many like me those who like to delegate.
BTW, how many tokens are required to run Node?
larynx can not be delegated at this time. who knows if that changes in the future, but there will be spk token mined from it in the future. last i check about 5k tokens to join governance but it varies so could be different already.
As @verbalshadow said the Larynx cannot be delegated.
The number of tokens needed to be a validator changes over time so it is difficult to really know the amount of Larynx needed to be a validator.
Started at 2.5k and now it is more than 5k