BitShares Forum
Main => Stakeholder Proposals => Topic started by: etienne_marais on December 07, 2017, 08:42:37 pm
-
I am planning on setting up what I take would be the first Witness in South Africa.
Please confirm if, and projected for how long, a server with the following specs. would suffice:
64GB RAM
E5 2603
2TB HD (SATA II, 64MB cache)
Server co-location I am looking at will provide 100MBS fibre backbone access with 4TB bandwidth.
Please indicate what could be my chances for being voted active.
-
Your server is more than sufficient for running a witness node at this time, and for some time to come.
In order to get voted in, you should provide additional infrastructure, like seed node(s) and/or API node(s). You also need a backup server, preferrably in a different location, that can take over when your main server goes down.
For setting things up and proving yourself it would be advisable to run a testnet witness as well.
-
Your server is more than sufficient for running a witness node at this time, and for some time to come.
In order to get voted in, you should provide additional infrastructure, like seed node(s) and/or API node(s). You also need a backup server, preferrably in a different location, that can take over when your main server goes down.
For setting things up and proving yourself it would be advisable to run a testnet witness as well.
Thanks for that. May I ask what type of replication system on a different premises keeps a backup server in sync ? Could something like rsync be adequate to keep the witness state replicated ?
-
Your backup node should be kept running in hot standby, so it will keep itself in sync with the rest of the network.
You must configure it to use a different block production key though, to make sure that not both nodes are producing blocks at the same time.
-
Got it, thanks.
-
My goal is to enhance regional activity on Bitshares based platforms and provide low latency access. My witness is operational and I am working towards backup and public full/seed/API nodes before I submit my proposal. Any further input regarding approaches to facilitate the mentioned goal would be highly appreciated.
Draft proposal: http://www.viralmike.com/etienne-marais.php#top
-
Backup server/witness-node is now operational as well.
I have two separate chain running on the main server:
witness_node --rpc-endpoint=127.0.0.1:8090 --witness-id "1.6.96" --private-key ["<my public key>", "my private key"]
witness_node -d <my data dir> --rpc-endpoint=0.0.0.0:8091 --p2p-endpoint=0.0.0.0:1776
The seed node is open for rpc, but does not include plugin history configuration which I assume is needed to qualify as a full node.
The backup proposed witness node is running on the backup server:
witness_node --rpc-endpoint=127.0.0.1:8090 --witness-id '"1.6.96"' --private-key '["<different public key>", "<different private key>"]
Full node to follow on backup server.
If you feel like it, you can vote for me so long while I read up a bit more on what exactly constitutes a full node / API node / plugin history settings.
EDIT: It seems the default witness invocations cater for everything.
etienne-marais 1.6.96
www.viralmike.com/etienne-marais.php
-
Good people
My witness and hotswapable backup witnesses are running, as well as two separate public full nodes (pull requests done to add to codebase)
Full node1: wss://btsza.co.za:8091
Full node2: wss://btsbackup.dedicated.co.za:8091
Please vote for etienne-marais or scrutinize if need, and thanks to those who have already done so.
Proposal/information available here: www.viralmike.com/etienne-marais.php
-
Voted. And have a quick question. Do you have your price feeds up?
-
Voted. And have a quick question. Do you have your price feeds up?
Thank you.
No. What are the requirements around this, i.e. are non commercial feeds from the crypto world an adequate start ?
My plan is to set up an ZAR (South African Rand) asset and feed in the coming months.
-
Voted. And have a quick question. Do you have your price feeds up?
Thank you.
No. What are the requirements around this, i.e. are non commercial feeds from the crypto world an adequate start ?
My plan is to set up an ZAR (South African Rand) asset and feed in the coming months.
It is very unlikely that you will get on the active list until you have your price feeds up. Better get on it!
-
Been busy with it since this morning, was just about to inquire...
-
Witness set up as price feed, but bts monitor reports:
2017-12-29 18:16:33,592 WARNING [bts_tools.feeds:check_feeds:773] -- bts witness etienne-marais feeds: tried to publish all feeds in a single transaction, but failed. Will try to publish each feed separately now
2017-12-29 18:16:33,607 WARNING [bts_tools.feeds:check_feeds:789] -- bts witness etienne-marais feeds: Failed to publish feed for asset USD
and cli wallet running as daemon says:
Caught exception while broadcasting tx c7464b9185c58175f7dc7114ccc0782254bb8216: 0 exception: unspecified
missing required active authority: Missing Active Authority 1.2.401166
Config.yaml looks like this:
type: bts # [REQUIRED] build environment used for compiling the binary [bts, muse, steem, ppy, etc.]
data_dir: /datadir/bts/chain # [REQUIRED] the data dir of the client is where the blockchain data and the wallet file are stored
api_access: /datadir/bts/chain/api_access.json # [REQUIRED] api_access.json should be created according to https://github.com/BitShares/bitshares-2#accessing-restricted-apis
seed_nodes: # [OPTIONAL]
- bts-seed1.abit-more.com:62015
- seed.bitsharesnodes.com:1776
p2p_port: 1778 # [OPTIONAL] network port to be used for p2p communication of the witness node
track_accounts: # [OPTIONAL] [bts only] reduce RAM usage by specifying the only accounts that should be tracked
- 1.2.0 # witness-account
- 1.2.111226 # bittwenty
- 1.2.126782 # bittwenty.feed
witness_host: localhost # [OPTIONAL] defaults to 'localhost', but can be a remote host if desired
witness_port: 8090 # [OPTIONAL] some defaults are provided for each different chain
witness_user: etienne-marais # [REQUIRED] as in api_access.json
witness_password: <tried exactly as in generated json file, as well as the password used to create hash> # [REQUIRED] as in api_access.json
wallet_host: localhost # [OPTIONAL] defaults to 'localhost', but can be a remote host if desired
wallet_port: 8092 # [OPTIONAL] some defaults are provided for each different chain
wallet_password: # [OPTIONAL] only needed for feed publishing # FIXME: not true, currently unused param
notification: email #, telegram # [OPTIONAL] type of notification channel to be used: [email, boxcar, telegram]
# roles are optional, and you can have as many as you want for a given client
# a client that doesn't define any role will not be monitored by the web interface,
# but can still be used for building and running a client
roles:
-
role: witness
name: etienne-marais # [REQUIRED] name of the witness account on the blockchain
witness_id: 1.6.96 # [REQUIRED]
signing_key: <private key used in witness > # [REQUIRED] private key used by this witness for signing
-
role: feed_publisher
name: etienne-marais # [REQUIRED] name of the account that publishes the feed on the blockchain
-
role: seed
name: seed77 # [REQUIRED] name has no relevance for seed nodes, except for identifying them in the UI
# most of the clients try to have sensible defaults as much as possible, but you
# need to specify at least: type, data_dir, api_access, witness_user, witness_password
-
you are only allowed to post feeds when you're active
-
That's kind of circular :P
-
Join the telegram channel for witnesses if you haven't already.
-
Thank you to everybody has voted so far.
Price feed is ready as of yesterday and I am looking forward to get actively involved.
-
I will eventually post in a separate thread, but I have had a look at UI related issues on GitHub. My initial intent was to get involved with existing trading platforms but I fear that my perception of how user experience and UI layout should be adapted, especially with an understanding of the local potential market's character, may require a fork of the windows trading platform and redesign some UI features from the ground up. Would another trading platform be detrimental to rate of development and improvement of the existing or beneficial (especially considering existing other separate projects in development) ?
-
After some consideration I have decided to withdraw my witness proposal. I think the existing witnesses are well established with members very active in the community and high levels of contribution. I will not be able to spend that amount of time on development and activity.
I do however propose incentive for running a full node, to the degree of covering server fees and a bit. If this should happen I will happily return and get involved to some degree if I can contribute.
-
:-( Please reconsider. You have shown initiative, you have the skills, and you seem to quickly grasp how things work. I'd say we have active witnesses in the list who lack in more than of these regards. We need more witnesses than we have, and the pay is quite generous.
I know the lobbying part sucks for technically oriented people. And it's especially difficult for newcomers. But be persistent - all it takes is to convince some of the voting proxies. I've already voted for you.
-
Just saw this and voted. @etienne_marais are you still around? Please contact @xeroc for more votes.
-
Thanks people, I will give it another go and do some canvassing.
-
you just got my vote ... sorry for being late to the show :-D
-
Thank You.
-
Join the telegram channel for witnesses if you haven't already.
What is the URL for this witness channel?
-
Join the telegram channel for witnesses if you haven't already.
What is the URL for this witness channel?
Tell us more info about your, and/or contribute more, then people will invite you.
-
Hey there Etienne,
I am writing you today as member of the BitShares UI team. We are updating node descriptions and I believe these ones are run by you?
{url: "wss://blockzms.xyz/ws", location: "USA"},
Could you please provide me with an update to that a la
https://github.com/bitshares/bitshares-ui/issues/1521
Thanks in advance,
Stefan