Main Menu

BitShares Seed Nodes

Started by vikram, January 15, 2017, 10:24:48 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

R


knaperek

Quote from: hardinero007 on December 05, 2017, 07:34:55 AM
and what is the term duration in being a witness?  is it 1 month? 6 months?  or as long as they got the votes?
Your witness will be in service as long as it gets the votes. Each stakeholder can vote or withdraw their vote anytime and the votes are counted once each maintenance interval.

hardinero007

Quote from: sahkan on December 04, 2017, 06:05:32 PM
Quote from: hardinero007 on December 04, 2017, 05:51:49 PM
hi experts, my company has a server which is online 24/7 and have permanent ip address.  can we make this server also bitshares server?  what are the requirements to become a seed?  do seeds earn bts in return?
Only witness nodes get rewards.

thanks for reply.  i wonder how many witnesses do we have currently?  i guess only around 30-50?  and what is the term duration in being a witness?  is it 1 month? 6 months?  or as long as they got the votes?

sahkan

Quote from: hardinero007 on December 04, 2017, 05:51:49 PM
hi experts, my company has a server which is online 24/7 and have permanent ip address.  can we make this server also bitshares server?  what are the requirements to become a seed?  do seeds earn bts in return?
Only witness nodes get rewards.
DEX Access:  [url="https://dexnode.net/?r=sahkan-bitshares"]https://dexnode.net/?r=sahkan-bitshares[/url]

hardinero007

hi experts, my company has a server which is online 24/7 and have permanent ip address.  can we make this server also bitshares server?  what are the requirements to become a seed?  do seeds earn bts in return?

knaperek

Thanks for nice breakdown @sahkan. I've put it to table based on your definition.






RoleStores blockchainPublic RPCProvides blockchain via p2pGenerates blocksIncludes history plugins
Witness✔❌✔✔❌
Seed✔❌✔❌❌
Full node✔✔/ ❌✔❌✔

All roles are covered by the built-in witness_node program and the particular role is determined by configuration and environment implications.

Other opinions are welcome :-)

sahkan

Here are my definitions of BTS nodes:
Witness - Stores blockchain, limits CLI access to local port, provides p2p for blockchain downloads, generates blocks, and does not include history plugins
Seed - Stores blockchain, limits CLI access to local port, provides p2p for blockchain downloads, does not generate blocks, and does not include history plugins
Full node - Stores blockchain, opens CLI access to www (for the community) or limits it to local port (for example runs on your computer to provide fast wallet sync), provides p2p for blockchain downloads, does not generate blocks, and includes history plugins
DEX Access:  [url="https://dexnode.net/?r=sahkan-bitshares"]https://dexnode.net/?r=sahkan-bitshares[/url]

knaperek

Quote from: abit on November 18, 2017, 03:08:53 PM
In BitShares, seed nodes also serve as full nodes.
That means seed nodes are techically no different from full nodes; they are in fact just a subset of all full nodes known to be stable and trustworthy enough be listed (hard-coded) in the default node software. That is an interesting clarification, thank you abit and I hope other newcomers will find this information valuable also.

abit

Quote from: knaperek on November 18, 2017, 10:07:03 AM
Quote from: abit on November 17, 2017, 06:53:23 PM
Quote from: knaperek on November 16, 2017, 04:31:27 PM
I was just hoping it would be possible to run a single seed node that works for any chain ID, similarly to BitTorrent DHT nodes.
Not possible so far.
Thanks for the clarification abit. For some reason I thought there were two types of nodes :
1.) Seed nodes that only provide node discovery service
2.) Actual full nodes (or witnesses) that keep track of the blockchain and serve blocks to other peers on request
If this was the case then I guess the seed nodes could be made more generic and thus shared among all graphene based projects (Bitshares, Steem, ...), which could provide better reliability overall. I'd draw a parallel with BitTorrent  - no matter which torrent you are downloading, the DHT nodes are the same (disregarding some optimizations that are not important in this context because the number of chains is significantly lower than the number of BitTorrent infohashes).

So, please corrent me if I'm wrong, but the way it works now is that there's no role separation between Seed nodes and Witness nodes and there's just a single program (binary) that runs it, listening on a single port, right?
In BitShares, seed nodes also serve as full nodes.
BitShares committee member: abit
BitShares witness: in.abit

knaperek

Quote from: abit on November 17, 2017, 06:53:23 PM
Quote from: knaperek on November 16, 2017, 04:31:27 PM
I was just hoping it would be possible to run a single seed node that works for any chain ID, similarly to BitTorrent DHT nodes.
Not possible so far.
Thanks for the clarification abit. For some reason I thought there were two types of nodes :
1.) Seed nodes that only provide node discovery service
2.) Actual full nodes (or witnesses) that keep track of the blockchain and serve blocks to other peers on request
If this was the case then I guess the seed nodes could be made more generic and thus shared among all graphene based projects (Bitshares, Steem, ...), which could provide better reliability overall. I'd draw a parallel with BitTorrent  - no matter which torrent you are downloading, the DHT nodes are the same (disregarding some optimizations that are not important in this context because the number of chains is significantly lower than the number of BitTorrent infohashes).

So, please corrent me if I'm wrong, but the way it works now is that there's no role separation between Seed nodes and Witness nodes and there's just a single program (binary) that runs it, listening on a single port, right?

abit

Quote from: knaperek on November 16, 2017, 04:31:27 PM
I was just hoping it would be possible to run a single seed node that works for any chain ID, similarly to BitTorrent DHT nodes.
Not possible so far.
BitShares committee member: abit
BitShares witness: in.abit

knaperek

Quote from: abit on November 16, 2017, 02:34:01 PM
Quote from: knaperek on November 16, 2017, 09:47:18 AM
Hello, I'm creating a custom blockchain forked from BitShares and would be happy to give back to the BitShares community and open up my Seed Nodes for BitShares users as well. So I was wondering whether it is possible to have a single seed node that supports multiple Chain IDs. Any ideas?
You can use different port for different chains.
I guess this implies running a separate instance for each chain ID, bound to a unique port on the system. Well that is an option of course, I was just hoping it would be possible to run a single seed node that works for any chain ID, similarly to BitTorrent DHT nodes.

abit

Quote from: knaperek on November 16, 2017, 09:47:18 AM
Hello, I'm creating a custom blockchain forked from BitShares and would be happy to give back to the BitShares community and open up my Seed Nodes for BitShares users as well. So I was wondering whether it is possible to have a single seed node that supports multiple Chain IDs. Any ideas?
You can use different port for different chains.
BitShares committee member: abit
BitShares witness: in.abit

knaperek

Hello, I'm creating a custom blockchain forked from BitShares and would be happy to give back to the BitShares community and open up my Seed Nodes for BitShares users as well. So I was wondering whether it is possible to have a single seed node that supports multiple Chain IDs. Any ideas?

iHashFury

Please amend my seed node details from:

"212.47.249.84:50696", //     (France)

to

"seed.bitsharesdex.com:50696", //     (Europe)

Thanks

sahkan

"23.92.53.182:1776"    // sahkan-bitshares  USA
DEX Access:  [url="https://dexnode.net/?r=sahkan-bitshares"]https://dexnode.net/?r=sahkan-bitshares[/url]

iHashFury


oxarbitrage

Last version was sent to master as pull request:

https://github.com/bitshares/bitshares-core/pull/241/files

Seed Nodes:

+               "seed01.bitsharesnodes.com:1776",   // wackou
+               "seed05.bitsharesnodes.com:1776",   // Thom
+               "seed06.bitsharesnodes.com:1776",   // Thom
+               "seed07.bitsharesnodes.com:1776",   // Thom
+               "seed.roelandp.nl:1776",            // roelandp (Canada)
+               "bts-seed1.abit-more.com:62015",    // abit
+               "seeds.bitshares.eu:1776",          // xeroc
+               "51.15.61.160:1776",                // lafona
+               "128.199.143.47:2015"               // Harvey

Lafona added a pull request with a node less than 24 hours ago and was merged so i included it.

Harvey

#10
The BTS seed node "128.199.143.47:2015" and  API node "128.199.143.47:2016" are alive.
Please vote for the witness harvey-xts
BTS       Witness:harvey-xts Seed:128.199.143.47:2015 API:[url="wss://128.199.143.47"]wss://128.199.143.47[/url]:2016 
MUSE   Witness:harvey-xts Seed:128.199.143.47:2017 API:[url="ws://128.199.143.47:2018"]ws://128.199.143.47:2018[/url]

pc

Quote from: oxarbitrage on February 28, 2017, 02:31:48 PM

"bts.seeds.quisquis.de:1776", // cyrano
"seeds.bitshares.eu 1776" // pc


These two provide identical information. bitshares.eu looks more official and belongs to xeroc, so I suggest to remove bts.seeds.quisquis.de.
Bitcoin - Perspektive oder Risiko? ISBN 978-3-8442-6568-2 [url="http://bitcoin.quisquis.de"]http://bitcoin.quisquis.de[/url]

oxarbitrage

#8
References:

· github issue 5: https://github.com/bitshares/bitshares-core/pull/5
· Forum 1st post: https://bitsharestalk.org/index.php/topic,18908.0.html
· Forum updated post by vikram: https://bitsharestalk.org/index.php/topic,23715.0.html
· Bitshares nodes website: http://status.bitsharesnodes.com/
· http://seeds.quisquis.de/bitshares.html

This are the  working nodes we can have in the default list for a possible pull request:

vector<string> seeds = {
"seed01.bitsharesnodes.com:1776", // wackou
"seed05.bitsharesnodes.com:1776", // Thom
"seed06.bitsharesnodes.com:1776", // Thom
"seed07.bitsharesnodes.com:1776", // Thom
"seed.roelandp.nl:1776", // roelandp (Canada)
"bts-seed1.abit-more.com:62015", // abit
"bts.seeds.quisquis.de:1776", // cyrano
"seeds.bitshares.eu 1776" // pc
};


The rest of the working IP addresses working can be found at:

· http://seeds.quisquis.de/bitshares.html

But we can't add it to the default list as we need the explicit authorization from the seed node owner, they can be private project nodes, they can be nodes of variable IP or port.

If you own a node that want to be included please post here.

abit

Quote from: xeroc on January 16, 2017, 03:33:22 PM
"seeds.bitshares.eu:1776" is a location-based DNS resolver offered by @pc
Its status tracker is here: http://seeds.quisquis.de/bitshares.html
BitShares committee member: abit
BitShares witness: in.abit

abit

BitShares committee member: abit
BitShares witness: in.abit

xeroc

"seeds.bitshares.eu:1776" is a location-based DNS resolver offered by @pc

iHashFury

"212.47.249.84:50696", // iHashFury

is a valid seed node

vikram

Quote from: Brekyrself on January 16, 2017, 12:33:18 AM
Sorry for the dumb question but is this something that could run on a Rasp Pi for example?  I wouldn't mind having a dedicated one or two up and running 24/7 to help out...

I don't know much about Raspberry Pi's but BitShares is not officially supported on ARM. It may be possible (I think it was at one point) but I'd start a different thread to discuss it.

Brekyrself

Sorry for the dumb question but is this something that could run on a Rasp Pi for example?  I wouldn't mind having a dedicated one or two up and running 24/7 to help out...

vikram

#1
This is a new thread to maintain updated info on seed nodes for BitShares. The previous thread was: https://bitsharestalk.org/index.php/topic,18908.0.html

The current list of default seed nodes is here: https://github.com/bitshares/bitshares-core/blob/master/libraries/app/application.cpp#L168-L181

               "104.236.144.84:1777",               // puppies      (USA)
               "128.199.143.47:2015",               // Harvey       (Singapore)
               "212.47.249.84:50696",               // iHashFury    (France)
               "51.15.61.160:1776",                 // lafona       (France)
               "bts-seed1.abit-more.com:62015",     // abit         (China)
               "seed.bitsharesnodes.com:1776",      // wackou       (Netherlands)
               "seed.blocktrades.us:1776",          // BlockTrades  (USA)
               "seed.cubeconnex.com:1777",          // cube         (USA)
               "seed.roelandp.nl:1776",             // roelandp     (Canada)
               "seed04.bitsharesnodes.com:1776",    // Thom         (Australia)
               "seed05.bitsharesnodes.com:1776",    // Thom         (USA)
               "seed06.bitsharesnodes.com:1776",    // Thom         (USA)
               "seed07.bitsharesnodes.com:1776",    // Thom         (Singapore)
               "seeds.bitshares.eu:1776"            // pc           (http://seeds.quisquis.de/bitshares.html)


I am requesting that operators currently in the list please confirm whether you are still actively maintaining your listed node(s). Anyone that wants to be added please also post here.

Sincere thanks to all volunteers for providing this essential service to the community and stakeholders.