BitShares Forum
Main => General Discussion => Topic started by: JonnyB on January 01, 2016, 11:47:58 pm
-
Openledger/bitshares is down for me, anyone else?
-
Yep, me too. Light wallet and the browser..
-
https://bitsharestalk.org/index.php/topic,20851.msg269437.html#new
-
well this is a great start to the new year :-(
-
Openledger server is down. We are working on restoring it.
-
probably needs some antifreeze :)
-
How decentralized is BitShares if we depend on OpenLedger service to be up and running? I couldn't use it with the light client too.
-
How decentralized is BitShares if we depend on OpenLedger service to be up and running? I couldn't use it with the light client too.
Run a business .. setup your own witness nodes and there you go ..
The network is decentralized .. access to the network currently is not ..
-
How decentralized is BitShares if we depend on OpenLedger service to be up and running? I couldn't use it with the light client too.
Run a business .. setup your own witness nodes and there you go ..
The network is decentralized .. access to the network currently is not ..
Is there more detailed instructions about how to that ? thanks
-
How decentralized is BitShares if we depend on OpenLedger service to be up and running? I couldn't use it with the light client too.
Run a business .. setup your own witness nodes and there you go ..
The network is decentralized .. access to the network currently is not ..
is that a valid statement for the light wallet too?
-
There's no distinct documentation for this yet ..
putting it on my list .
essentially yuo have to do what is written here:
http://docs.bitshares.eu/apps/node.html
Only need to enable the RPC
Then in the settings of your lilght wallet you can change the websocket server to your local full/witness node.
Done
-
Are there any other websocket servers that we can choose from ?
-
I am invested heavily in Obits. @ccedk I would like an update here please.
Was your site hacked, wan down, feds showed up or what?
-
Are there any other websocket servers that we can choose from ?
ws://185.82.203.92:8090 will be up in a few minutes. This is my personal chain server on a dedicated server. I'll leave it public till things stabilise.
-
I am invested heavily in Obits. @ccedk I would like an update here please.
Was your site hacked, wan down, feds showed up or what?
Queen's Guards..
-
this thread is 10 days old. ::)
-
How decentralized is BitShares if we depend on OpenLedger service to be up and running? I couldn't use it with the light client too.
Run a business .. setup your own witness nodes and there you go ..
The network is decentralized .. access to the network currently is not ..
I just don't know how to connect to other witness node in case the OpenLedger one that seems to be the default, is down. I don't know which other websocket servers to choose from, where's a list for me to manually input a new one. Couldn't we make it so in case one is down, it automatically redirects to other random node ran by witnesses?
-
How decentralized is BitShares if we depend on OpenLedger service to be up and running? I couldn't use it with the light client too.
Run a business .. setup your own witness nodes and there you go ..
The network is decentralized .. access to the network currently is not ..
I just don't know how to connect to other witness node in case the OpenLedger one that seems to be the default, is down. I don't know which other websocket servers to choose from, where's a list for me to manually input a new one. Couldn't we make it so in case one is down, it automatically redirects to other random node ran by witnesses?
That's not a bad idea.. setup a proxy that monitors available nodes and connects you. The only danger in that is if those nodes are not keeping up to date could be an issue.. it's easy to tell if a server is online and responding but not so easy to tell if the node is getting blocks properly etc.
-
How decentralized is BitShares if we depend on OpenLedger service to be up and running? I couldn't use it with the light client too.
Run a business .. setup your own witness nodes and there you go ..
The network is decentralized .. access to the network currently is not ..
I just don't know how to connect to other witness node in case the OpenLedger one that seems to be the default, is down. I don't know which other websocket servers to choose from, where's a list for me to manually input a new one. Couldn't we make it so in case one is down, it automatically redirects to other random node ran by witnesses?
That's not a bad idea.. setup a proxy that monitors available nodes and connects you. The only danger in that is if those nodes are not keeping up to date could be an issue.. it's easy to tell if a server is online and responding but not so easy to tell if the node is getting blocks properly etc.
Then when we click to add a new node, a list of nodes owned by witnesses would popup and we would choose the one we want. Witnesses nodes should be up to date. Or a list of witnesses who processed the last 10 blocks
-
How decentralized is BitShares if we depend on OpenLedger service to be up and running? I couldn't use it with the light client too.
Run a business .. setup your own witness nodes and there you go ..
The network is decentralized .. access to the network currently is not ..
I just don't know how to connect to other witness node in case the OpenLedger one that seems to be the default, is down. I don't know which other websocket servers to choose from, where's a list for me to manually input a new one. Couldn't we make it so in case one is down, it automatically redirects to other random node ran by witnesses?
That's not a bad idea.. setup a proxy that monitors available nodes and connects you. The only danger in that is if those nodes are not keeping up to date could be an issue.. it's easy to tell if a server is online and responding but not so easy to tell if the node is getting blocks properly etc.
Then when we click to add a new node, a list of nodes owned by witnesses would popup and we would choose the one we want. Witnesses nodes should be up to date. Or a list of witnesses who processed the last 10 blocks
It's up to the witnesses to provide that.. however I don't think they should.. their task is to witness block production.. we add end user load to that and you invite an attack vector + you need to increase their pay for more infrastructure.
-
How abour something similar to pool.ntp.org but for api
-
But they're the only reliable nodes, that way we end up having a bottleneck with only a single node, in this case OpenLedger, for all users. Also I don't agree with xeroc when he says the network is decentralized but access is not... that may be true in theory but from a user pov that's not decentralized since if one single node is down he has no access. This, from a user pov
-
How can I run a wallet server?
-
How can I run a wallet server?
I will write a tutorial about it tomorrow
-
How can I run a wallet server?
I will write a tutorial about it tomorrow
+5% +5% +5%
-
How can I run a wallet server?
There is a brief installation instruction here https://github.com/cryptonomex/faucet/blob/master/README.md
-
Are there any other websocket servers that we can choose from ?
In China we have DACPLAY, and harvey, and perhaps btsabc running ws servers. Anyone else is running this service?
Maybe it's better to add them to Graphene-ui? Maybe add a list in the documents? @xeroc @svk @wmbutler
//Update:
I'll try to collect a detailed list first.
DACPLAY: wss://bitshares.dacplay.org:8089
RiverHead: ws://185.82.203.92:8090
Harvey: ws://128.199.143.47:2016
BTSDac: ws://139.196.37.179:8090
-
How decentralized is BitShares if we depend on OpenLedger service to be up and running? I couldn't use it with the light client too.
Run a business .. setup your own witness nodes and there you go ..
The network is decentralized .. access to the network currently is not ..
I just don't know how to connect to other witness node in case the OpenLedger one that seems to be the default, is down. I don't know which other websocket servers to choose from, where's a list for me to manually input a new one. Couldn't we make it so in case one is down, it automatically redirects to other random node ran by witnesses?
That's not a bad idea.. setup a proxy that monitors available nodes and connects you. The only danger in that is if those nodes are not keeping up to date could be an issue.. it's easy to tell if a server is online and responding but not so easy to tell if the node is getting blocks properly etc.
Then when we click to add a new node, a list of nodes owned by witnesses would popup and we would choose the one we want. Witnesses nodes should be up to date. Or a list of witnesses who processed the last 10 blocks
It's up to the witnesses to provide that.. however I don't think they should.. their task is to witness block production.. we add end user load to that and you invite an attack vector + you need to increase their pay for more infrastructure.
Better if seed nodes provide ws services as well. Or another list of ws servers.
-
That's not a bad idea.. setup a proxy that monitors available nodes and connects you. The only danger in that is if those nodes are not keeping up to date could be an issue.. it's easy to tell if a server is online and responding but not so easy to tell if the node is getting blocks properly etc.
We should set up DNS seeders that do that. For API servers as well as seed nodes.
Then when we click to add a new node, a list of nodes owned by witnesses would popup and we would choose the one we want. Witnesses nodes should be up to date. Or a list of witnesses who processed the last 10 blocks
Witness nodes should not provide API functions to the world. They shouldn't allow any incoming connections - otherwise it's too easy to overload them.
-
Are there any other websocket servers that we can choose from ?
In China we have DACPLAY, and harvey, and perhaps btsabc running ws servers. Anyone else is running this service?
Maybe it's better to add them to Graphene-ui? Maybe add a list in the documents? @xeroc @svk @wmbutler
//Update:
I'll try to collect a detailed list first.
DACPLAY: wss://bitshares.dacplay.org:8089
RiverHead: ws://185.82.203.92:8090
Harvey: ws://128.199.143.47:2016
BTSDac: ws://139.196.37.179:8090
BTAER(BTSDac): ws://btaer.com:8090 (currently offline for me)
Pull request submitted. https://github.com/cryptonomex/graphene-ui/pull/666
-
How can I run a wallet server?
I will write a tutorial about it tomorrow
http://docs.bitshares.eu/bitshares/tutorials/full-node-usage.html