Author Topic: please vote for witness : ioex  (Read 734 times)

0 Members and 1 Guest are viewing this topic.

Offline ioex.henry

  • Full Member
  • ***
  • Posts: 64
    • View Profile
  • BitShares: ioex
please vote for witness : ioex
« on: May 22, 2019, 05:25:06 am »
Hello,Some days ago,ioex became active witness,only gave several feedprice , but could not produce blocks , because long time standby , I destoryed the node.

These days  I rebuild my witness node , So hope you vote me , let me active, thanks .

Offline ioex

  • Full Member
  • ***
  • Posts: 195
    • View Profile
Re: please vote for witness : ioex
« Reply #1 on: May 22, 2019, 05:26:19 am »

Online sschiessl

Re: please vote for witness : ioex
« Reply #2 on: May 22, 2019, 07:39:53 am »
Can you please provide a testnet witness to join latest development efforts and a public API node for reference UI?

Offline ioex

  • Full Member
  • ***
  • Posts: 195
    • View Profile
Re: please vote for witness : ioex
« Reply #3 on: May 22, 2019, 07:48:44 am »
Can you please provide a testnet witness to join latest development efforts and a public API node for reference UI?
I tried to start a testnet witness , but failed at 6690000-6700000 blocks.
And I tried again by a VPS with 100M bandwidth  12CPU 24G Memory ,after more than 8 hours , finally failed.

Online sschiessl

Re: please vote for witness : ioex
« Reply #4 on: May 22, 2019, 08:38:25 am »
Can you please provide a testnet witness to join latest development efforts and a public API node for reference UI?
I tried to start a testnet witness , but failed at 6690000-6700000 blocks.
And I tried again by a VPS with 100M bandwidth  12CPU 24G Memory ,after more than 8 hours , finally failed.

Valuable lessons learned from running on testnet. If that would happen on mainnet you also wouldn't just stop, would you? :)

Offline ioex

  • Full Member
  • ***
  • Posts: 195
    • View Profile
Re: please vote for witness : ioex
« Reply #5 on: May 22, 2019, 08:47:27 am »
Can you please provide a testnet witness to join latest development efforts and a public API node for reference UI?
I tried to start a testnet witness , but failed at 6690000-6700000 blocks.
And I tried again by a VPS with 100M bandwidth  12CPU 24G Memory ,after more than 8 hours , finally failed.

Valuable lessons learned from running on testnet. If that would happen on mainnet you also wouldn't just stop, would you? :)

This issues mainly cause by the big blocks ( 10000 continues blocks are big blocks ) because at that time execute a performance test on testnet .

On mainnet ,nodes handle blocks one by one , will not meet these problems.

Online sschiessl

Re: please vote for witness : ioex
« Reply #6 on: May 22, 2019, 09:13:05 am »
Can you please provide a testnet witness to join latest development efforts and a public API node for reference UI?
I tried to start a testnet witness , but failed at 6690000-6700000 blocks.
And I tried again by a VPS with 100M bandwidth  12CPU 24G Memory ,after more than 8 hours , finally failed.

Valuable lessons learned from running on testnet. If that would happen on mainnet you also wouldn't just stop, would you? :)

This issues mainly cause by the big blocks ( 10000 continues blocks are big blocks ) because at that time execute a performance test on testnet .

On mainnet ,nodes handle blocks one by one , will not meet these problems.

I find that poor reasoning. Testnet participation is a must if you ask me.

Offline ioex.henry

  • Full Member
  • ***
  • Posts: 64
    • View Profile
  • BitShares: ioex
Re: please vote for witness : ioex
« Reply #7 on: May 22, 2019, 12:28:58 pm »
Can you please provide a testnet witness to join latest development efforts and a public API node for reference UI?
I tried to start a testnet witness , but failed at 6690000-6700000 blocks.
And I tried again by a VPS with 100M bandwidth  12CPU 24G Memory ,after more than 8 hours , finally failed.

Valuable lessons learned from running on testnet. If that would happen on mainnet you also wouldn't just stop, would you? :)

This issues mainly cause by the big blocks ( 10000 continues blocks are big blocks ) because at that time execute a performance test on testnet .

On mainnet ,nodes handle blocks one by one , will not meet these problems.

I find that poor reasoning. Testnet participation is a must if you ask me.

now the testnet witness is ready too, please vote testnet witness: ioex-test

Offline ioex.henry

  • Full Member
  • ***
  • Posts: 64
    • View Profile
  • BitShares: ioex
Re: please vote for witness : ioex
« Reply #8 on: May 26, 2019, 03:07:58 pm »
If I am an active witness , this is my feed log :

Quote
2019-05-26 19:37:34,739 - __main__- 122 - INFO -  so my feed price cny : 0.4485422
2019-05-26 19:57:38,234 - __main__- 122 - INFO -  so my feed price cny : 0.44797832771693347
2019-05-26 20:17:40,485 - __main__- 122 - INFO -  so my feed price cny : 0.4477568872145044
2019-05-26 20:37:44,802 - __main__- 122 - INFO -  so my feed price cny : 0.4512924058397743
2019-05-26 20:57:47,472 - __main__- 122 - INFO -  so my feed price cny : 0.4533640210006176
2019-05-26 21:17:50,866 - __main__- 122 - INFO -  so my feed price cny : 0.4519275512253917
2019-05-26 21:37:56,192 - __main__- 122 - INFO -  so my feed price cny : 0.4516390430524383
2019-05-26 21:57:59,904 - __main__- 122 - INFO -  so my feed price cny : 0.45617125468164793
2019-05-26 22:18:04,215 - __main__- 122 - INFO -  so my feed price cny : 0.454606124093473
2019-05-26 22:38:10,143 - __main__- 122 - INFO -  so my feed price cny : 0.45523011229009996
2019-05-26 22:58:14,776 - __main__- 122 - INFO -  so my feed price cny : 0.4556626461121464