Author Topic: BitShares 2 Release Coordination Thread  (Read 32037 times)

0 Members and 1 Guest are viewing this topic.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
I think it should be ok to release some basic network/hosting information as long as they dont allow others to identify you machine


Edit: keeping all information 'secret' will not help shareholders decide

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4627
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
//Edit: missed blocks due to latency issue

Code: [Select]
2015-10-24T09:50:24 th_a:invoke handle_block         handle_block ] Got block: #306412 time: 2015-10-24T09:50:24 latency: 344 ms from:
 delegate.ihashfury  irreversible: 306386 (-26)                   application.cpp:496
2015-10-24T09:50:30 th_a:Witness Block Production block_production_loo ] Generated block #306413 with timestamp 2015-10-24T09:50:30 at
 time 2015-10-24T09:50:30                 witness.cpp:179
2015-10-24T09:50:30 th_a:invoke handle_block         handle_block ] Got block: #306413 time: 2015-10-24T09:50:27 latency: 3422 ms from
: verbaltech2  irreversible: 306387 (-26)                 application.cpp:496
2015-10-24T09:50:33 th_a:invoke handle_block         handle_block ] Got block: #306414 time: 2015-10-24T09:50:33 latency: 374 ms from:
 wackou  irreversible: 306387 (-27)                       application.cpp:496
2015-10-24T09:50:33 th_a:invoke handle_block          _push_block ] Switching to fork: 0004acee321e2d9ba26852c24af99e9a6d826bed
                db_block.cpp:137
2015-10-24T09:50:33 th_a:invoke handle_block          _push_block ] pushing blocks from fork 306413 0004aced9d269bbd0bb17fa02cbbe7f16262ff23                    db_block.cpp:147
2015-10-24T09:50:33 th_a:invoke handle_block          _push_block ] pushing blocks from fork 306414 0004acee321e2d9ba26852c24af99e9a6d826bed                    db_block.cpp:147
2015-10-24T09:50:36 th_a:invoke handle_block         handle_block ] Got block: #306415 time: 2015-10-24T09:50:36 latency: 345 ms from: dele-puppy  irreversible: 306388 (-27)                   application.cpp:496

And earlier another:
Code: [Select]
2015-10-24T03:25:00 th_a:invoke handle_block         handle_block ] Got block: #298723 time: 2015-10-24T03:25:00 latency: 551 ms from:
 mindphlux.witness  irreversible: 298700 (-23)                    application.cpp:496
2015-10-24T03:25:06 th_a:Witness Block Production block_production_loo ] Generated block #298724 with timestamp 2015-10-24T03:25:06 at
 time 2015-10-24T03:25:06                 witness.cpp:179
2015-10-24T03:25:06 th_a:invoke handle_block         handle_block ] Got block: #298724 time: 2015-10-24T03:25:03 latency: 3723 ms from
: rnglab  irreversible: 298701 (-23)                      application.cpp:496
2015-10-24T03:25:09 th_a:invoke handle_transaction   handle_transaction ] Got 1 transactions from network                       applic
ation.cpp:545
2015-10-24T03:25:10 th_a:invoke handle_block         handle_block ] Got block: #298725 time: 2015-10-24T03:25:09 latency: 1010 ms from
: delegate-1.lafona  irreversible: 298701 (-24)                   application.cpp:496
2015-10-24T03:25:10 th_a:invoke handle_block          _push_block ] Switching to fork: 00048ee5fc659531b4974f3d9781a7a82be5625b
                db_block.cpp:137
2015-10-24T03:25:10 th_a:invoke handle_block          _push_block ] pushing blocks from fork 298724 00048ee4bee8781d6a7755ba09e9e71c1a0d1d8b                    db_block.cpp:147
« Last Edit: October 24, 2015, 07:17:21 pm by abit »
BitShares committee member: abit
BitShares witness: in.abit

Offline kenCode

  • Hero Member
  • *****
  • Posts: 2283
    • View Profile
    • Agorise
I and a number of witnesses have mentioned our node locations and hosting/non-hosting information in the Witness-only channels in Telegram and Slack.  Does mentioning of our node locations in this public forum become an attack vector and compromises the bts network security?  Are we giving the hackers, spammers, bad governments and other bad actors out there more information than we should?

agree. Do not post witness detail hosting information and vps location here?please use our telegram

Exactly. I think it would be wise to assume the worst. Assume the NSA, Mi5, hackerboy123, etc has bots already tracking and trying to penetrate from every angle, and don't rule out their tracing methods or social engineering either:
 
https://www.youtube.com/watch?v=3VlyZIywY9c
 
BitShares is going to change the world. Do not take our security lightly. 
1. One human should not control more than 1 Witness account. That human should not be friends or even geo-located near another Witness-controlling human.
2. Amazon controls many webhosting providers. Amazon should not have access to more than 1 Witness. (ie: who owns namecheap? who owns godaddy? who owns digital ocean? etc)
3. No more than 1 Witness should be physically hosted in 1 country.
kenCode - Decentraliser @ Agorise
Matrix/Keybase/Hive/Commun/Github: @Agorise
www.PalmPay.chat

Offline twitter

  • Sr. Member
  • ****
  • Posts: 279
    • View Profile
agree. Do not post witness detail hosting information and vps location here?please use our telegram
witness:

Offline cube

  • Hero Member
  • *****
  • Posts: 1404
  • Bit by bit, we will get there!
    • View Profile
  • BitShares: bitcube
I and a number of witnesses have mentioned our node locations and hosting/non-hosting information in the Witness-only channels in Telegram and Slack.  Does mentioning of our node locations in this public forum become an attack vector and compromises the bts network security?  Are we giving the hackers, spammers, bad governments and other bad actors out there more information than we should?
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4627
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
Missed a block today:
Code: [Select]
2015-10-23T13:40:34 th_a:Witness Block Production block_production_loo ] Not producing block because node didn't wake up within 500ms of the slot time.                 witness.cpp:197
2015-10-23T13:40:34 th_a:invoke get_blockchain_synopsis get_blockchain_synop ] synopsis: ["00044e96bc00dbac113a661f9fadf7ac48b7d9a1","00044ea3fbc78cd46ff1b8ae08d1f51cca560f42","00044ea9d2c1e249c9d2a772af24e361e3c0cc4e","00044eac93d30606ddecaf9f1556c2a22d00b482","00044eaed7842cd0729fbe9b67f0a874c5f6b2b4"]                       application.cpp:816
2015-10-23T13:40:35 th_a:Witness Block Production block_production_loo ] Not producing block because node didn't wake up within 500ms of the slot time.                 witness.cpp:197

//Edit:
My main node is in China. My own hardware. ISP is China Telecom.
« Last Edit: October 23, 2015, 08:19:47 pm by abit »
BitShares committee member: abit
BitShares witness: in.abit

Offline kenCode

  • Hero Member
  • *****
  • Posts: 2283
    • View Profile
    • Agorise
I agree with your decision 100% BM. DSN has always run my server for me, he is excellent. Decentralization is key however, so if he runs a Witness on his network, then I must move to a new webhost for my Witness.
Just curious, how many Witnesses are running their server at a company owned, or Partnered with Amazon?
Good point, decentralization includes a diversity of administrators and hardware/VPSes. I think everyone would happily switch VPS providers to ensure diversity.
Also, kencode, you should look into a worker proposal, I'd support your work.

Thank you @maqifrnswa :)
 
dragonball runs  on my own machine(s), not owned by any cloud service providers.

Who serves up the gateway to your router? Comcast? T-Mobile? __________?
 
Good info guys, we need to track this stuff somewhere. (a private, consensus-driven sidechain perhaps?)
« Last Edit: October 24, 2015, 09:57:32 am by kenCode »
kenCode - Decentraliser @ Agorise
Matrix/Keybase/Hive/Commun/Github: @Agorise
www.PalmPay.chat

Offline maqifrnswa

  • Hero Member
  • *****
  • Posts: 661
    • View Profile
Me: DO NYC3 with my own hardware for failover
maintains an Ubuntu PPA: https://launchpad.net/~showard314/+archive/ubuntu/bitshares [15% delegate] wallet_account_set_approval maqifrnswa true [50% delegate] wallet_account_set_approval delegate1.maqifrnswa true

Offline ffwong

  • Full Member
  • ***
  • Posts: 76
    • View Profile
  • BitShares: fftt
dragonball runs  on my own machine(s), not owned by any cloud service providers.
Cast me some votes. I am running:
- dragonball for Bitshares 2.0 net
- delegate.fftt for PTS (DPOS) net

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
I use so you start aws and digital ocean. 
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline maqifrnswa

  • Hero Member
  • *****
  • Posts: 661
    • View Profile
I agree with your decision 100% BM. DSN has always run my server for me, he is excellent. Decentralization is key however, so if he runs a Witness on his network, then I must move to a new webhost for my Witness.
 
Just curious, how many Witnesses are running their server at a company owned, or Partnered with Amazon?

Good point, decentralization includes a diversity of administrators and hardware/VPSes. I think everyone would happily switch VPS providers to ensure diversity.

Also, kencode, you should look into a worker proposal, I'd support your work.
maintains an Ubuntu PPA: https://launchpad.net/~showard314/+archive/ubuntu/bitshares [15% delegate] wallet_account_set_approval maqifrnswa true [50% delegate] wallet_account_set_approval delegate1.maqifrnswa true

Offline Spectral

Vote for BTS-2 witness: spectral (1.6.30)
0.9 DVS delegate: dvs1.bitspace
Stay tuned for bitspace-clains worker!

Offline mindphlux

  • Sr. Member
  • ****
  • Posts: 232
    • View Profile
Updated my witness this morning. Running fine.
Please consider voting for my witness mindphlux.witness and my committee user mindphlux. I will not vote for changes that affect witness pay.

Offline twitter

  • Sr. Member
  • ****
  • Posts: 279
    • View Profile
bue has been  updated to v2.15.294.

It was required --resync-blockchain  .... replay does not work... :)
witness:

Offline kenCode

  • Hero Member
  • *****
  • Posts: 2283
    • View Profile
    • Agorise
Voted for you.
Voted out kencode after seeing fav's post that his witness was being run by datasecuritynode and thus not actually providing any decentralization.

I agree with your decision 100% BM. DSN has always run my server for me, he is excellent. Decentralization is key however, so if he runs a Witness on his network, then I must move to a new webhost for my Witness.
 
Just curious, how many Witnesses are running their server at a company owned, or Partnered with Amazon?
kenCode - Decentraliser @ Agorise
Matrix/Keybase/Hive/Commun/Github: @Agorise
www.PalmPay.chat