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

[noobwhosuckatlife]

Can we hit YObit sometime soon?)

https://twitter.com/bitwarriorX/status/724564619562377216

Attaboy!

[CryptoCoderz]

not sure if you read my post here,

https://bitcointalk.org/index.php?topic=1434700.msg14656785#msg14656785

but that is what happened.


@CosaNostra, i have seen that fix you posted work for other coins. However, rebroadcasting it to the network does not work in this case due to the issue it stems from being different that the one that happened with dash. This base issue with espers is a little more complex. (i had tried a rebroadcast with no success. if it works for ene1980 more power to him. ill have to try again)

@ene1980, it looks from the Net amount column that you used a large input (possibly a reverse-ico deposit) although without looking at your wallet itself i cant quite tell. it is possible that those 300 million coins are no longer sendable. if that is the case, i am sorry that happened dude.

Thank you for offering condolences Griffith and continually assisting us.
As stated previously we will be updating the source and client to resolve these issues

@ene1980 - your balance should remain spendable.
The transaction fee however is as Griffith stated below recognized input which is most likely causing your issue.
We will make sure to work with you to resolve any issues.
Be sure you have abackup of your dat file.

[ene1980]

Houston, we have a problem.
Maybe...

Status: 0/unconfirmed
Date: 25/04/2016 14:27
To: EWKV45sKLV5u8QzNwr9JfHjd7mY8PfGXAS
Debit: -305991288.00 ESP
Transaction fee: -0.0001 ESP
Net amount: -305991288.0001 ESP
Transaction ID: 4c5acabcebafd7c8ade594249a22db307cc8b90b2111159736de6c1d9b7274d0

more than 30 min and still 0 confirmation, when i search transaction id on explorer, say me dont exist.

see my post above

Ok, tnx  

So now just need someone who can enter this in the console:

sendrawtransaction 01000000030d2d11f9c7c7456604e43d279c5e8c61c014488df264f3f2dd81e42a09d4332b00000 0006a47304402201cf677480e8cbd5992f83295e5e04a63f0d4969a35c461eda52af0a57e523643 02205b4c54b7fac544fae78c75501e7ae608453e1e934caf6892c968351f363dce8c012102188f3 fe549979c9bf1572d83aad96eeb7fe921c5c824be65f4602e5b853712efffffffff4468b7b66655 4045a409631c089c31a1d9d6141560f6a2fd8229108079a8073c000000006b483045022100f04ed 43ff61e35a88e1a0d71e9769164b185451767b15ba3774a34b4b7c116560220355508dd52ba3a80 87a68b3829e232140c37d349c2bf3419e92206bed1838ec20121022ce591a19aa5257bc11147efd 06e320d1ab70b44c02c13afeb5d4fdae50e3ebaffffffff573c03213dc094b55ea6ef7d3c1ebcb5 ee2460999382b6a1275d2c9bcad7bae50c0000006a473044022005c03f77ed8ca4618655fefe7d6 c634eb6ce8136bb88a76fcfe385092f7df53302207a2211d6ba6f164a988716b37c6b703796de43 99981b450f39fd55f4d25c8d99012102188f3fe549979c9bf1572d83aad96eeb7fe921c5c824be6 5f4602e5b853712efffffffff0200db336ad41b00001976a914906964c42631b57dc0cbf30c9ae0 0f520cef1fd488acac000000000000001976a91470d69c3e04eaede2d3ce478f93e24ebfc8c9786 288ac00000000

im right?

Seems like incomplete string or something else wrong. Are you sure you've copied all right?

I tryed again, and this is what i receive:



01000000030d2d11f9c7c7456604e43d279c5e8c61c014488df264f3f2dd81e42a09d4332b00000 0006a47304402201cf677480e8cbd5992f83295e5e04a63f0d4969a35c461eda52af0a57e523643 02205b4c54b7fac544fae78c75501e7ae608453e1e934caf6892c968351f363dce8c012102188f3 fe549979c9bf1572d83aad96eeb7fe921c5c824be65f4602e5b853712efffffffff4468b7b66655 4045a409631c089c31a1d9d6141560f6a2fd8229108079a8073c000000006b483045022100f04ed 43ff61e35a88e1a0d71e9769164b185451767b15ba3774a34b4b7c116560220355508dd52ba3a80 87a68b3829e232140c37d349c2bf3419e92206bed1838ec20121022ce591a19aa5257bc11147efd 06e320d1ab70b44c02c13afeb5d4fdae50e3ebaffffffff573c03213dc094b55ea6ef7d3c1ebcb5 ee2460999382b6a1275d2c9bcad7bae50c0000006a473044022005c03f77ed8ca4618655fefe7d6 c634eb6ce8136bb88a76fcfe385092f7df53302207a2211d6ba6f164a988716b37c6b703796de43 99981b450f39fd55f4d25c8d99012102188f3fe549979c9bf1572d83aad96eeb7fe921c5c824be6 5f4602e5b853712efffffffff0200db336ad41b00001976a914906964c42631b57dc0cbf30c9ae0 0f520cef1fd488acac000000000000001976a91470d69c3e04eaede2d3ce478f93e24ebfc8c9786 288ac00000000

not sure if you read my post here,

https://bitcointalk.org/index.php?topic=1434700.msg14656785#msg14656785

but that is what happened.


@CosaNostra, i have seen that fix you posted work for other coins. However, rebroadcasting it to the network does not work in this case due to the issue it stems from being different that the one that happened with dash. This base issue with espers is a little more complex. (i had tried a rebroadcast with no success. if it works for ene1980 more power to him. ill have to try again)

@ene1980, it looks from the Net amount column that you used a large input (possibly a reverse-ico deposit) although without looking at your wallet itself i cant quite tell. it is possible that those 300 million coins are no longer sendable. if that is the case, i am sorry that happened dude.

This coin i have already send to novaexchange some days ago, take back in wallet yesterday, and today when tryed again to send to nova had this problem.
So are not directly from the reverse ico, other transaction was all fine

[dukektm]

Can we hit YObit sometime soon?)

https://twitter.com/bitwarriorX/status/724564619562377216

retweet 

[noobwhosuckatlife]

Can we hit YObit sometime soon?)

https://twitter.com/bitwarriorX/status/724564619562377216

retweet 

Can I re-retweet?

[Selsonblue]

yes we did Espers Market now is bigger.   Thank-you David (owner) of Novaexchange

Espers Market Now includes
https://novaexchange.com/market/ESP_BTCD/ Bitcoindark
https://novaexchange.com/market/ESP_CLAM/ Clamcoin
https://novaexchange.com/market/ESP_MOON/ Mooncoin
https://novaexchange.com/market/ESP_POT/ Potcoin
https://novaexchange.com/market/ESP_RADS/ Radium
https://novaexchange.com/market/ESP_SPN/ Spartancoin
https://novaexchange.com/market/ESP_VRC/ Vericoin
Plus all the other ones we already had over there

Don't forget our friend rapta owner of coingather.com
https://www.coingather.com/exchange/020/ESP 020Londoncoin
https://www.coingather.com/exchange/BC/ESP Blackcoin
And you can also trade RDD DOGE DGB & ASC in the ESP markets also

Awesome so many pairs! And it has a Radium pair!!! Thats great! Im really interested in this project.

[CC-Resurgam]

@Everyone
Please note that it has been brought to our attention that if you send too small of amount then there will be an issue with the wallet and may cause you to lose coins.
As a temporary fix please insert;

paytxfee=0.01

to your Espers.conf file

This will charge you .01 ESP and thus make it impossible to send an amount lower then that. this will fix the issue. However we will fix this and have the updated client As Soon As Possible.

Thank you for your time,
-Jacob

EDIT; THIS IS ONLY AN ISSUE IF YOU SEND LESS THEN .001 ESP. MOST IF NOT ALL BLOCKCHAINS RUN INTO THIS ERROR JUST DON'T REALIZE IT BECAUSE EVERYONE ELSE CHARGES FEES.
WE DO NOT WANT TO CHARGE FEES EVER. WE WILL FIX THE ISSUE SO YOU WILL STILL NOT BE FEE'D.

[CryptoCoderz]

2Devs, when can we test PoR system?

Hold on there speedy. We are still in alpha of just the PoW system. We will get there don't worry.




@everyone -
in response to the latest discovered bugs we advise everyone set a tx fee to 0.01 so that the issue of alower amount being lost or ignored is no longer apossibility.
We will update the source and client soon to resolve this across the board.
Again Thank you goes to griff for being an upstanding community member and quickly pointing this out.
As this is an alpha chain we strongly advise periodic backups of your dat file

[ocminer]

Actually you won't be losing the coins completely, as they're never send across the network, but you'd need to dump the privkey of your receiving address (or all receiving addresses), clear your wallet + blockchain data (backup first) and in a fresh, fully synchronized client you'd import the privkey(s) again and your funds should be back.

However, setting txfee to 0.01 and/or fixing the bug is surely the best way to solve it Just wanted to make sure that nobody will lose any coins, they're still there.

[CryptoCoderz]

Actually you won't be losing the coins completely, as they're never send across the network, but you'd need to dump the privkey of your receiving address (or all receiving addresses), clear your wallet + blockchain data (backup first) and in a fresh, fully synchronized client you'd import the privkey(s) again and your funds should be back.

However, setting txfee to 0.01 and/or fixing the bug is surely the best way to solve it Just wanted to make sure that nobody will lose any coins, they're still there.

Definitely ocminer that is agreat resolution to anyone with astuck transaction. Thank you!!!

Also we will simply have the client charge a 0.01 tx fee if the user inputs avalue lower than 0.01 and address the issue more thouroughly later.
Our main goal at this time will be to keep everyone's tokens safe and secure.
Thank you again for your help.

[ene1980]

Actually you won't be losing the coins completely, as they're never send across the network, but you'd need to dump the privkey of your receiving address (or all receiving addresses), clear your wallet + blockchain data (backup first) and in a fresh, fully synchronized client you'd import the privkey(s) again and your funds should be back.

However, setting txfee to 0.01 and/or fixing the bug is surely the best way to solve it Just wanted to make sure that nobody will lose any coins, they're still there.

Thank you!! all fine now 

[ocminer]

Actually you won't be losing the coins completely, as they're never send across the network, but you'd need to dump the privkey of your receiving address (or all receiving addresses), clear your wallet + blockchain data (backup first) and in a fresh, fully synchronized client you'd import the privkey(s) again and your funds should be back.

However, setting txfee to 0.01 and/or fixing the bug is surely the best way to solve it Just wanted to make sure that nobody will lose any coins, they're still there.

Thank you!! all fine now 

[CryptoCoderz]

Actually you won't be losing the coins completely, as they're never send across the network, but you'd need to dump the privkey of your receiving address (or all receiving addresses), clear your wallet + blockchain data (backup first) and in a fresh, fully synchronized client you'd import the privkey(s) again and your funds should be back.

However, setting txfee to 0.01 and/or fixing the bug is surely the best way to solve it Just wanted to make sure that nobody will lose any coins, they're still there.

Thank you!! all fine now  

Ocminer you rock.
WE will promptly patch the client asap.

[DeCrypterManiac]

Actually you won't be losing the coins completely, as they're never send across the network, but you'd need to dump the privkey of your receiving address (or all receiving addresses), clear your wallet + blockchain data (backup first) and in a fresh, fully synchronized client you'd import the privkey(s) again and your funds should be back.

However, setting txfee to 0.01 and/or fixing the bug is surely the best way to solve it Just wanted to make sure that nobody will lose any coins, they're still there.

Thank you!! all fine now 

Worked for me too, thanks oc !

[Arrakeen]

Awesome news regarding YoBit 

Congrats!

Can't wait for ESP to finally take off

[CryptoCoderz]

Awesome news regarding YoBit 

Congrats!

Can't wait for ESP to finally take off

Definitely bud, just a couple small things to take care of first though. 

[pi2u]

Awesome news regarding YoBit 

Congrats!

Can't wait for ESP to finally take off

Can't wait to see some big dumps

[CryptoCoderz]

Awesome news regarding YoBit 

Congrats!

Can't wait for ESP to finally take off

Can't wait to see some big dumps

Absolutely. We'll be waiting for them cheap ESP

[locopao]

any news regarding yobit?
still unavailable

[CryptoCoderz]

any news regarding yobit?
still unavailable

We paid on Friday. They stated two business days so either Tuesday or Wednesday.