when will be next distrubion??? and when you paid my friends his nickname boss and number 117
As stated in previous posts We will elaborate on that today. As for your friend, they need to pm us through bitcoin garden. Please let's respect the rules of this forum. We'll make sure to process your request Thank you for notifying us he write two letters and you dont answer him Bud, most of the team is at work. For the next three hours we won't have much time to answer messages please understand he write your on bitcoin garden yesterday and two day ago please send him his coins EaHdWrBwVjZoM3oeFEfHM4d3bHqp7HWGGQ I understand. Please don't assume we are ignoring you. We have been busy. We'll take care of it today. |
|
|
|
What makes you think google is mining? Extreme hash rate Is that 241Khash? Must be a nice Octo-core or possibly Xeon cpu. Nova was also the first. yes it could be true! but is coingather new exchange like nova? Coin gather is still a fairly young exchange from what I've seen. Correct me if I'm wrong but from what I've seen that's what I've drawn up as far as aconclusion |
|
|
|
What makes you think google is mining? Extreme hash rate Is that 241Khash? Must be a nice Octo-core or possibly Xeon cpu(s). Nova was also the first. |
|
|
|
Just remember res. This chain doesn't have the network hash meter yet
oh i got ya. that is the pool's hash but not the networks. sorry forgot  No prob just wanted to point that out Hey Chief, any news or updates on the wallet? Amore Jaz We will get cracking on it as soon as we are in front of our systems. Currently the team are at their day jobs including myself |
|
|
|
when will be next distrubion??? and when you paid my friends his nickname boss and number 117
As stated in previous posts We will elaborate on that today. As for your friend, they need to pm us through bitcoin garden. Please let's respect the rules of this forum. We'll make sure to process your request Thank you for notifying us he write two letters and you dont answer him Bud, most of the team is at work. For the next three hours we won't have much time to answer messages please understand |
|
|
|
Just remember res. This chain doesn't have the network hash meter yet
oh i got ya. that is the pool's hash but not the networks. sorry forgot No prob just wanted to point that out |
|
|
|
That number may be incorrect. It states that the Pool hash and Network hash are the same. As i am personally mining solo at over 20KH/s that cannot be correct. I think that this is around 31.24720 MH/s What i am saying is that Nova pool is reporting Pool Hash: 28,654.52 KH/s Pool Workers: 312 Net Hash: 28,654.52 KH/s With many people solo mining the Pool hash and the network hash cannot be the same. these numbers are false. the network hash is probably 28,654.52 KH/s While the pools Hash is something less then that. Just remember res. This chain doesn't have the network hash meter yet |
|
|
|
Nice!! diff. around 43. more miners!! always need moar!  |
|
|
|
when will be next distrubion??? and when you paid my friends his nickname boss and number 117
As stated in previous posts We will elaborate on that today.
As for your friend, they need to pm us through bitcoin garden. Please let's respect the rules of this forum. We'll make sure to process your request Thank you for notifying us I miss the 1st airdrop  hope i can make it in the 2nd. Just buying some. Any info on when will the 2nd airdrop take place? I missed the first one too  |
|
|
|
Hello all,
It seems Griffith and ocminer have made it their duty to ensure to point out any possible flaw with the system.
big thank you to them for saving us a ton of work and headache in the future.
In addition to the tx size limit issue that we will be addressing today we will also address the tx fee to ensure that no one "loses coins".
Although we may be less active in the forum today it is because we are correcting the pointed out issues in this alpha launch.
The updates will not affect your coin balance. We will announce the update and what the changes entail later this evening.
Again Thank you all for being a part of this project!
nah, i wouldnt say that. i originally wasnt going to say anything about the small tx problem but ocminer might have had a problem because of it so i did. ill wait until you resolve the actual issue behind that before mentioning anything else Oh my there's more? Thank you for bug testing our system so extensively. This will save a lot of headache for the users and our team alike. Be sure to PM your ESP address if you'd like we would love to tip you some for the help. Again Thank you and looking forward to further assistance. Edit: although if you could favor us with the other info you've discovered we could offer a more inclusive update to the community since I'm personally stuck at my day job anyway like the other members of the team. |
|
|
|
when will be next distrubion??? and when you paid my friends his nickname boss and number 117
As stated in previous posts We will elaborate on that today. As for your friend, they need to pm us through bitcoin garden. Please let's respect the rules of this forum. We'll make sure to process your request Thank you for notifying us |
|
|
|
@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.
I think at one moment - Unique Auto-Generating Configuer
rewrote my custom written (which had only addnodes in it) espers.conf with auto generated one. So it might happen -iThink- that paytxfee=0.01 would not be in new auto generated one.. with wallet restart?... or it creates it only once till erased? but coins can be saved with private key. so it doesnt matter During launch of the client The auto generated config checks to see if you already have aconfig. If not it generates one for you. If you already have one it skips over We will double and triple check however during pre launch testing this is the way it worked as we wanted to make sure users can set their own config Verified. The config is skipped if it already exists |
|
|
|
any news regarding yobit?
still unavailable
As previously stated we paid on Friday. They stated two business days so either Tuesday or Wednesday. That's really great news! Thanks for your answer! That's what we're here for Let us know if you have any other questions we will do our best to respond as quickly as possible. |
|
|
|
any news regarding yobit?
still unavailable
We paid on Friday. They stated two business days so either Tuesday or Wednesday. |
|
|
|
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 |
|
|
|
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. |
|
|
|
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   
WE will promptly patch the client asap. |
|
|
|
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. |
|
|
|
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
|
|
|
|
not sure if you read my post here, https://bitcointalk.org/index.php?topic=1434700.msg14656785#msg14656785but 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. |
|
|
|
|
Show Posts
