Topic: Qora | POS | Assets | Names | Polls | Automated Transactions | Social Network - page 126. (Read 249452 times)
August 25, 2016, 12:14:57 PM
So, um, is Qora.co.in gone for good or just down?
August 25, 2016, 12:14:50 PM
If enough people have not been staking for a long time, it is a fundamental problem with the coin. Needs fixing. Maybe go to POW or tweak the POS to encourage staking.
I think building a plan for Qora 2.0 and allowing people to buy into it with Qora should work. That's the only way this coin can have a bright future imo. Temporary measures such as paying people to stake are not going to work when there are fundamental issues with the coin itself, there's no funding and no dedicated marketing manager. It is best to create Qora 2.0 with a LONG TERM vision.
Thinking on the lines of Verium, Nxt 2.0 (Ardor)
Also, Qora is such a bad name. Qora 2.0 should have a better name
I think building a plan for Qora 2.0 and allowing people to buy into it with Qora should work. That's the only way this coin can have a bright future imo. Temporary measures such as paying people to stake are not going to work when there are fundamental issues with the coin itself, there's no funding and no dedicated marketing manager. It is best to create Qora 2.0 with a LONG TERM vision.
Thinking on the lines of Verium, Nxt 2.0 (Ardor)
Also, Qora is such a bad name. Qora 2.0 should have a better name
QORA is a great name, I doubt we'll change that....
Recently someone invented an indigenous faecal incontinence management device, and called it 'Qora'. Unfortunately it shows up at the bottom of the first page of results when Googling for 'Qora'. It's going to get embarrassing if the faecal incontinence device starts getting a higher Google rank. It already shows up directly above Qoracoin's Facebook link.
August 25, 2016, 11:16:06 AM
So I figured I would ask this here while I'm waiting on developer reply, hopefully I can get the hosted wallet up sooner than later...
I've got a linux host running the wallet on a server in my DC. The issue I'm having, is I can't seem to allow it access outside the same 127.0.0.1, despite setting the settings to allow all...
Does anyone know the setting modification necessary in settings.json file that will allow access from outside the sytem? I am thinking that maybe if I set the setting manually in the json file as opposed to attempting to use the GUI (yes, this server I've setup running Mint, so kill me. lol. I will setup an ubuntu server version as well, once I've figured this final riddle out.)
If anyone knows what I need to add to allow access from outside localhost, i.e. the internet, please let me know.
This is the final piece remaining until I can give polo a link to a 'working blockexplorer' since they can't seem to figure out the local blockex on their end.
Any assistance is greatly appreciated. I'm sure I should have an answer by tomorrow, but I was just wanting to get it setup sooner rather than later.
Thanks!
I've got a linux host running the wallet on a server in my DC. The issue I'm having, is I can't seem to allow it access outside the same 127.0.0.1, despite setting the settings to allow all...
Does anyone know the setting modification necessary in settings.json file that will allow access from outside the sytem? I am thinking that maybe if I set the setting manually in the json file as opposed to attempting to use the GUI (yes, this server I've setup running Mint, so kill me. lol. I will setup an ubuntu server version as well, once I've figured this final riddle out.)
If anyone knows what I need to add to allow access from outside localhost, i.e. the internet, please let me know.
This is the final piece remaining until I can give polo a link to a 'working blockexplorer' since they can't seem to figure out the local blockex on their end.
Any assistance is greatly appreciated. I'm sure I should have an answer by tomorrow, but I was just wanting to get it setup sooner rather than later.
Thanks!
The easiest way is to do this within the application (no need to edit the settings.json manually). Open the wallet in normal mode (not light mode). Within the gui open File->Settings
In the Basic frame make sure you have the web enabled. After that go to Access Permission and make sure "Allow for all" is enabled for Web Server whitelist. Then press apply!
August 25, 2016, 01:34:45 AM
So I figured I would ask this here while I'm waiting on developer reply, hopefully I can get the hosted wallet up sooner than later...
I've got a linux host running the wallet on a server in my DC. The issue I'm having, is I can't seem to allow it access outside the same 127.0.0.1, despite setting the settings to allow all...
Does anyone know the setting modification necessary in settings.json file that will allow access from outside the sytem? I am thinking that maybe if I set the setting manually in the json file as opposed to attempting to use the GUI (yes, this server I've setup running Mint, so kill me. lol. I will setup an ubuntu server version as well, once I've figured this final riddle out.)
If anyone knows what I need to add to allow access from outside localhost, i.e. the internet, please let me know.
This is the final piece remaining until I can give polo a link to a 'working blockexplorer' since they can't seem to figure out the local blockex on their end.
Any assistance is greatly appreciated. I'm sure I should have an answer by tomorrow, but I was just wanting to get it setup sooner rather than later.
Thanks!
I've got a linux host running the wallet on a server in my DC. The issue I'm having, is I can't seem to allow it access outside the same 127.0.0.1, despite setting the settings to allow all...
Does anyone know the setting modification necessary in settings.json file that will allow access from outside the sytem? I am thinking that maybe if I set the setting manually in the json file as opposed to attempting to use the GUI (yes, this server I've setup running Mint, so kill me. lol. I will setup an ubuntu server version as well, once I've figured this final riddle out.)
If anyone knows what I need to add to allow access from outside localhost, i.e. the internet, please let me know.
This is the final piece remaining until I can give polo a link to a 'working blockexplorer' since they can't seem to figure out the local blockex on their end.
Any assistance is greatly appreciated. I'm sure I should have an answer by tomorrow, but I was just wanting to get it setup sooner rather than later.
Thanks!
I'm only guessing like you, but swapping 127.0.0.1 for your IP in the settings.json file might work.
"checkpoint": true,
"soundreceivepayment": true,
"rpcallowed": [
"127.0.0.1"
],
"generatorkeycaching": true,
"webenabled": true,
"soundreceivemessage": true,
"soundnewtransaction": true,
"minconnections": 10,
"weballowed": [
"127.0.0.1"
],
These are the only two links I could find explaining how to set up a node (one explains Linux, the other Windows). Sadly neither of them explain how to make the explorer available outside localhost.
https://bitcointalksearch.org/topic/m.6943209
https://bitcointalksearch.org/topic/m.6915791
The Windows link does mention a bounty that used to be paid out needing rpc port 9085 being reachable to get it, but I don't know why.
Quote
Since there is a reward for running a node every week.
It should run without -disablerpc parameter.
The rpc port is 9085.
Make sure port 9085 is reachable if you want to get the reward.
It should run without -disablerpc parameter.
The rpc port is 9085.
Make sure port 9085 is reachable if you want to get the reward.
August 24, 2016, 11:07:36 PM
So I figured I would ask this here while I'm waiting on developer reply, hopefully I can get the hosted wallet up sooner than later...
I've got a linux host running the wallet on a server in my DC. The issue I'm having, is I can't seem to allow it access outside the same 127.0.0.1, despite setting the settings to allow all...
Does anyone know the setting modification necessary in settings.json file that will allow access from outside the sytem? I am thinking that maybe if I set the setting manually in the json file as opposed to attempting to use the GUI (yes, this server I've setup running Mint, so kill me. lol. I will setup an ubuntu server version as well, once I've figured this final riddle out.)
If anyone knows what I need to add to allow access from outside localhost, i.e. the internet, please let me know.
This is the final piece remaining until I can give polo a link to a 'working blockexplorer' since they can't seem to figure out the local blockex on their end.
Any assistance is greatly appreciated. I'm sure I should have an answer by tomorrow, but I was just wanting to get it setup sooner rather than later.
Thanks!
I've got a linux host running the wallet on a server in my DC. The issue I'm having, is I can't seem to allow it access outside the same 127.0.0.1, despite setting the settings to allow all...
Does anyone know the setting modification necessary in settings.json file that will allow access from outside the sytem? I am thinking that maybe if I set the setting manually in the json file as opposed to attempting to use the GUI (yes, this server I've setup running Mint, so kill me. lol. I will setup an ubuntu server version as well, once I've figured this final riddle out.)
If anyone knows what I need to add to allow access from outside localhost, i.e. the internet, please let me know.
This is the final piece remaining until I can give polo a link to a 'working blockexplorer' since they can't seem to figure out the local blockex on their end.
Any assistance is greatly appreciated. I'm sure I should have an answer by tomorrow, but I was just wanting to get it setup sooner rather than later.
Thanks!
August 24, 2016, 11:02:51 PM
@crowetic
If people continue posting addresses here crowetic, the whole Qora team, and anyone who posted an address could get banned, and this thread could get locked.
Giveaways were banned in Alternate cryptocurrencies boards years ago by theymos (the forum administrator).
The moderators won't mind people sending addresses to crowetic by pm, but posting any address in this thread is not allowed.
If people continue posting addresses here crowetic, the whole Qora team, and anyone who posted an address could get banned, and this thread could get locked.
Giveaways were banned in Alternate cryptocurrencies boards years ago by theymos (the forum administrator).
The moderators won't mind people sending addresses to crowetic by pm, but posting any address in this thread is not allowed.
The moderators can speak for themselves if they have a concern, which is unlikely.
It's not a giveaway, per se. It's trying to solve a compelling urgent problem, in the only way possible.
In case you weren't following along: A huge percent of the Qora coins have been locked in Poloniex exchange for several months. They disabled dep/wd, so noone can get their coins out. They say the network wasn't stable enough because not enough wallets forging. But the wallets can't forge *because they have no coins* ! We can't add new users, because noone can get any coins from the main exchange!
This is the only way to solve the problem, untangle the knot.
The so-called "giveaway" amounts are relatively small, and for people pledging to actually do work (ie. get the wallet installed, synced and forging, which is not very easy at the moment).
That said, crowetic, we probably do need a smallish cap on the number of added forging wallets here, to avoid a giant string of 'me too' posts (which is really the only point of that restriction). And maybe use another word like 'bounty'.
Absolutely correct, if the mods feel the need to ban me for helping to fix a coin with an issue that can only be resolved in this fashion, that is their prerogative, I already realize they don't like the fact that altcoins are even on this forum in the first place, which is why I have already developed an alternative. Which we will be releasing shortly.
But yes, just in case, anyone interested in helping the QORA network, please send me a PM with your address (and only if you haven't already, please...) and I will send you some coin to forge with (only to help the network out of the current state, for anyone who is wondering, this is NOT a giveaway, it is a move that is necessary to revive the network while the largest exchange with 90% of the coin has their wallet on maintenance without good reason.)
Alright, I've finished the upload for the 'data' folder from the QORA wallet location. I believe this should help with the people who are having sync issues. You shouldn't be getting no connections, if you are, I will find a solution for that as well, but I have yet to see that issue, try restarting your wallet.
Also, if you're having issues on wallet close (which is an issue I've already reported to main dev and we're going to talk today in the meeting about a solution) please let me know, and I'll give you a few options that will hopefully help.
Here is a download on my cloud (I will have a more 'official' download coming soon, still working on domains and such.) - https://cloud.crowetic.com/s/wecM2rDvqIIFAPl
Hello,
Installed the client again, got to sync just fine (in under 2 hours). But Im always "no connections" so I cannot forge. I have a couple more wallets that are forging other coins on that machine.
I will download your files to see if they help, thanks.
This link has both data folders zipped. But if you're not getting a connection, make sure your windows firewall isn't blocking QORA. I don't believe that the lack of connections issue is caused by the db, it doesn't make sense to be that way.
Make sure you use this link, which has both... https://cloud.crowetic.com/s/3rUsS3CAEwc6Ze8
Ok let me explain.
I can install a fresh client, connect to others and sync to full the DB in a couple of hours, no problem there. As soon as I get up to date with the blocks I start getting disconnects every other minute. So im online with the network now, then a minute later im with no peers.
Code:
2016-08-24 11:26:45 INFO ConnectionCreator:60 - Connecting to known peer
61.186
.94.152 :: 13 / 23 :: Connections: 5
2016-08-24 11:26:45 INFO Network:66 - Connection successfull :
/61.186.94.152
2016-08-24 11:26:45 INFO ConnectionCreator:60 - Connecting to known peer
61.186
.94.153 :: 14 / 23 :: Connections: 6
2016-08-24 11:26:46 INFO Network:91 - Connection close : /61.186.94.152
2016-08-24 11:26:46 INFO Network:66 - Connection successfull :
/61.186.94.153
2016-08-24 11:26:46 INFO ConnectionCreator:60 - Connecting to known peer
61.186
.94.154 :: 15 / 23 :: Connections: 6
2016-08-24 11:26:46 INFO Network:66 - Connection successfull :
/61.186.94.154
2016-08-24 11:26:46 INFO ConnectionCreator:60 - Connecting to known peer
61.186
.94.156 :: 16 / 23 :: Connections: 7
2016-08-24 11:26:46 INFO Network:66 - Connection successfull :
/61.186.94.156
2016-08-24 11:26:46 INFO ConnectionCreator:60 - Connecting to known peer
61.186
.94.157 :: 17 / 23 :: Connections: 8
2016-08-24 11:26:47 INFO Network:66 - Connection successfull :
/61.186.94.157
2016-08-24 11:26:47 INFO ConnectionCreator:60 - Connecting to known peer
61.186
.94.158 :: 18 / 23 :: Connections: 9
2016-08-24 11:26:47 INFO Network:66 - Connection successfull :
/61.186.94.158
2016-08-24 11:26:47 INFO ConnectionCreator:60 - Connecting to known peer
198.19
9.103.12 :: 19 / 23 :: Connections: 10
2016-08-24 11:26:47 INFO Network:66 - Connection successfull :
/198.199.103.12
2016-08-24 11:26:47 INFO ConnectionCreator:60 - Connecting to known peer
188.16
6.53.239 :: 20 / 23 :: Connections: 11
2016-08-24 11:26:47 INFO Network:91 - Connection close : /61.186.94.158
2016-08-24 11:26:51 INFO Network:91 - Connection close : /61.186.94.146
2016-08-24 11:26:51 INFO Network:91 - Connection close : /61.186.94.146
2016-08-24 11:26:51 INFO Network:91 - Connection close : /61.186.94.147
2016-08-24 11:26:51 INFO Network:91 - Connection close : /61.186.94.147
2016-08-24 11:26:54 INFO Network:91 - Connection close : /61.186.94.148
2016-08-24 11:26:54 INFO Network:91 - Connection close : /61.186.94.148
2016-08-24 11:26:55 INFO Network:91 - Connection close : /61.186.94.149
2016-08-24 11:26:55 INFO Network:91 - Connection close : /61.186.94.149
2016-08-24 11:26:55 INFO Network:91 - Connection close : /61.186.94.151
2016-08-24 11:26:55 INFO Network:91 - Connection close : /61.186.94.151
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.153
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.153
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.154
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.154
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.156
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.156
2016-08-24 11:26:57 INFO Network:91 - Connection close : /61.186.94.157
2016-08-24 11:26:57 INFO Network:91 - Connection close : /61.186.94.157
2016-08-24 11:26:57 INFO Network:91 - Connection close : /198.199.103.12
2016-08-24 11:26:57 INFO Network:91 - Connection close : /198.199.103.12
2016-08-24 11:27:08 INFO Peer:146 - Failed to connect to : /188.166.53.239
2016-08-24 11:27:08 INFO ConnectionCreator:60 - Connecting to known peer
193.24
2.148.251 :: 21 / 23 :: Connections: 0
2016-08-24 11:27:10 INFO Peer:146 - Failed to connect to : /193.242.148.251
61.186
.94.152 :: 13 / 23 :: Connections: 5
2016-08-24 11:26:45 INFO Network:66 - Connection successfull :
/61.186.94.152
2016-08-24 11:26:45 INFO ConnectionCreator:60 - Connecting to known peer
61.186
.94.153 :: 14 / 23 :: Connections: 6
2016-08-24 11:26:46 INFO Network:91 - Connection close : /61.186.94.152
2016-08-24 11:26:46 INFO Network:66 - Connection successfull :
/61.186.94.153
2016-08-24 11:26:46 INFO ConnectionCreator:60 - Connecting to known peer
61.186
.94.154 :: 15 / 23 :: Connections: 6
2016-08-24 11:26:46 INFO Network:66 - Connection successfull :
/61.186.94.154
2016-08-24 11:26:46 INFO ConnectionCreator:60 - Connecting to known peer
61.186
.94.156 :: 16 / 23 :: Connections: 7
2016-08-24 11:26:46 INFO Network:66 - Connection successfull :
/61.186.94.156
2016-08-24 11:26:46 INFO ConnectionCreator:60 - Connecting to known peer
61.186
.94.157 :: 17 / 23 :: Connections: 8
2016-08-24 11:26:47 INFO Network:66 - Connection successfull :
/61.186.94.157
2016-08-24 11:26:47 INFO ConnectionCreator:60 - Connecting to known peer
61.186
.94.158 :: 18 / 23 :: Connections: 9
2016-08-24 11:26:47 INFO Network:66 - Connection successfull :
/61.186.94.158
2016-08-24 11:26:47 INFO ConnectionCreator:60 - Connecting to known peer
198.19
9.103.12 :: 19 / 23 :: Connections: 10
2016-08-24 11:26:47 INFO Network:66 - Connection successfull :
/198.199.103.12
2016-08-24 11:26:47 INFO ConnectionCreator:60 - Connecting to known peer
188.16
6.53.239 :: 20 / 23 :: Connections: 11
2016-08-24 11:26:47 INFO Network:91 - Connection close : /61.186.94.158
2016-08-24 11:26:51 INFO Network:91 - Connection close : /61.186.94.146
2016-08-24 11:26:51 INFO Network:91 - Connection close : /61.186.94.146
2016-08-24 11:26:51 INFO Network:91 - Connection close : /61.186.94.147
2016-08-24 11:26:51 INFO Network:91 - Connection close : /61.186.94.147
2016-08-24 11:26:54 INFO Network:91 - Connection close : /61.186.94.148
2016-08-24 11:26:54 INFO Network:91 - Connection close : /61.186.94.148
2016-08-24 11:26:55 INFO Network:91 - Connection close : /61.186.94.149
2016-08-24 11:26:55 INFO Network:91 - Connection close : /61.186.94.149
2016-08-24 11:26:55 INFO Network:91 - Connection close : /61.186.94.151
2016-08-24 11:26:55 INFO Network:91 - Connection close : /61.186.94.151
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.153
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.153
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.154
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.154
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.156
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.156
2016-08-24 11:26:57 INFO Network:91 - Connection close : /61.186.94.157
2016-08-24 11:26:57 INFO Network:91 - Connection close : /61.186.94.157
2016-08-24 11:26:57 INFO Network:91 - Connection close : /198.199.103.12
2016-08-24 11:26:57 INFO Network:91 - Connection close : /198.199.103.12
2016-08-24 11:27:08 INFO Peer:146 - Failed to connect to : /188.166.53.239
2016-08-24 11:27:08 INFO ConnectionCreator:60 - Connecting to known peer
193.24
2.148.251 :: 21 / 23 :: Connections: 0
2016-08-24 11:27:10 INFO Peer:146 - Failed to connect to : /193.242.148.251
As you can see, I do connect to the peers. but for some reason I get disconnected. So its just imposible to forge.
If anyone is kind enough to help me out by, or, do you have a list of updated peers I can add to get a reliable connection?
thanks
addnode:
106.187.42.214
188.166.16.64
August 24, 2016, 07:30:43 PM
I'm forging with the 50k qora crowetic loaned me to get the network back to health. Once polo allows withdrawals, I will have a very substantial quantity of qora that will forge and I expect to find blocks every day or so.
What is the value of 1 block ??
I also have lots of qora in polo50 qora...not that much, but healthy for the network to spread it out
August 24, 2016, 07:17:40 PM
I'm forging with the 50k qora crowetic loaned me to get the network back to health. Once polo allows withdrawals, I will have a very substantial quantity of qora that will forge and I expect to find blocks every day or so.
What is the value of 1 block ??
I also have lots of qora in polo August 24, 2016, 07:09:40 PM
I'm forging with the 50k qora crowetic loaned me to get the network back to health. Once polo allows withdrawals, I will have a very substantial quantity of qora that will forge and I expect to find blocks every day or so.
August 24, 2016, 05:05:12 PM
I am running version 0.26.0
I have 4 connections.
Three of them are wallet version 0.25.1
Are these older wallets compatible and OK to run?
I see 4 and up to 10 others fading in and out of my peers Tab but cannot yet see what version they are.
MM
I have 4 connections.
Three of them are wallet version 0.25.1
Are these older wallets compatible and OK to run?
I see 4 and up to 10 others fading in and out of my peers Tab but cannot yet see what version they are.
MM
August 24, 2016, 05:01:51 PM
Is there an online Qora wallet that's moderately reputable/trustworthy?
I'm working on it. Having some strange issues. talking with the dev about the issues I'm having, hopefully I'll have the wallet up shortly.
I'll propose the above issue as well, to the dev.
August 24, 2016, 12:40:52 PM
@crowetic
If people continue posting addresses here crowetic, the whole Qora team, and anyone who posted an address could get banned, and this thread could get locked.
Giveaways were banned in Alternate cryptocurrencies boards years ago by theymos (the forum administrator).
The moderators won't mind people sending addresses to crowetic by pm, but posting any address in this thread is not allowed.
If people continue posting addresses here crowetic, the whole Qora team, and anyone who posted an address could get banned, and this thread could get locked.
Giveaways were banned in Alternate cryptocurrencies boards years ago by theymos (the forum administrator).
The moderators won't mind people sending addresses to crowetic by pm, but posting any address in this thread is not allowed.
The moderators can speak for themselves if they have a concern, which is unlikely.
It's not a giveaway, per se. It's trying to solve a compelling urgent problem, in the only way possible.
In case you weren't following along: A huge percent of the Qora coins have been locked in Poloniex exchange for several months. They disabled dep/wd, so noone can get their coins out. They say the network wasn't stable enough because not enough wallets forging. But the wallets can't forge *because they have no coins* ! We can't add new users, because noone can get any coins from the main exchange!
This is the only way to solve the problem, untangle the knot.
The so-called "giveaway" amounts are relatively small, and for people pledging to actually do work (ie. get the wallet installed, synced and forging, which is not very easy at the moment).
That said, crowetic, we probably do need a smallish cap on the number of added forging wallets here, to avoid a giant string of 'me too' posts (which is really the only point of that restriction). And maybe use another word like 'bounty'.
Absolutely correct, if the mods feel the need to ban me for helping to fix a coin with an issue that can only be resolved in this fashion, that is their prerogative, I already realize they don't like the fact that altcoins are even on this forum in the first place, which is why I have already developed an alternative. Which we will be releasing shortly.
But yes, just in case, anyone interested in helping the QORA network, please send me a PM with your address (and only if you haven't already, please...) and I will send you some coin to forge with (only to help the network out of the current state, for anyone who is wondering, this is NOT a giveaway, it is a move that is necessary to revive the network while the largest exchange with 90% of the coin has their wallet on maintenance without good reason.)
Alright, I've finished the upload for the 'data' folder from the QORA wallet location. I believe this should help with the people who are having sync issues. You shouldn't be getting no connections, if you are, I will find a solution for that as well, but I have yet to see that issue, try restarting your wallet.
Also, if you're having issues on wallet close (which is an issue I've already reported to main dev and we're going to talk today in the meeting about a solution) please let me know, and I'll give you a few options that will hopefully help.
Here is a download on my cloud (I will have a more 'official' download coming soon, still working on domains and such.) - https://cloud.crowetic.com/s/wecM2rDvqIIFAPl
Hello,
Installed the client again, got to sync just fine (in under 2 hours). But Im always "no connections" so I cannot forge. I have a couple more wallets that are forging other coins on that machine.
I will download your files to see if they help, thanks.
This link has both data folders zipped. But if you're not getting a connection, make sure your windows firewall isn't blocking QORA. I don't believe that the lack of connections issue is caused by the db, it doesn't make sense to be that way.
Make sure you use this link, which has both... https://cloud.crowetic.com/s/3rUsS3CAEwc6Ze8
Ok let me explain.
I can install a fresh client, connect to others and sync to full the DB in a couple of hours, no problem there. As soon as I get up to date with the blocks I start getting disconnects every other minute. So im online with the network now, then a minute later im with no peers.
Code:
2016-08-24 11:26:45 INFO ConnectionCreator:60 - Connecting to known peer
61.186
.94.152 :: 13 / 23 :: Connections: 5
2016-08-24 11:26:45 INFO Network:66 - Connection successfull :
/61.186.94.152
2016-08-24 11:26:45 INFO ConnectionCreator:60 - Connecting to known peer
61.186
.94.153 :: 14 / 23 :: Connections: 6
2016-08-24 11:26:46 INFO Network:91 - Connection close : /61.186.94.152
2016-08-24 11:26:46 INFO Network:66 - Connection successfull :
/61.186.94.153
2016-08-24 11:26:46 INFO ConnectionCreator:60 - Connecting to known peer
61.186
.94.154 :: 15 / 23 :: Connections: 6
2016-08-24 11:26:46 INFO Network:66 - Connection successfull :
/61.186.94.154
2016-08-24 11:26:46 INFO ConnectionCreator:60 - Connecting to known peer
61.186
.94.156 :: 16 / 23 :: Connections: 7
2016-08-24 11:26:46 INFO Network:66 - Connection successfull :
/61.186.94.156
2016-08-24 11:26:46 INFO ConnectionCreator:60 - Connecting to known peer
61.186
.94.157 :: 17 / 23 :: Connections: 8
2016-08-24 11:26:47 INFO Network:66 - Connection successfull :
/61.186.94.157
2016-08-24 11:26:47 INFO ConnectionCreator:60 - Connecting to known peer
61.186
.94.158 :: 18 / 23 :: Connections: 9
2016-08-24 11:26:47 INFO Network:66 - Connection successfull :
/61.186.94.158
2016-08-24 11:26:47 INFO ConnectionCreator:60 - Connecting to known peer
198.19
9.103.12 :: 19 / 23 :: Connections: 10
2016-08-24 11:26:47 INFO Network:66 - Connection successfull :
/198.199.103.12
2016-08-24 11:26:47 INFO ConnectionCreator:60 - Connecting to known peer
188.16
6.53.239 :: 20 / 23 :: Connections: 11
2016-08-24 11:26:47 INFO Network:91 - Connection close : /61.186.94.158
2016-08-24 11:26:51 INFO Network:91 - Connection close : /61.186.94.146
2016-08-24 11:26:51 INFO Network:91 - Connection close : /61.186.94.146
2016-08-24 11:26:51 INFO Network:91 - Connection close : /61.186.94.147
2016-08-24 11:26:51 INFO Network:91 - Connection close : /61.186.94.147
2016-08-24 11:26:54 INFO Network:91 - Connection close : /61.186.94.148
2016-08-24 11:26:54 INFO Network:91 - Connection close : /61.186.94.148
2016-08-24 11:26:55 INFO Network:91 - Connection close : /61.186.94.149
2016-08-24 11:26:55 INFO Network:91 - Connection close : /61.186.94.149
2016-08-24 11:26:55 INFO Network:91 - Connection close : /61.186.94.151
2016-08-24 11:26:55 INFO Network:91 - Connection close : /61.186.94.151
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.153
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.153
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.154
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.154
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.156
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.156
2016-08-24 11:26:57 INFO Network:91 - Connection close : /61.186.94.157
2016-08-24 11:26:57 INFO Network:91 - Connection close : /61.186.94.157
2016-08-24 11:26:57 INFO Network:91 - Connection close : /198.199.103.12
2016-08-24 11:26:57 INFO Network:91 - Connection close : /198.199.103.12
2016-08-24 11:27:08 INFO Peer:146 - Failed to connect to : /188.166.53.239
2016-08-24 11:27:08 INFO ConnectionCreator:60 - Connecting to known peer
193.24
2.148.251 :: 21 / 23 :: Connections: 0
2016-08-24 11:27:10 INFO Peer:146 - Failed to connect to : /193.242.148.251
61.186
.94.152 :: 13 / 23 :: Connections: 5
2016-08-24 11:26:45 INFO Network:66 - Connection successfull :
/61.186.94.152
2016-08-24 11:26:45 INFO ConnectionCreator:60 - Connecting to known peer
61.186
.94.153 :: 14 / 23 :: Connections: 6
2016-08-24 11:26:46 INFO Network:91 - Connection close : /61.186.94.152
2016-08-24 11:26:46 INFO Network:66 - Connection successfull :
/61.186.94.153
2016-08-24 11:26:46 INFO ConnectionCreator:60 - Connecting to known peer
61.186
.94.154 :: 15 / 23 :: Connections: 6
2016-08-24 11:26:46 INFO Network:66 - Connection successfull :
/61.186.94.154
2016-08-24 11:26:46 INFO ConnectionCreator:60 - Connecting to known peer
61.186
.94.156 :: 16 / 23 :: Connections: 7
2016-08-24 11:26:46 INFO Network:66 - Connection successfull :
/61.186.94.156
2016-08-24 11:26:46 INFO ConnectionCreator:60 - Connecting to known peer
61.186
.94.157 :: 17 / 23 :: Connections: 8
2016-08-24 11:26:47 INFO Network:66 - Connection successfull :
/61.186.94.157
2016-08-24 11:26:47 INFO ConnectionCreator:60 - Connecting to known peer
61.186
.94.158 :: 18 / 23 :: Connections: 9
2016-08-24 11:26:47 INFO Network:66 - Connection successfull :
/61.186.94.158
2016-08-24 11:26:47 INFO ConnectionCreator:60 - Connecting to known peer
198.19
9.103.12 :: 19 / 23 :: Connections: 10
2016-08-24 11:26:47 INFO Network:66 - Connection successfull :
/198.199.103.12
2016-08-24 11:26:47 INFO ConnectionCreator:60 - Connecting to known peer
188.16
6.53.239 :: 20 / 23 :: Connections: 11
2016-08-24 11:26:47 INFO Network:91 - Connection close : /61.186.94.158
2016-08-24 11:26:51 INFO Network:91 - Connection close : /61.186.94.146
2016-08-24 11:26:51 INFO Network:91 - Connection close : /61.186.94.146
2016-08-24 11:26:51 INFO Network:91 - Connection close : /61.186.94.147
2016-08-24 11:26:51 INFO Network:91 - Connection close : /61.186.94.147
2016-08-24 11:26:54 INFO Network:91 - Connection close : /61.186.94.148
2016-08-24 11:26:54 INFO Network:91 - Connection close : /61.186.94.148
2016-08-24 11:26:55 INFO Network:91 - Connection close : /61.186.94.149
2016-08-24 11:26:55 INFO Network:91 - Connection close : /61.186.94.149
2016-08-24 11:26:55 INFO Network:91 - Connection close : /61.186.94.151
2016-08-24 11:26:55 INFO Network:91 - Connection close : /61.186.94.151
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.153
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.153
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.154
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.154
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.156
2016-08-24 11:26:56 INFO Network:91 - Connection close : /61.186.94.156
2016-08-24 11:26:57 INFO Network:91 - Connection close : /61.186.94.157
2016-08-24 11:26:57 INFO Network:91 - Connection close : /61.186.94.157
2016-08-24 11:26:57 INFO Network:91 - Connection close : /198.199.103.12
2016-08-24 11:26:57 INFO Network:91 - Connection close : /198.199.103.12
2016-08-24 11:27:08 INFO Peer:146 - Failed to connect to : /188.166.53.239
2016-08-24 11:27:08 INFO ConnectionCreator:60 - Connecting to known peer
193.24
2.148.251 :: 21 / 23 :: Connections: 0
2016-08-24 11:27:10 INFO Peer:146 - Failed to connect to : /193.242.148.251
As you can see, I do connect to the peers. but for some reason I get disconnected. So its just imposible to forge.
If anyone is kind enough to help me out by, or, do you have a list of updated peers I can add to get a reliable connection?
thanks
August 24, 2016, 12:14:49 PM
Is there an online Qora wallet that's moderately reputable/trustworthy?
August 24, 2016, 12:05:35 PM
If enough people have not been staking for a long time, it is a fundamental problem with the coin. Needs fixing. Maybe go to POW or tweak the POS to encourage staking.
I think building a plan for Qora 2.0 and allowing people to buy into it with Qora should work. That's the only way this coin can have a bright future imo. Temporary measures such as paying people to stake are not going to work when there are fundamental issues with the coin itself, there's no funding and no dedicated marketing manager. It is best to create Qora 2.0 with a LONG TERM vision.
Thinking on the lines of Verium, Nxt 2.0 (Ardor)
Also, Qora is such a bad name. Qora 2.0 should have a better name
I think building a plan for Qora 2.0 and allowing people to buy into it with Qora should work. That's the only way this coin can have a bright future imo. Temporary measures such as paying people to stake are not going to work when there are fundamental issues with the coin itself, there's no funding and no dedicated marketing manager. It is best to create Qora 2.0 with a LONG TERM vision.
Thinking on the lines of Verium, Nxt 2.0 (Ardor)
Also, Qora is such a bad name. Qora 2.0 should have a better name
QORA is a great name, I doubt we'll change that, but I will say that your thoughts are pretty much exactly in line with ours... Also, I'm not personally managing all of the coins, we have a team broken down into smaller groups that are focused on individual projects. My focus is BURST and QORA right now, I'll be focusing more on assisting the others once we've gotten things squared away here. As far as the marketing, our team has the ability to handle this, and we will start doing so once this immediate problem is handled.
To the people asking about forging, yes, it will take you a very long time to find a block with the small amount of coins I gave you. This isn't the point as it was brought up, this is to help make the network stronger.
Once it is to a point where it is strong enough I can tell Polo to stop forging, then the rest of us will have more of a chance at finding a block, but the network needs more use before finding a block will mean much.
My main goal here is to just get to the point where I can explain what we're going to do in the future, and release the QrowdFunds, get things really moving...
Polo hasn't replied to me yet, and we're synchronizing some hosted wallets as we speak to send them a link to the blockex that they can use as the 'official' since they're asking for that. Once that has been completed, and they unlock deposit and withdrawal, I will tell them to stop forging if we have enough people doing so. Then we can talk more about the future.
August 24, 2016, 10:48:28 AM
If enough people have not been staking for a long time, it is a fundamental problem with the coin. Needs fixing. Maybe go to POW or tweak the POS to encourage staking.
I think building a plan for Qora 2.0 and allowing people to buy into it with Qora should work. That's the only way this coin can have a bright future imo. Temporary measures such as paying people to stake are not going to work when there are fundamental issues with the coin itself, there's no funding and no dedicated marketing manager. It is best to create Qora 2.0 with a LONG TERM vision.
Thinking on the lines of Verium, Nxt 2.0 (Ardor)
Also, Qora is such a bad name. Qora 2.0 should have a better name
I think building a plan for Qora 2.0 and allowing people to buy into it with Qora should work. That's the only way this coin can have a bright future imo. Temporary measures such as paying people to stake are not going to work when there are fundamental issues with the coin itself, there's no funding and no dedicated marketing manager. It is best to create Qora 2.0 with a LONG TERM vision.
Thinking on the lines of Verium, Nxt 2.0 (Ardor)
Also, Qora is such a bad name. Qora 2.0 should have a better name
August 24, 2016, 08:29:14 AM
Forging right now but why does it say " Approx time to find the block : 593 days "
That's a long ass time man
That's a long ass time man Please read previous posts in order how to get the bootstrap file (file copy of blocks) so that you fasten your syncing.
I am talking about the forging time, I already finished the synchronisation
Oh sorry I did not see that right, I think you need more coins in your wallet to get to that block faster
Then what is the point to forge if it is going to take 500 Days to get a block
You are contributing to the stability and health of the network thats the main point and not on getting the block.
August 24, 2016, 08:27:35 AM
Forging right now but why does it say " Approx time to find the block : 593 days "
That's a long ass time man
That's a long ass time man Please read previous posts in order how to get the bootstrap file (file copy of blocks) so that you fasten your syncing.
I am talking about the forging time, I already finished the synchronisation
Oh sorry I did not see that right, I think you need more coins in your wallet to get to that block faster
Then what is the point to forge if it is going to take 500 Days to get a block
You are contributing to the stability and health of the network thats the main point and not on getting the block.
Oh nice I want to support
August 24, 2016, 08:25:51 AM
Forging right now but why does it say " Approx time to find the block : 593 days "
That's a long ass time man
That's a long ass time man Please read previous posts in order how to get the bootstrap file (file copy of blocks) so that you fasten your syncing.
I am talking about the forging time, I already finished the synchronisation
Oh sorry I did not see that right, I think you need more coins in your wallet to get to that block faster
Then what is the point to forge if it is going to take 500 Days to get a block
You are contributing to the stability and health of the network thats the main point and not on getting the block.
August 24, 2016, 08:02:50 AM
Forging right now but why does it say " Approx time to find the block : 593 days "
That's a long ass time man
That's a long ass time man Please read previous posts in order how to get the bootstrap file (file copy of blocks) so that you fasten your syncing.
I am talking about the forging time, I already finished the synchronisation
Oh sorry I did not see that right, I think you need more coins in your wallet to get to that block faster
Then what is the point to forge if it is going to take 500 Days to get a block
August 24, 2016, 07:51:26 AM
Forging right now but why does it say " Approx time to find the block : 593 days "
That's a long ass time man
That's a long ass time man Please read previous posts in order how to get the bootstrap file (file copy of blocks) so that you fasten your syncing.
I am talking about the forging time, I already finished the synchronisation
Oh sorry I did not see that right, I think you need more coins in your wallet to get to that block faster
Jump to: