⚡[ANN]⚡ ▐░Espers [ESP]░▌▐░PoW/PoS░▌▐░HMQ1725 Algo░▌ ▐░New Features░▌ - page 326.

Griffith

legendary

Activity: 1400

Merit: 1000

Quote from: Take the red pill on March 06, 2017, 12:26:38 PM

Quote from: FutureBitcoin on March 06, 2017, 07:00:02 AM

Meanwhile, the 24-volume of coin trading ESP/LTC on the novaexch is very small. And the rate has not changed for the better. Very sadly ...

Don't worry, you should buy now

not if the chain is forked. you should never buy a coin with forks in its chain. there is no way of guaranteeing that you are buying coins on the right chain

Take the red pill

sr. member

Activity: 416

Merit: 250

Quote from: FutureBitcoin on March 06, 2017, 07:00:02 AM

Meanwhile, the 24-volume of coin trading ESP/LTC on the novaexch is very small. And the rate has not changed for the better. Very sadly ...

Don't worry, you should buy now

mineru

full member

Activity: 129

Merit: 100

https://forum.cryptoinfo.net/

Quote from: TomVelvetPaws on March 05, 2017, 06:53:20 PM

Quote from: EpyxZ on March 05, 2017, 05:51:02 PM

Quote from: bluedude on March 05, 2017, 04:34:49 PM

I think there are still 2 chains going on. I synced from scratch and my new blockhash is not the same as the one here at http://espv2.miningalts.com/

So that chain is the correct one right? Just making sure before I re-sync and dload the chain again.

Here's what I suggest.It looks like there is 2 chains maybe more god forbid..Everyone that has a synced up wallet Post your block count and Time that way we can figure out if 2 chains or not then get everyone on the same chain and discard ignore one.W could probably do that by looking at nodes and just deleting them from the conf file.If we do this diligently for a bit we can figure it out being a few blocks off and minutes will show were on the same chain but big discrepancies in block count and time will show a bad chain.What you want is the highest block count with the lesser time.Any other thoughts on this?

Also look at your configuration file as well we need to make sure everyone has the same client when thats done we can work on getting everyone on the same chain as I mentioned.First things first.Create the Conf file or get peer info.It could help by posting that info here on this thread as well.Just one person running the wrong client can really screw up the system.Im not running mine at all until I figure everything out.My suggestion to coderz is to disable pow and staking until this is figured out.You all are just going to have to bear with it until its fixed. I guarantee you it will be worth the work.Normally I would have thrown in the hat as they say because of the problems.Those problems do not lay in the algorithm it's self but that being said this is a ground breaking history making ALT so its worth the work and wait.I am somewhat of a visionary and you youngsters will remember this and you will remember that I and we helped you.It is my greatest wish

Sounds good. Let's wait for coderz's release and work all this from there.

FutureBitcoin

legendary

Activity: 2674

Merit: 1138

Meanwhile, the 24-volume of coin trading ESP/LTC on the novaexch is very small. And the rate has not changed for the better. Very sadly ...

mineru

full member

Activity: 129

Merit: 100

https://forum.cryptoinfo.net/

Quote from: pallas on March 05, 2017, 02:26:51 PM

I'm against being on zpool. It will only bring casual miners which use their BTC address and that will mean constant dump and price down. Even if you use an esp address, zpool will not buy any coin on the exchange, it will only wait for the coins to be mined.
[/quote]

I agree with Pallas concerning zpool.

BelgianBoy

full member

Activity: 149

Merit: 100

Quote from: CryptoHobo on March 06, 2017, 05:40:41 AM

Quote from: BelgianBoy on March 06, 2017, 04:39:38 AM

Quote from: gawlea on March 06, 2017, 03:50:26 AM

Quote from: perez70 on March 06, 2017, 03:47:12 AM

Quote from: connexus on March 06, 2017, 03:31:11 AM

Try using the latest update v0.8.5.4, it may solve your wallet problem.

I use it!

Same here on 0.8.5.4 version of wallet.
PoS is working but is showing 0 net weight. Wallet need some adjustments but the good thing is that is working.

Same here... No stakes. Used the Espers_v0.8.5.4_Patch-6_cleanbuild-qt, and sync all the blocks trough network.

same everywhere i guess but if you do getstakinginfo in debug you'll see the netweight, funny a recent release called neuron has the exact same issue

[edit]
win 10 X64 v0.8.5.4-Patch 6

Code:

11:17:30

getpeerinfo

11:17:31

[
{
"addr" : "[2001:0:34a4:e5e4:14d3:a13:b128:96ad]:22448",
"addrlocal" : "*",
"services" : "00000001",
"lastsend" : 1488799017,
"lastrecv" : 1488799018,
"bytessent" : 61367,
"bytesrecv" : 108332,
"conntime" : 1488798940,
"pingtime" : 0.12232600,
"version" : 60020,
"subver" : "/Espers:0.8.5.4/",
"inbound" : false,
"startingheight" : 649999,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "198.245.50.213:22448",
"addrlocal" : "*",
"services" : "00000001",
"lastsend" : 1488798974,
"lastrecv" : 1488799017,
"bytessent" : 1694,
"bytesrecv" : 6084,
"conntime" : 1488798973,
"pingtime" : 0.25969000,
"version" : 60020,
"subver" : "/Espers:0.8.5.4/",
"inbound" : false,
"startingheight" : 651232,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "85.145.32.75:22448",
"addrlocal" : "*",
"services" : "00000001",
"lastsend" : 1488799017,
"lastrecv" : 1488799017,
"bytessent" : 902,
"bytesrecv" : 13548,
"conntime" : 1488798974,
"pingtime" : 0.10427700,
"version" : 60020,
"subver" : "/Espers:0.8.5.4/",
"inbound" : false,
"startingheight" : 651232,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "137.74.33.98:22448",
"addrlocal" : "*",
"services" : "00000001",
"lastsend" : 1488798980,
"lastrecv" : 1488799016,
"bytessent" : 292,
"bytesrecv" : 959,
"conntime" : 1488798980,
"pingtime" : 0.19150900,
"version" : 60020,
"subver" : "/Espers:0.8.5.4/",
"inbound" : false,
"startingheight" : 651232,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "85.255.7.224:22448",
"addrlocal" : "*",
"services" : "00000001",
"lastsend" : 1488799017,
"lastrecv" : 1488799023,
"bytessent" : 353,
"bytesrecv" : 5248,
"conntime" : 1488798980,
"pingtime" : 5.72421600,
"version" : 60020,
"subver" : "/Espers:0.8.5.4/",
"inbound" : false,
"startingheight" : 651232,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "[2001:0:d58:bbbf:30fb:d293:e020:7631]:51405",
"addrlocal" : "*",
"services" : "00000001",
"lastsend" : 1488799040,
"lastrecv" : 1488799040,
"bytessent" : 2728,
"bytesrecv" : 237,
"conntime" : 1488799040,
"pingtime" : 0.24565300,
"version" : 60020,
"subver" : "/Espers:0.8.5.4/",
"inbound" : true,
"startingheight" : 651233,
"banscore" : 0,
"syncnode" : false
}
]

Dev worked whole night on the fix, it well be released soon. Its problem with difficulty.

CryptoHobo

legendary

Activity: 1050

Merit: 1000

Quote from: BelgianBoy on March 06, 2017, 04:39:38 AM

Quote from: gawlea on March 06, 2017, 03:50:26 AM

Quote from: perez70 on March 06, 2017, 03:47:12 AM

Quote from: connexus on March 06, 2017, 03:31:11 AM

Try using the latest update v0.8.5.4, it may solve your wallet problem.

I use it!

Same here on 0.8.5.4 version of wallet.
PoS is working but is showing 0 net weight. Wallet need some adjustments but the good thing is that is working.

Same here... No stakes. Used the Espers_v0.8.5.4_Patch-6_cleanbuild-qt, and sync all the blocks trough network.

same everywhere i guess but if you do getstakinginfo in debug you'll see the netweight, funny a recent release called neuron has the exact same issue

[edit]
win 10 X64 v0.8.5.4-Patch 6

Code:

11:17:30

getpeerinfo

11:17:31

[
{
"addr" : "[2001:0:34a4:e5e4:14d3:a13:b128:96ad]:22448",
"addrlocal" : "*",
"services" : "00000001",
"lastsend" : 1488799017,
"lastrecv" : 1488799018,
"bytessent" : 61367,
"bytesrecv" : 108332,
"conntime" : 1488798940,
"pingtime" : 0.12232600,
"version" : 60020,
"subver" : "/Espers:0.8.5.4/",
"inbound" : false,
"startingheight" : 649999,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "198.245.50.213:22448",
"addrlocal" : "*",
"services" : "00000001",
"lastsend" : 1488798974,
"lastrecv" : 1488799017,
"bytessent" : 1694,
"bytesrecv" : 6084,
"conntime" : 1488798973,
"pingtime" : 0.25969000,
"version" : 60020,
"subver" : "/Espers:0.8.5.4/",
"inbound" : false,
"startingheight" : 651232,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "85.145.32.75:22448",
"addrlocal" : "*",
"services" : "00000001",
"lastsend" : 1488799017,
"lastrecv" : 1488799017,
"bytessent" : 902,
"bytesrecv" : 13548,
"conntime" : 1488798974,
"pingtime" : 0.10427700,
"version" : 60020,
"subver" : "/Espers:0.8.5.4/",
"inbound" : false,
"startingheight" : 651232,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "137.74.33.98:22448",
"addrlocal" : "*",
"services" : "00000001",
"lastsend" : 1488798980,
"lastrecv" : 1488799016,
"bytessent" : 292,
"bytesrecv" : 959,
"conntime" : 1488798980,
"pingtime" : 0.19150900,
"version" : 60020,
"subver" : "/Espers:0.8.5.4/",
"inbound" : false,
"startingheight" : 651232,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "85.255.7.224:22448",
"addrlocal" : "*",
"services" : "00000001",
"lastsend" : 1488799017,
"lastrecv" : 1488799023,
"bytessent" : 353,
"bytesrecv" : 5248,
"conntime" : 1488798980,
"pingtime" : 5.72421600,
"version" : 60020,
"subver" : "/Espers:0.8.5.4/",
"inbound" : false,
"startingheight" : 651232,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "[2001:0:d58:bbbf:30fb:d293:e020:7631]:51405",
"addrlocal" : "*",
"services" : "00000001",
"lastsend" : 1488799040,
"lastrecv" : 1488799040,
"bytessent" : 2728,
"bytesrecv" : 237,
"conntime" : 1488799040,
"pingtime" : 0.24565300,
"version" : 60020,
"subver" : "/Espers:0.8.5.4/",
"inbound" : true,
"startingheight" : 651233,
"banscore" : 0,
"syncnode" : false
}
]

cryptomass

sr. member

Activity: 325

Merit: 250

Quote from: TomVelvetPaws on March 05, 2017, 06:53:20 PM

Quote from: EpyxZ on March 05, 2017, 05:51:02 PM

Quote from: bluedude on March 05, 2017, 04:34:49 PM

I think there are still 2 chains going on. I synced from scratch and my new blockhash is not the same as the one here at http://espv2.miningalts.com/

So that chain is the correct one right? Just making sure before I re-sync and dload the chain again.

Here's what I suggest.It looks like there is 2 chains maybe more god forbid..
Everyone that has a synced up wallet Post your block count and Time that way we can figure out if 2 chains or not then get everyone on the same chain and discard ignore one.
W could probably do that by looking at nodes and just deleting them from the conf file.
If we do this diligently for a bit we can figure it out being a few blocks off and minutes will show were on the same chain but big discrepancies in block count and time will show a bad chain.
What you want is the highest block count with the lesser time.Any other thoughts on this?

Also look at your configuration file as well we need to make sure everyone has the same client when thats done we can work on getting everyone on the same chain as I mentioned.First things first.

Create the Conf file or get peer info.
It could help by posting that info here on this thread as well.Just one person running the wrong client can really screw up the system.
Im not running mine at all until I figure everything out.
My suggestion to coderz is to disable pow and staking until this is figured out.You all are just going to have to bear with it until its fixed.
I guarantee you it will be worth the work.
Normally I would have thrown in the hat as they say because of the problems.
Those problems do not lay in the algorithm it's self but that being said this is a ground breaking history making ALT so its worth the work and wait.
I am somewhat of a visionary and you youngsters will remember this and you will remember that I and we helped you.It is my greatest wish

Hi.
I'm at block 651210, March 06, 2017, 09:59:42 AM Bitcointalk time.
Client v0.8.5.4-Patch 6 compiled on Ubuntu.

Peerinfo:
{
"addr" : "85.145.32.75:22448",
"addrlocal" : "151.57.135.142:27107",
"services" : "00000001",
"lastsend" : 1488794314,
"lastrecv" : 1488794316,
"bytessent" : 1667,
"bytesrecv" : 5227,
"conntime" : 1488794062,
"pingtime" : 2.31932400,
"version" : 60020,
"subver" : "/Espers:0.8.5.4/",
"inbound" : false,
"startingheight" : 651209,
"banscore" : 0,
"syncnode" : true
}

BelgianBoy

full member

Activity: 149

Merit: 100

Quote from: gawlea on March 06, 2017, 03:50:26 AM

Quote from: perez70 on March 06, 2017, 03:47:12 AM

Quote from: connexus on March 06, 2017, 03:31:11 AM

Try using the latest update v0.8.5.4, it may solve your wallet problem.

I use it!

Same here on 0.8.5.4 version of wallet.
PoS is working but is showing 0 net weight. Wallet need some adjustments but the good thing is that is working.

Same here... No stakes. Used the Espers_v0.8.5.4_Patch-6_cleanbuild-qt, and sync all the blocks trough network.

gawlea

hero member

Activity: 756

Merit: 579

Quote from: perez70 on March 06, 2017, 03:47:12 AM

Quote from: connexus on March 06, 2017, 03:31:11 AM

Try using the latest update v0.8.5.4, it may solve your wallet problem.

I use it!

Same here on 0.8.5.4 version of wallet.
PoS is working but is showing 0 net weight. Wallet need some adjustments but the good thing is that is working.

dox-ua

full member

Activity: 237

Merit: 101

Quote from: xtrembash on March 05, 2017, 04:01:47 PM

pow broken
but some1 is mining some blocks
who is he ?!
http://espv2.miningalts.com/

my node got two pos blocks , espv2.miningalts.com shows it was three. last one (third) is trying to be confirmed for about 8-10 times with no success, but it already shows as mined. dev's got to fix this imo. wallet synced yesterday added nodes from posts at 500-501 page

perez70

sr. member

Activity: 327

Merit: 251

SmartHoldem.IO

Quote from: connexus on March 06, 2017, 03:31:11 AM

Try using the latest update v0.8.5.4, it may solve your wallet problem.

I use it!

connexus

hero member

Activity: 774

Merit: 503

Quote from: perez70 on March 06, 2017, 03:06:13 AM

Maybe something went wrong with the op.

Try using the latest update v0.8.5.4, it may solve your wallet problem.

perez70

sr. member

Activity: 327

Merit: 251

SmartHoldem.IO

Maybe something went wrong with the op.

TomVelvetPaws

hero member

Activity: 616

Merit: 500

BTC=1GjeqWFLc4TBDg3bwdQk9ZWnEoNPCT9t6G

Quote from: marcelocoin on March 06, 2017, 12:17:08 AM

Hello there is no active pool?

Quote from: marcelocoin on March 06, 2017, 12:17:08 AM

Hello there is no active pool?

Did you even read anything? Lol Cheesy

marcelocoin

hero member

Activity: 1085

Merit: 500

hi =D

Hello there is no active pool?

TomVelvetPaws

hero member

Activity: 616

Merit: 500

BTC=1GjeqWFLc4TBDg3bwdQk9ZWnEoNPCT9t6G

Quote from: EpyxZ on March 05, 2017, 05:51:02 PM

Quote from: bluedude on March 05, 2017, 04:34:49 PM

I think there are still 2 chains going on. I synced from scratch and my new blockhash is not the same as the one here at http://espv2.miningalts.com/

So that chain is the correct one right? Just making sure before I re-sync and dload the chain again.

Here's what I suggest.It looks like there is 2 chains maybe more god forbid..Everyone that has a synced up wallet Post your block count and Time that way we can figure out if 2 chains or not then get everyone on the same chain and discard ignore one.W could probably do that by looking at nodes and just deleting them from the conf file.If we do this diligently for a bit we can figure it out being a few blocks off and minutes will show were on the same chain but big discrepancies in block count and time will show a bad chain.What you want is the highest block count with the lesser time.Any other thoughts on this?

Also look at your configuration file as well we need to make sure everyone has the same client when thats done we can work on getting everyone on the same chain as I mentioned.First things first.Create the Conf file or get peer info.It could help by posting that info here on this thread as well.Just one person running the wrong client can really screw up the system.Im not running mine at all until I figure everything out.My suggestion to coderz is to disable pow and staking until this is figured out.You all are just going to have to bear with it until its fixed. I guarantee you it will be worth the work.Normally I would have thrown in the hat as they say because of the problems.Those problems do not lay in the algorithm it's self but that being said this is a ground breaking history making ALT so its worth the work and wait.I am somewhat of a visionary and you youngsters will remember this and you will remember that I and we helped you.It is my greatest wish

EpyxZ

hero member

Activity: 994

Merit: 500

Quote from: bluedude on March 05, 2017, 04:34:49 PM

I think there are still 2 chains going on. I synced from scratch and my new blockhash is not the same as the one here at http://espv2.miningalts.com/

So that chain is the correct one right? Just making sure before I re-sync and dload the chain again.

bluedude

hero member

Activity: 714

Merit: 500

y²=x3+ax+b, a=0,b=7

I think there are still 2 chains going on. I synced from scratch and my new blockhash is not the same as the one here at http://espv2.miningalts.com/

xtrembash

sr. member

Activity: 473

Merit: 250

pow broken
but some1 is mining some blocks
who is he ?!
http://espv2.miningalts.com/

Topic: ⚡[ANN]⚡ ▐░Espers [ESP]░▌▐░PoW/PoS░▌▐░HMQ1725 Algo░▌ ▐░New Features░▌ - page 326. (Read 924238 times)