Author Topic: Delegate Bandwidth Requirements  (Read 1714 times)

0 Members and 1 Guest are viewing this topic.

Offline bytemaster

yep .. but that currently is not supported yet .. afaik ...
but you still need to be connected to receive the transactions ..

just don't send out blocks if asked for ..

I'll have to watch for that block thing.  Depending on how transactions fees mount up and considering I'm only at 5%....time will tell. Though if this takes off I don't mind paying a few hundred a month to support the network.

If you run behind a firewall where no one can connect to you then you will have lower bandwidth requirements.   The influx of new users is certainly taxing public nodes.
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline Riverhead

yep .. but that currently is not supported yet .. afaik ...
but you still need to be connected to receive the transactions ..

just don't send out blocks if asked for ..

I'll have to watch for that block thing.  Depending on how transactions fees mount up and considering I'm only at 5%....time will tell. Though if this takes off I don't mind paying a few hundred a month to support the network.

« Last Edit: August 21, 2014, 06:33:49 pm by Riverhead »

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
yep .. but that currently is not supported yet .. afaik ...
but you still need to be connected to receive the transactions ..

just don't send out blocks if asked for ..

Offline Riverhead

if you were to only enable
+ block production
+ receiving of transaction

you might produce less data. I guess the (current) high demand in new users loading the blockchain vs. the low number of early runners/delegates is the reason for this


You mean turning myself off as a node?


Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
if you were to only enable
+ block production
+ receiving of transaction

you might produce less data. I guess the (current) high demand in new users loading the blockchain vs. the low number of early runners/delegates is the reason for this

Offline Riverhead


We are in a fairly low transaction count period due to the market being closed.  That said it looks like we're currently using about 160,000 bytes/sec which translates into about 0.38TB/m of data transfer. Does anyone have any estimates of transfer requirements once we are live? 3TB/m at Digital Ocean is $20/month. Double the transfer cap double the price. 6TB/$40/m, etc.


I guess I can switch Droplets as usage dictates. If you snapshot and destroy a droplet you aren't charged for it.

Code: [Select]
by hour:
   *                  298504 bytes/sec
   *                  270194 bytes/sec
   *                  241884 bytes/sec
   *                  213574 bytes/sec
   *            * * * 185264 bytes/sec
   * **         *** * 156954 bytes/sec
  ** ***       ****** 128644 bytes/sec
 ********* * ******** 100334 bytes/sec
 *********** ******** 72024 bytes/sec
********************* 43714 bytes/sec
« Last Edit: August 21, 2014, 06:03:35 pm by Riverhead »