Qora | POS | Assets | Names | Polls | Automated Transactions | Social Network

[fher98]

@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.

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

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

[1714237203]

1714237203

[1714237203]

1714237203

[1714237203]

1714237203

[1714237203]

1714237203

[1714237203]

1714237203

[crowetic]

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.

[MikeMike]

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

[theduuude]

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.

[okinawa]

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

[theduuude]

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

50 qora...not that much, but healthy for the network to spread it out

[yns1971]

@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.

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

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

[crowetic]

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!

[tex99]

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'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://bitcointalk.org/index.php?topic=522102.msg6943209#msg6943209

https://bitcointalk.org/index.php?topic=522102.msg6915791#msg6915791

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.

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.

[Skerberus]

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!

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!

[tex99]

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

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.

[rlh]

So, um, is Qora.co.in gone for good or just down?

[YukonCoinelius]

Settings parameter   "weballowed"  is the list of IPs that can connect, and empty list apparently means all.  You can set that by editing settings.json,  or via the File-Settings dialog.    However, there appears to be a bug:

BUG:  File-Settings dialog is overwriting/truncating the settings.json file when you click Apply.  It's only writing some of the settings, (maybe just the changed ones, or just the ones on that tab?),  and ignoring the rest.  And it overwrites the file in place,  so you see the cruft from the prior settings still there, but they're past the closing bracket so won't be read.   Observed on Wallet 0.26,  Linux

EDIT:  Also, it seems wrong that empty list on a parameter called "weballowed" means everyone allowed.  Empty should mean none allowed.  Should be something like "*" or "*.*.*.*", or a broadcast/mask address to mean everyone allowed.

Keep a backup of your settings.json
Here is a standard one:

Code:

{
        "knownpeers":[

        ],
        "rpcallowed":[
                "127.0.0.1"
        ],
        "weballowed":[
                "127.0.0.1"
        ],
        "guienabled":true,
        "rpcenabled":true,
        "webenabled":true,
        "systray":true,
        "maxconnections":100,
        "minconnections":10,
        "generatorkeycaching":true,
        "checkpoint":true,
        "soundreceivepayment":true,
        "soundnewtransaction":true,
        "soundreceivemessage":true
}

[crowetic]

So, um, is Qora.co.in gone for good or just down?

I would assume that site is down for good, but I've successfully gotten two hosted wallets up, the first one may be slower than the second, I'm waiting on the DNS to propagate to the qora.tech domain.

I think I will also put it on qora.online



http://burstkore.ddns.net:9090/index/blockexplorer.html

http://qora.tech:9090/index/blockexplorer.html

[crowetic]

Here's a good copy of the chain in case anyone is having issues...

https://cloud.crowetic.com/s/3rUsS3CAEwc6Ze8

Also, some simple guidelines until we get the actual fix pushed...


1. ALWAYS close the wallet with file-quit to avoid db issues

2. The default settings.json file seems corrupted. IF you file-quit the wallet, wait for the db to save (don't kill it.) then DELETE the settings.json file, and restart the wallet, your settings will then save and be good.



oh yea, and now for a little showing off of what QORA hosting can do...

http://216.126.198.26:9090/2ndtest/nature

This image is hosted FULLY ON THE BLOCKCHAIN. Took about 300 tx to be there, but is now fully hosted decentralized via QORA.

I will be doing some more tests and putting up some more cool stuff on QORA hosting shortly!

[YukonCoinelius]

Running the wallet in forging mode several days. 
There are only ever 4 lasting connections (other ones show up transiently for a few seconds and go away). 
For example  (from  File-Debug-Peers)

Code:

106.187.42.214   271687
188.166.16.64    271690
128.199.45.81    271706
5.230.145.31     271705

The number after the IP above is "height".    The heights are all widely different!!  And they generally stay different, all counting up or jumping ahead to catch each other, but never in unison.  I've *never* seen them all the same height!

Why, what's going on?   Is this right, or just a debug display issue?  It seems worrisome, and maybe indicates why there are syncing/forking problems.   If all of these nodes were actively forging, seems they'd all be chaining up different blocks.

Also, why only 4 peers?  I thought there were more other nodes active by now?   Anyone have active node IPs not shown in that list?

[MikeMike]

Running the wallet in forging mode several days.  
There are only ever 4 lasting connections (other ones show up transiently for a few seconds and go away).  
For example  (from  File-Debug-Peers)

Code:

106.187.42.214   271687
188.166.16.64    271690
128.199.45.81    271706
5.230.145.31     271705

The number after the IP above is "height".    The heights are all widely different!!  And they generally stay different, all counting up or jumping ahead to catch each other, but never in unison.  I've *never* seen them all the same height!

Why, what's going on?   Is this right, or just a debug display issue?  It seems worrisome, and maybe indicates why there are syncing/forking problems.   If all of these nodes were actively forging, seems they'd all be chaining up different blocks.

Also, why only 4 peers?  I thought there were more other nodes active by now?   Anyone have active node IPs not shown in that list?

I get up to 10 peers fade in and out. They try

to connect but dont.



Here are a few other IPs that try to connect:

60.29.233.154
60.172.227.64

[YukonCoinelius]

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.

They/we need an external Block Explorer, because the built-in one is self-referential (it shows what the node itself is doing).  It's helpful for quick reference, but if a forging node (like Poloniex) starts spinning away on it's own fork, their own block explorer can't show that.  They need the external one to check if their blocks are getting out to the network.

I've successfully gotten two hosted wallets up, the first one may be slower than the second, I'm waiting on the DNS to propagate to the qora.tech domain.
I think I will also put it on qora.online

http://burstkore.ddns.net:9090/index/blockexplorer.html
http://qora.tech:9090/index/blockexplorer.html

I checked out the one at burstkore, looks good, nice work!

[crowetic]

Running the wallet in forging mode several days. 
There are only ever 4 lasting connections (other ones show up transiently for a few seconds and go away). 
For example  (from  File-Debug-Peers)

Code:

106.187.42.214   271687
188.166.16.64    271690
128.199.45.81    271706
5.230.145.31     271705

The number after the IP above is "height".    The heights are all widely different!!  And they generally stay different, all counting up or jumping ahead to catch each other, but never in unison.  I've *never* seen them all the same height!

Why, what's going on?   Is this right, or just a debug display issue?  It seems worrisome, and maybe indicates why there are syncing/forking problems.   If all of these nodes were actively forging, seems they'd all be chaining up different blocks.

Also, why only 4 peers?  I thought there were more other nodes active by now?   Anyone have active node IPs not shown in that list?

I would say your db is corrupt, maybe you were on a fork at one time. please delete it and download the one I linked above, and try that.

also, there's a new node @ 216.126.198.26

[crowetic]

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.

They/we need an external Block Explorer, because the built-in one is self-referential (it shows what the node itself is doing).  It's helpful for quick reference, but if a forging node (like Poloniex) starts spinning away on it's own fork, their own block explorer can't show that.  They need the external one to check if their blocks are getting out to the network.

I've successfully gotten two hosted wallets up, the first one may be slower than the second, I'm waiting on the DNS to propagate to the qora.tech domain.
I think I will also put it on qora.online

http://burstkore.ddns.net:9090/index/blockexplorer.html
http://qora.tech:9090/index/blockexplorer.html

I checked out the one at burstkore, looks good, nice work!

The other can be seen at http://216.126.198.26:9090/index/blockexplorer.html until the DNS propagates on qora.tech.

Thanks!