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

[Take the red pill]

To ESPERS community

If we wish to really help CryptoCoderz and Espers than we have to get ESP to https://www.zpool.ca

How?
We have to move ESP to one of this exchanges: Bittrex, Poloniex, BLEUTRADE, Yobit, Cryptopia or CCEX
We can forget about Yobit as it still on old ESP chain and will not move to new until they see profit, so the best chance is to win voting at C-CEX. Whit 307 votes there is a good chance to be listed in next weeks, but you all have to vote: https://c-cex.com/?id=vote&coin=esp
Here is the condition from zpool to add ESP: https://twitter.com/_zpool_/status/837660603279884288

(Maybe DEV could also help herewith some bounty)

Why?
If we win voting at C-CEX and start trading at C-CEX zpool will add ESPERS and HMQ1725 algo to their multi-pool. This means that you all could mine in any algo listed (at the moment 30 supported algho) and be paid in ESP or BTC. If you choose to be paid in ESP zpool will buy ESP at C-CEX and send to you wallet!

This way the price will for sure increase and maybe we will help also DEV to finish next steps in development!

What do you think about this idea!? Will you help?

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.

OK... any better idea at the moment?! What if we still try to get to C-CEX first and than will see what will happen

[Lucky - Luciano]

To ESPERS community

If we wish to really help CryptoCoderz and Espers than we have to get ESP to https://www.zpool.ca

How?
We have to move ESP to one of this exchanges: Bittrex, Poloniex, BLEUTRADE, Yobit, Cryptopia or CCEX
We can forget about Yobit as it still on old ESP chain and will not move to new until they see profit, so the best chance is to win voting at C-CEX. Whit 307 votes there is a good chance to be listed in next weeks, but you all have to vote: https://c-cex.com/?id=vote&coin=esp
Here is the condition from zpool to add ESP: https://twitter.com/_zpool_/status/837660603279884288

(Maybe DEV could also help herewith some bounty)

Why?
If we win voting at C-CEX and start trading at C-CEX zpool will add ESPERS and HMQ1725 algo to their multi-pool. This means that you all could mine in any algo listed (at the moment 30 supported algho) and be paid in ESP or BTC. If you choose to be paid in ESP zpool will buy ESP at C-CEX and send to you wallet!

This way the price will for sure increase and maybe we will help also DEV to finish next steps in development!

What do you think about this idea!? Will you help?

 First should dev   to help himself. You're talking about success and dev weeks is not able to make stable wallet and  wallet which work?! Do not be naive. The first stable wallet and then the rest.

[xtrembash]

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

[bluedude]

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/

[EpyxZ]

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.

[TomVelvetPaws]

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

[marcelocoin]

Hello there is no active pool?

[TomVelvetPaws]

Hello there is no active pool?

Hello there is no active pool?

   
Did you even read anything?  Lol 

[perez70]

Maybe something went wrong with the op.

[connexus]

Maybe something went wrong with the op.

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

[perez70]

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

I use it!

[dox-ua]

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

[gawlea]

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.

[BelgianBoy]

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.

[cryptomass]

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
}

[CryptoHobo]

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
}
]

[BelgianBoy]

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.

[mineru]

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.

[FutureBitcoin]

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]

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.