Repository
https://github.com/scr53005/eftg-steem/blob/master/README.md
Details
The first task related to the eftg-steem project was assigned to @jga. Here is his contribution.
There are few improvments that need to be done:
• the architecture. – is missing
• minimum requirements for the VMs computing power and storage. – it needs few more details (is the same for all the roles witness, fullrpcnode, seednode?)
• firewall setup (opened ports and protocols) requirements for operating system and also for all dependencies. – it needs few more details (to be detailed all the needed ports, TCP/UDP?/ inbound/outbnoud? )
• step by step instructions (command lines) on how to start and connect different type of peers. = DONE
• step by step instructions (command lines) on how to generate the genesis block (first block) and the first key pair. = DONE
• specifying how to modify the number of minimum/maximum witnesses based on different network topologies. – explanations needed
• specifying how to modify the blocksize (if needed for some specific projects). –missing
• all the config files. = DONE
• documenting all the steps needed to install, configure and start the Steemit condenser on this specific steem private network. - missing/ but removed from task 1 and created task 2
• documenting all the steps needed to install, configure and start the Steemdb blockexplorer on this specific Steem private network. – missing/ but removed from task 1 and will be created a new task
• documenting all the steps needed to install, configure and start the steemconnect on this specific Steem private network and how to create new accounts. – missing / but removed/ we don’t need it at the moment
Also, the posting function, the transfer, transaction history and the creation of a new account should be tested. Also, the producer reword needs to be checked .
Directly linked to the first task, here is the second task :
TASK 2
The goal of this task is to provide a clear documentation on how to setup a steem condenser (steemit or busy) to work with a private steem blockchain network. It will be tested with our existing private network. You find here all the details to connect with
It is required to document all the steps needed to install, configure and start the steemit/busy condenser on this specific steem private network.
Components
steemit condenser or busy condenser.
Deadline
1 week starting with the decision to select someone to work on.
Communication
Get in touch with us on: https://discord.gg/pV5hgDA
Before starting any work, please get in touch with us, to avoid tasks or subtasks overlap.
Thanks for creating a TR.
The TR can be solved by many devs in our community and will surely receive some awesome contributions.
Some more proper markdown will make the TR look much better.
Awesome work! Hope that you get TR solved really soon.
Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.
To view those questions and the relevant answers related to your post, click here.
Need help? Write a ticket on https://support.utopian.io/.
Chat with us on Discord.
[utopian-moderator]
Hey @smartiot
Thanks for contributing on Utopian.
We’re already looking forward to your next task request!
Want to chat? Join us on Discord https://discord.gg/h52nFrV.
Vote for Utopian Witness!
Confusing how this post refers to SteemIt/busy condenser.
Condenser is the nickname given to the SteemIt frontend.
Busy is the name of the busy frontend.
Condenser doesn't refer to busy.
Is this task asking how to run the busy.org frontend or the SteemIt.com frontend? The process would be wildly different.
Thank you for this comment. Our goal is to have configured our own frontend, even it is condenser (steemit) look like or busy.org look like.
As Iulian (@smartiot) says, it is unimportant whether the code base is that of the SteemIt condenser or the Busy frontend.
If someone from @busy (such as for instance @fabien or @ekitcho or somebody else) would like to contribute a guide on how to set up the busy frontend to work with a private steem blockchain, we would be very happy. I confess I find the Busy frontend to be niftier than the Steemit one :-)