Author [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: *.bitdelegate - introduction, purpose, status and updates  (Read 785 times)

0 Members and 1 Guest are viewing this topic.

Offline emski

  • Hero Member
  • *****
  • Posts: 1283
    • View Profile
    • http://lnkd.in/nPbhxG
*.bitdelegate - introduction, purpose, status and updates
« on: October 09, 2014, 08:44:50 PM »

My name is Emil Velichkov (https://www.linkedin.com/in/emilvelichkov).
Together with Konstantin Krustev (https://www.linkedin.com/in/konstantinkrastev) we are responsible for development, maintenance and security of *.bitdelegate and some seed nodes.
Since we heard about III (december 2013) we immediately realized the potential of the concept and the (un)imaginable possible applications of DAC(s).
We haven't stopped mining Bitshares-PTS with all the GPUs we have (except for 2x GTX 780 which do pretty good job for gaming) even though it is not profitable anymore.

We have set up 2 facilities about 20 km apart with high speed fiber-optic internet (100mbit upload and 100mbit download), backup internet connection with similar capabilities but different ISP. UPS and dedicated high-end hardware (Each server has Quad Core CPU,32GB RAM, SSD, HDDs in HW Raid). We have split the delegates into these 2 locations. Each location backs the other one. We have also backups on the cloud.

Currently we are hosting:
BitsharesX delegates:

angel.bitdelegate  (Active, 3%)  -  Its income is intended to be used to fund projects beneficial for Bitshares ecosystem.
immortal.bitdelegate  (Active, 3%)  -  Its income is intended to be used for maintenance and development of delegates/seed nodes and anything needed for Bitshares ecosystem. The goal is to provide seed node(s) and delegates for any new or small project related to Bitshares.
lotto.bitdelegate  (Active, 3%)  -  I'll shut it down when it is voted out:https://bitsharestalk.org/index.php?topic=5368.msg106083#msg106083. All the funds will be distributed via lottery.
emski.bitdelegate  (Active, 3%)  -  I'll use it for testing the new versions before updating other delegates. Current experience I have is that updating as soon as the update is released results in instability and missed blocks and/or forks.
Seed node 84.238.140.192:42577 ( Active )


Bitshares2 Witness
emski (active, not voted in)
seed node 84.238.140.192:42570


All delegates use the version published without any code modifications. Feeds are provided by the script I presented here - https://bitsharestalk.org/index.php?topic=9698.0

How the funds gathered so far are spent: I haven't used "wallet_delegate_withdraw_pay" except in the test networks.

I'll provide dedicated hosting to any project beneficial to Bitshares ecosystem (free of charge as long as I have sufficient resources left and its requirements are sane) PM me or write here for requests.

Any changes will be added to this post. Any updates will be posted in this thread.

Devshares:
Seed node 46.10.205.0:32123 (dvsseed.bitdelegate.org:32123) ( Active )

emski ( Active, not voted in, 20% ) - used for testing.


Bitshares 1.0 Lotto delegate funds 39,341.00 BTS . Distribution via lottery is still pending as the sum is insignificant.

EDIT1:Removed KeyID delegates and seed info post feb 5th snapshot.
EDIT2:Strikeout PTS Mining post feb 5th snapshot.
EDIT3:Added delegate pay
EDIT4:Added devshares seed and delegate. "Strikeout" purpose of delegates as their pay was reduced to 3%
EDIT5:Removed bitshares1.0 delegates and descriptions. Added information about lotto delegate funds.
EDIT6:Removed BTS2.0 seed and witness as they are now inactive.
« Last Edit: January 11, 2016, 08:57:18 AM by emski »

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12280
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BTS: xeroc
  • GitHub: xeroc
Re: *.bitdelegate - introduction, purpose, status and updates
« Reply #1 on: October 11, 2014, 06:53:40 PM »
We have set up 2 facilities about 20 km apart with high speed fiber-optic internet (100mbit upload and 100mbit download), backup internet connection with similar capabilities but different ISP. UPS and dedicated high-end hardware (Each server has Quad Core CPU,32GB RAM, SSD, HDDs in HW Raid). We have split the delegates into these 2 locations. Each location backs the other one. We have also backups on the cloud.
much impressive .. very Wow ..

+5% .. If think you already are on my slate list .. 8)
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline cube

  • Hero Member
  • *****
  • Posts: 1404
  • Bit by bit, we will get there!
    • View Profile
  • BTS: bitcube
  • Witness: bitcube
Re: *.bitdelegate - introduction, purpose, status and updates
« Reply #2 on: October 12, 2014, 11:42:30 AM »
A good intro.   +5%

I saw your post numerous time but now I get to know you better. 
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

Offline emski

  • Hero Member
  • *****
  • Posts: 1283
    • View Profile
    • http://lnkd.in/nPbhxG
Re: *.bitdelegate - introduction, purpose, status and updates
« Reply #3 on: October 30, 2014, 09:38:12 AM »
My primary ISP decided to do an unplanned "maintenance" at 2:15 - 3:30 AM again.
Few issues were exposed:
1 Both locations use the same primary ISP. If its international connection is down => everything is down.
2 Automatic ISP switching didn't work as expected.
3 Notification system is unreliable if I'm asleep.

I'll see what I can do to improve these issues.

 

Google+