Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - sahkan

Pages: 1 ... 7 8 9 10 11 12 13 [14] 15 16 17
196
Technical Support / Re: light wallet connectivity issues
« on: April 30, 2017, 02:56:47 am »
You can also add my latest build:
wss://dexnode.net/ws

197
Stakeholder Proposals / Re: [Witness Proposal] sahkan-bitshares
« on: April 30, 2017, 02:54:49 am »
[29 APR 17] sahkan-bitshares Witness Update:

Witness Server Performance:
24 Core, 64GB, 240GB SSD


Price feeds:
bitEUR/BTS, bitNZD/BTS, bitAUD/BTS, bitCNY/BTS, bitJPY/BTS, TUSD/BTS, bitBTC/BTS, bitSGD/BTS, bitKRW/BTS,  bitARS/BTS, CASH.USD/BTS, bitGBP/BTS, bitTRY/BTS, bitCHF/BTS, ALTCAP/bitBTC, bitHKD/BTS, bitCAD/BTS, bitSILVER/BTS, RUBLE/BTS, bitUSD/BTS, bitGOLD/BTS,, bitMXN/BTS, BTWTY/BTS

Seed:
Currently 8 Core, 16GB RAM, 2TB HDD

I have added another dedicated server:
Dallas, TX - 16 core, 96GB RAM, 1TB HDD

It's a full node and provides an additional access point to DEX:
https://dexnode.net

You can check the SSL rating here: https://www.ssllabs.com/ssltest/analyze.html?d=dexnode.net

If you are running a light wallet and would like to connect to it, you can  go to SETTINGS, ACCESS, ADD API and add: wss://dexnode.net/ws

To do (next few days):
- Test xeroc's new price feed script
- Add a professional price feed, please contribute to this topic: https://bitsharestalk.org/index.php/topic,24006.0.html
- Add a seed node Done, added a seed node on 30 APR 17 - 23.92.53.182:1776 - VPS, 4 cores, 18GB RAM, 90GB SSD
- Upgrade my Hawaii seed

Note to other witnesses: If you want my vote just reply here or PM me your witness server specs: number of cores, ram, disk size and how many seeds you run in addition to your main server. (Hint: your RAM needs to be 16GB or more)


198
General Discussion / Re: Witness pay framework
« on: April 30, 2017, 01:36:21 am »
Thom has some very good points. I will add a couple of things from my point of view:

Bare minimum:
The truth is that all you need is a home computer with 8GB RAM and some 8GB swap file and you can run a witness. You don't have to do anything else except for being voted in as active <-- very cheap and very crappy at the same time

What a witness should have (VPS/server running costs):
- a server can cost anywhere from around $1K to $3K
- Co-location costs around $80 to $200/month if you want something decent
- Dedicated Server $80 - $150
- VPS  about $60 & up/month if you want decent RAM

In my opinion an active witness should have at least 3 (I have 3 and will be adding more - one in May)

It costs BTS to do price feeds,  and here again the number of assets that witnesses post prices for vary because there is no set list that we should go off.

The more servers we have (I think Thom has 6) the more time it takes to maintain them. Some witnesses provide additional work for the community  and maintain other products.

I think it's important to build a capable network of Witness Node servers and the motivation should not be the witness pay. We just need more active witnesses capable of providing the backbone infrastructure for DEX. For example, in addition to the voted in witnesses I would like to see a Network select witness that's selected during the maintenance window based on his/her Server capabilities (connection, RAM etc.) - if there is a way to measure that properly. Because few proxy voters have not changed their votes for months some active witnesses feel very secure and provide very little feedback on their activities.

As far as the hours and monthly pay, lately I have been putting in a lot more than 5 hours but I am ok with your $400 as pay was not my motivation (and I suspect there are few others that share that opinion). If we can focus on improving DEX and adding traders, it will help us to generate higher income for DEX. At the same time based on the BTS reserves we should have a plan to decrease witness and worker pay to generate an overall profit and maybe create a dividend for all share holders. With the rising price of BTS we might be able to get there quicker.

199
Stakeholder Proposals / Re: Witness: delegate.ihashfury
« on: April 26, 2017, 06:10:40 pm »
We should look into getting our standby witnesses rotated in (like steem does), it would give everyone a chance to test drive their rigs and possibly improve our pool of witnesses.

200
I just updated to 0.4.10, but the asset does not have the "Witness fed asset" tag and since I am not on the list my RUBLE price feed is not being published.

It wasn't clear that you wish to publish price feeds, but we have 2 more places
I'll add you to the list

---
UPD

https://market.rudex.org/block/15999612

Few posts ago @alt asked you to change the flag on the asset so all active witnesses can do the price feed. I think it will be a better solution than trying to lock it in to a specific group of people. I think it would be a better long term solution.

201
Technical Support / Setting Up a Price Feed [BTS Tools]
« on: April 25, 2017, 11:23:17 pm »
Setup your Ubuntu server:
https://bitsharestalk.org/index.php/topic,24005.0.html

Setup your bitShares node:
https://bitsharestalk.org/index.php/topic,23925.0.html

I did some testing, reading and browsing through different price feed scripts and ended up picking wackou's BTS Tools.
Here are some of the options:
Latest by xeroc: https://github.com/xeroc/bitshares-pricefeed
This one by Alt: https://pypi.python.org/pypi/btsprice
And wackou's BTS Tools:  https://pypi.python.org/pypi/bts_tools/0.4.10

You will need to create an api access file for BTS Tools to interact with your node so let's start with that:

SSH to your server
You will need to get a hash for your witness' password:
Code: [Select]
$ python bitshares-core/programs/witness_node/saltpass.py
enter your password (for example: supersecret) and you will get your hash & salt, like so:
 {
            "password_hash_b64" : "9e9GF7ooXVb9k4BoSfNIPTelXeGOZ5DrgOYMj94elaY=",
            "password_salt_b64" : "INDdM6iCi/8="
  }


Now move back to the directory where you want your api access file to be at, for example your home directory:
Code: [Select]
$cd
Create your api access file:
Code: [Select]
$nano api_access.jsonEnter:
{
   "permission_map" :
   [
      [
         "YOUR_WITNESS_NAME",
         {
            "password_hash_b64" : "9e9GF7ooXVb9k4BoSfNIPTelXeGOZ5DrgOYMj94elaY=",
            "password_salt_b64" : "INDdM6iCi/8=",
            "allowed_apis" : ["database_api", "network_broadcast_api", "history_api", "network_node_api"]
         }
      ]
   ]
}


Save & Exit.

Edit the node config file and add the location for your api access file:
Code: [Select]
$nano bitshares-core/witness_node_data_dir/config.ini
find:
api-access =
and modify:
api-access = /home/muLinuxUser/api_access.json

Save & exit

Installing BTS Tools:
Install dependencies:
Code: [Select]
$sudo apt-get install build-essential libyaml-dev python3-dev python3-pip
Install tools:
Code: [Select]
$ pip3 install bts_tools
Verify installed version: (it should also create a default config.yaml file for you):
Code: [Select]
$bts - version
Edit your config.yaml file:
Code: [Select]
$nano .bts_tools/config.yaml# For a more detailed description of the format of this file, visit:
# https://bts-tools.readthedocs.io/en/latest/config_format.html
#

# (OPTIONAL) will show this hostname as the source of notification messages
hostname: <your-host-name>

# the logging levels for the different submodules
# can be any of DEBUG, INFO, WARNING, ERROR
logging:
    bts_tools.feeds: INFO

# flags to be passed to make; shared among all build environments
make_args: ['-j4']

#
# list of clients (witness accounts / seed nodes) that are being monitored
#
clients:
    bts:
        type: bts
        data_dir: ~/.BitShares2
        witness_host: localhost
        witness_port: 8090
        # api_access.json should be created according to:
        # https://github.com/BitShares/bitshares-2#accessing-restricted-apis
        witness_user: YOUR_WITNESS      # as in api_access.json
        witness_password: supersecret  # as in api_access.json
        wallet_host: localhost
        wallet_port: 8093
        wallet_password: changeme!  # only needed for feed publishing
        notification: email
        roles:
        -
            role: witness
            name: xxxxxxxxx
            witness_id: 1.6.xxxx
            signing_key: 5xxxxxxxx
        -
            role: feed_publisher
            name: xxxxxxxx
 
#
# configuration of the monitoring plugins
# global default when not overriden by a role's specific params
#
monitoring:
    seed:
        desired_number_of_connections: 200
        maximum_number_of_connections: 400

    feeds:
        enabled_assets: [RUBLE, BTWTY, ALTCAP]
        disabled_assets: [RUB, SEK, GRIDCOIN, TCNY, CASH.BTC]  # black swan
        check_time_interval: 300
        median_time_span: 1800
        #publish_time_interval: 2400         # use this to publish feeds at fixed time intervals (in seconds)
        #publish_time_slot: 0                # use this to publish every hour at a fixed number of minutes (in minutes)
        feed_providers: [Poloniex, Btc38, Yunbi,    # BTS valuation
                         Yahoo, Google, Bloomberg]  # market indices

#
# configuration of the notification channels
#
notification:
    email:
        smtp_server: smtp.example.com
        smtp_user: user
        smtp_password: secret-password
        identity: "BTS Monitor <bts_monitor@example.com>"
        recipient: me@example.com

    boxcar:
        tokens: []

    telegram:
        token: 'xxxxxxxxxxxxxxxx'
        chat_id: 12341234


Save & exit
For production deployments, it is recommended to put it behind a WSGI server, in which case the entry point is bts_tools.wsgi:application
You can set it up according to wackou's docs:
https://bts-tools.readthedocs.io/en/latest/monitor.html

Start your witness node,
Start CLI, unlock it and import feed key for BTS Tools:
Code: [Select]
import_key "announce" 5KJJNfiSyzsbHoVb81WkHHjaX2vZVQ1Fqq5wE5ro8HWXe6qNFyQ
verify your signing key and witness info:
Code: [Select]
get_witness YOUR_WITNESS_NAME
run the BTS Tools monitor:
Code: [Select]
$bts monitor
and you are all set!

To update your BTS Tools to a new version:
Stop the monitor (CTRL-C) and upgrade:
Code: [Select]
$pip3 install --upgrade bts_tools
Edit config.yaml and adjust as required

Restart the monitor:
Code: [Select]
$bts monitor













202
I just updated to 0.4.10, but the asset does not have the "Witness fed asset" tag and since I am not on the list my RUBLE price feed is not being published.

203
Please, invest in badass api nodes, raise the standarts. There is not much to choose from and it is super frustrating seeing init error.

Witnesses do not provide api nodes. They could of course do so as an additional service to justify their current high pay, but it's not part of the job description.

I have been providing an api node ( wss://altcap.io/ws ) and web wallet ( altcap.io ) for some considerable time.


I appreciate it, wish more witnesses did

I am planning to add another server this week and will work on price feeds and additional services for the community. (planning to have an update first week of May)

204
Technical Support / Re: Setting Up a New Witness Node
« on: April 22, 2017, 02:21:38 am »
@JonnyBitcoin
Thanks! I appreciate your confidence and the tip. You can have my votes as well if you ever need them.

@rnglab
The websocket exposure was only during the initial synch (per the docs guide) but I will skip it on my next build. Thank you.

So the 8GB was an initial recommendation I found browsing through the forum. My build uses 16GB and it's pushing its limit. I am looking at 32GB for my final build (aiming at a 2 year life cycle)

@alt
I meant this threat to be a guide for people to help secure the network, I am not even soliciting anything. I will write my witness proposal later when I get done tuning it and get the final build.
But I guess there is always a hater so to answer you quickly:
- about 'bue' - I like swiss cheese
- Running a witness is a RESPONSIBILITY and I would think that it is in community's interest to build a pool of capable witnesses, both active and standby
- If you keep hating on every new comer, you will not be able to grow this community
- and as far as the active witnesses go, they are mostly voted in by two people only
Feel free to look me up on https://bitcointalk.org or https://talk.peercoin.net/


@tbone
Thanks
sorry I just saw this today.
and you have my support
I am not hate for newcomer, I just need be carefully, because I have saw so many scam happened in Bitshares

Great, thank you. Let's take it to the next level together, it will be good for everyone!  8)

205
DEX is build on BitShares and therefore I think witnesses should be paid in BTS (witnesses pay for price feeds in BTS). But maybe we can come up with a 30 or 45 day moving average for BTS:USD price and the Committee can adjust the BTS pay as required. But I've said all along that witnessing should not be a business but responsibility to the community, so witnesses are maintaining infrastructure because their business relays on DEX not because they want to get paid as witnesses. We should lower the witness pay as the BTS:USD price goes up so the BTS reserve stops declining and we can continue to maintain DEX as designed.

206
Stakeholder Proposals / Re: [Witness Proposal] roelandp
« on: April 19, 2017, 11:54:59 pm »
    Great proposal!

    Your price feed script has only:
    • Livecoin
    • Liqui
    • Bittrex
    • Kuna

    and I see you are working on Poloniex. Do you plan to add other feeds to cover MPAs?
    [/list]

    Hi @sahkan thank you for notifiying. As I mentioned that was a sample of code I supplied to other graphene communities. In this case Golos. Being a Golos witness means supplying a dedicated Golos feed to the Golos blockchain. The Golos coin was only listed on those 4 exchanges. (Now only on 3 for the moment). Hence that specific pricescript only has those exchanges incorporated.

    Re: your question:
    I currently plan to use @xeroc 's pricefeed script which I have tested but can not publish the feeds which are only for active witnesses. If you check Bitshares overview you will notice that I currently publish ALTCAP.XDR. This is a script I codereviewed from @iHashFury and intend to have that 'manual' script for more MPA's yes.
    I don't want to saturate your proposal here, but I am trying to get a grip on this price feeding so we can get some governance and guidance that all witnesses are willing to follow. A list of required price feeds should be one of them. Please provide some feedback at https://bitsharestalk.org/index.php/topic,24006.0.html Thanks!

    207
    Stakeholder Proposals / Re: [Witness Proposal] roelandp
    « on: April 19, 2017, 06:07:06 pm »
      Great proposal!

      Your price feed script has only:
      • Livecoin
      • Liqui
      • Bittrex
      • Kuna

      and I see you are working on Poloniex. Do you plan to add other feeds to cover MPAs?
      [/list]

      209
      General Discussion / Re: Non Voting Accounts
      « on: April 18, 2017, 08:37:41 pm »
      Thank you, that's what I was looking for.

      210
      Stakeholder Proposals / Re: [Witness Proposal] openledger-dc
      « on: April 18, 2017, 03:06:13 pm »
      You already got my vote. The workload is increasing on the witnesses and we need a future-ready infrastructure.

      Pages: 1 ... 7 8 9 10 11 12 13 [14] 15 16 17