BitShares Forum
Main => Stakeholder Proposals => Topic started by: tiancaomei088 on September 14, 2020, 06:45:07 am
-
witness name : witness.hope
API node : wss://bts.8a8e.com:8889
Introduction :
Hello members of Bitshares . I am witness.hope, five years web developers , from Beijing. I hope to help bitshares network more safe and stable .
Main Witness Server
CPU Cores: 8
RAM: 32G
Disk SPACE : 500G
Connection: 2 Gps
Backup Witness Server
CPU Cores: 8
RAM: 32G
Disk SPACE: 500G
Connection: 2 Gbps
Full API Node:
CPU Cores :8
RAM: 32G
Disk Space : 500G SSD
Location : Beijing
Connection: 10Mbits
My plan for witness:
* Follow community consensus and implement voting results.
* Produce blocks stable to help the blockchain network safe.
* Feed price correctly : Zapata's bitshares-pricefeed script will be used for feeding price .I can handle Price threshold(BSIP76) and Loopholes protection(BAIP2) properly . Although pricefeed work is not witness' job at present ,I am always ready.
* Maintain a better connection API . Stable and easy to use .
-
witness name : witness.hope
API node : wss://bts.8a8e.com:8889
Introduction :
Hello members of Bitshares . I am witness.hope, five years web developers , from Beijing. I hope to help bitshares network more safe and stable .
Main Witness Server
CPU Cores: 8
RAM: 32G
Disk SPACE : 500G
Connection: 2 Gps
Backup Witness Server
CPU Cores: 8
RAM: 32G
Disk SPACE: 500G
Connection: 2 Gbps
Full API Node:
CPU Cores :8
RAM: 32G
Disk Space : 500G SSD
Location : Beijing
Connection: 10Mbits
My plan for witness:
* Follow community consensus and implement voting results.
* Produce blocks stable to help the blockchain network safe.
* Feed price correctly : Zapata's bitshares-pricefeed script will be used for feeding price .I can handle Price threshold(BSIP76) and Loopholes protection(BAIP2) properly . Although pricefeed work is not witness' job at present ,I am always ready.
* Maintain a better connection API . Stable and easy to use .
Welcome.
Why witness nodes has 2G connections but API node only 10M? Actually API nodes need higher bandwidth than producing nodes to work.
Please try a testnet witness too. Register your account at https://test.xbts.io/
-
Witness Server is located in San Francisco and Singapore. The bandwith is shared. API node is in Beijing ,10M is exclusive bandwidth.
witness name : witness.hope
API node : wss://bts.8a8e.com:8889
Introduction :
Hello members of Bitshares . I am witness.hope, five years web developers , from Beijing. I hope to help bitshares network more safe and stable .
Main Witness Server
CPU Cores: 8
RAM: 32G
Disk SPACE : 500G
Connection: 2 Gps
Backup Witness Server
CPU Cores: 8
RAM: 32G
Disk SPACE: 500G
Connection: 2 Gbps
Full API Node:
CPU Cores :8
RAM: 32G
Disk Space : 500G SSD
Location : Beijing
Connection: 10Mbits
My plan for witness:
* Follow community consensus and implement voting results.
* Produce blocks stable to help the blockchain network safe.
* Feed price correctly : Zapata's bitshares-pricefeed script will be used for feeding price .I can handle Price threshold(BSIP76) and Loopholes protection(BAIP2) properly . Although pricefeed work is not witness' job at present ,I am always ready.
* Maintain a better connection API . Stable and easy to use .
Welcome.
Why witness nodes has 2G connections but API node only 10M? Actually API nodes need higher bandwidth than producing nodes to work.
Please try a testnet witness too. Register your account at https://test.xbts.io/
-
Updated Witness and Node API to 5.0
-
witness name : witness.hope
API node : wss://bts.8a8e.com:8889
Please submit your API info to Github, edit the file https://github.com/bitshares/bitshares-ui/blob/develop/app/api/apiConfig.js and create a pull request.