"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)
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...
"seeds.bitshares.eu:1776" is a location-based DNS resolver offered by @pcIts status tracker is here: http://seeds.quisquis.de/bitshares.html
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
};
Code: [Select]"bts.seeds.quisquis.de:1776", // cyrano
"seeds.bitshares.eu 1776" // pc
"212.47.249.84:50696", // iHashFury
is a valid seed node
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.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 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 :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.
In BitShares, seed nodes also serve as full nodes.Thanks for the clarification abit. For some reason I thought there were two types of nodes :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.
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.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.
Role | Stores blockchain | Public RPC | Provides blockchain via p2p | Generates blocks | Includes history plugins |
Witness | ✔ | ❌ | ✔ | ✔ | ❌ |
Seed | ✔ | ❌ | ✔ | ❌ | ❌ |
Full node | ✔ | ✔/ ❌ | ✔ | ❌ | ✔ |
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.
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.
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.