Thank You.

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.

Thank you to everybody has voted so far.

Price feed is ready as of yesterday and I am looking forward to get actively involved.

Witness set up as price feed, but bts monitor reports:

Quote

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:

Quote

Caught exception while broadcasting tx c7464b9185c58175f7dc7114ccc0782254bb8216:  0 exception: unspecified
missing required active authority: Missing Active Authority 1.2.401166

Config.yaml looks like this:

Quote

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

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.

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

What is driving the rapid price increase ?

Trading volume seem to have picked up since 13/12

My full node is operational and running separately from my (to be) proposed witness: 41.185.20.18:8091 for client access and 41.185.20.18:1776 for seed access. Can somebody perhaps confirm if all seems in order?

How is a full node registered for discovery by bitshares based clients, i.e. as in Bitshares.171205 settings->access

Nuremberg, Germany
wss://bitshares.openledger.info/ws