[ANN] ★★ EBT Coin - Entropybit 100% PoS - Multipool - Bugfix version 4.0.3! ★★

[EBT]

why coins become forked for every round stake?
3 month ago it was 2000 EBT
today it is 255*8 EBT

or im missing something?

Each mint produces two transactions, both of equal size and half the value of the original stake plus the mint.

That's how Proof-of-Stake works.

You may want to consolidate your transactions from time to time.

[1524462942]

1524462942

[1524462942]

1524462942

[EBT]

it wasn't a disk issue, db.log shows

Code:

Lock table is out of available lock entries

This is a common problem with cryptocurrencies, including bitcoin. It most likely has to do with your OS.

http://bitcoin.stackexchange.com/questions/13354/bitcoind-stuck-lock-table-is-out-of-available-lock-entries

edit:

Actually, it seems that you have a very large wallet. Assuming your computer can handle the change, you can fix this error by increasing the following value in db.cpp. Then recompile the daemon:

Code:

db.cpp:    dbenv.set_lk_max_locks(10000);

[DannyTom]

EBT plummet in price (probably due to the 100% APR kicking in), now its a good time to mine cheap EBT at http://gagapool.pw/

This is probably day traders who keep all of their EBT on the exchange and don't stake their coin.

I agree...and I'm buying.

Or mine on gagapool, we are really loosing EBT miners.

Oh, I'm mining too. 

[xminer2014]

it wasn't a disk issue, db.log shows

Code:

Lock table is out of available lock entries

This is a common problem with cryptocurrencies, including bitcoin. It most likely has to do with your OS.

http://bitcoin.stackexchange.com/questions/13354/bitcoind-stuck-lock-table-is-out-of-available-lock-entries

edit:

Actually, it seems that you have a very large wallet. Assuming your computer can handle the change, you can fix this error by increasing the following value in db.cpp. Then recompile the daemon:

Code:

db.cpp:    dbenv.set_lk_max_locks(10000);

It's not a large wallet, just a 3 months old wallet for the pool. Deleting the blockchain and redownload it solved the issue.

[xminer2014]

EBT payment has been frozen on gagapool, due to poloniex freezes withdraw.

[sellbuy]

how to handle that?
it begun with zero EBT blocks, spamming my debug.log with tons of this

Code:

ERROR: GetKernelStakeModifier() : reached best block 7f682c15fbeefee90ca048238613c88cc3eb80b717e21835099c9cb6742c5f9d at height 394167 from block 69d27940c604b26e5442d0f1b48bf15cc41d122f225a5ac9a8aca918f66b264a
ERROR: GetKernelStakeModifier() : reached best block 7f682c15fbeefee90ca048238613c88cc3eb80b717e21835099c9cb6742c5f9d at height 394167 from block 7e390471d0c81d42779fb1bd6e2234430080e16db4f55f4c939d991ad065186a
ERROR: GetKernelStakeModifier() : reached best block 7f682c15fbeefee90ca048238613c88cc3eb80b717e21835099c9cb6742c5f9d at height 394167 from block d2d4fe7cf53c49e4446039c9b90009eeece9bc27a18790dc18d6c1121282240f
ERROR: GetKernelStakeModifier() : reached best block 7f682c15fbeefee90ca048238613c88cc3eb80b717e21835099c9cb6742c5f9d at height 394167 from block 7f14f1702ae59e75d491fa6121b4b9df67b3f89d9f1480508d34cfa975cc961f
ERROR: GetKernelStakeModifier() : reached best block 7f682c15fbeefee90ca048238613c88cc3eb80b717e21835099c9cb6742c5f9d at height 394167 from block 1f764af838b4289b70ba48413007d4ac94067ca46e85ffd6c5df34caa8ae4793
ERROR: GetKernelStakeModifier() : reached best block 7f682c15fbeefee90ca048238613c88cc3eb80b717e21835099c9cb6742c5f9d at height 394167 from block d6f1591d55ab17b07197a3d959ca375a50114a3d3aea71bdbde3f4e9e0c20145
ERROR: GetKernelStakeModifier() : reached best block 7f682c15fbeefee90ca048238613c88cc3eb80b717e21835099c9cb6742c5f9d at height 394167 from block 690c2f09cda163cd10340c4c05d44eac60a816fd8479f7ff1285588b5c502efb

[xminer2014]

Payment from gagapool for EBT are sent, withdraw issues resolved.

[xminer2014]

EBT payment will be delayed (again ) until polo unfreeze the withdraws of EBT.

[sellbuy]

my wallet is stuck on the block 395324
do you have the same issue?

[xminer2014]

poloniex tells me that the blockchain has forked so they has frozen all the withdraws. What is happening?

[EBT]

poloniex tells me that the blockchain has forked so they has frozen all the withdraws. What is happening?

The chain is not forked!

Blocks are taking a long time because of a bug in the code, which has been fixed. The fix is now in the source tree at https://github.com/CoinWhisperer/EBT

We will have new wallets available within 12 hours.

[xminer2014]

poloniex tells me that the blockchain has forked so they has frozen all the withdraws. What is happening?

The chain is not forked!

Blocks are taking a long time because of a bug in the code, which has been fixed. The fix is now in the source tree at https://github.com/CoinWhisperer/EBT

We will have new wallets available within 12 hours.

Can you please contact poloniex about this, they think it is and they are freezing all EBT withdraws.

[EBT]

poloniex tells me that the blockchain has forked so they has frozen all the withdraws. What is happening?

The chain is not forked!

Blocks are taking a long time because of a bug in the code, which has been fixed. The fix is now in the source tree at https://github.com/CoinWhisperer/EBT

We will have new wallets available within 12 hours.

Can you please contact poloniex about this, they think it is and they are freezing all EBT withdraws.

Yes, we've contacted poloniex and we have ensured they are on the right chain. The new source has very recent checkpoints. New clients will be available shortly. Some developers were asleep but now are available to help release clients.

[EBT]

Critical Bugfix Update: Version 4.0.3

A bug in the previous release impeded clients from successfully minting blocks after coins reached a certain age, slowing the block chain.

Release 4.0.3 addresses this problem and lowers the work required for a wallet to mint a block. Please update to version 4.0.3, linked below.

Also, the previous version flooded the log files. We have made some adjustments to reduce the flooding and save system resources.

We apologize for these bugs.


Source: https://github.com/CoinWhisperer/EBT

Windows Binaries:
Auto Install: https://drive.google.com/file/d/0BwGL9FkcBurEdnFHeHduMDZIcXc/edit?usp=sharing
Virus Total http://tinyurl.com/o495otj (0/53)

Manual Install: https://drive.google.com/file/d/0BwGL9FkcBurEdmlHU0QxaUwtbjQ/edit?usp=sharing
Virus Total http://tinyurl.com/pfyx94s (0/54)


OSX Wallet:
Disk Image: https://drive.google.com/file/d/0B8rWObF4xz1YcVYyc0V5bm5zeXc/edit?usp=sharing
Virus Total http://tinyurl.com/k2x292f (0/46)

[DannyTom]

Thank you!

[peggy2jj]

My updated wallet got stuck on block 392042 for 8 plus hours.

[endlessskill]

My updated wallet got stuck on block 392042 for 8 plus hours.

My updated wallet working great!

[xminer2014]

Great wallet update.

Poloniex still hasn't thaw the withdraws, gagapool has almost 2 days of backlog, as soon as poloniex thaw those withdraws, miners will get paid.

[garmin]

My updated wallet got stuck on block 392042 for 8 plus hours.

Same problem here. Deleted everything and restarted stuck in the same place on re-sync. Walletrepair is no help either.

[EBT]

My updated wallet got stuck on block 392042 for 8 plus hours.

Same problem here. Deleted everything and restarted stuck in the same place on re-sync. Walletrepair is no help either.

Please try to delete your blockchain and peers.dat file and put the following nodes (and only these nodes) in your EBT.conf file:

Code:

addnode=68.35.89.205
addnod=212.50.27.20
addnode=121.45.41.218
addnode=178.195.158.188

If you notice the block count where you are sticking, that is a cluster of nodes that continued on the PoW chain after PoW was stopped. Using the above node list should help you get past that cluster. They are all stuck because they have not updated their clients.

On a related note, poloniex is updating their chain. They claim that it is taking a long time. We re-synced the block explorer yesterday very quickly, so we don't know why poloniex is taking a while. Word from them says that the chain is almost fully synced and withdraws will be resumed shortly.

We will work on an EBT.conf setting to help speed synchronization by optionally restricting to nodes with recent updates.