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

[DannyTom]

4.0.1.2 and 4.0.1.3 seemed to be working fine.  I installed 4.0.1.4 and it just hangs, puts the cpu's at 100%.  Tried rebooting and restarting, so far I haven't been able to get it to open.

Any suggestions for 4.0.1.4?

If you have a lot of mature coins, the CPU usage might be from staking coins. That will hang your computer. You wouldn't have been able to stake with 4.0.1.2 and 4.0.1.3.

If you believe that staking is not causing the sluggish behavior, please

• Stop your 4.0.1.4 client
• Dete the debug.log file in your roaming folder
• Restart your client and wait a while
• Paste the contents of your log file or PM us with a private link (google drive) if you'd like to keep the log private

It finally opened after close to an hour.  Will close it tonight after work and try again to check the open time.

[1714093174]

1714093174

[xminer2014]

Hashing now for EBT at gagapool.pw!

Status: 351 confirmations
Date: 6/12/2014 05:43
From: unknown
To: 5oXQV43Tyd8t43V2SC2XFnZ5RZtzgK82yi (own address, label: GaGa Pool)
Credit: 5163.95047 EBT
Net amount: +5163.95047 EBT
Transaction ID: f545e5c654060950c6db70e75efd33807549a23a87269c3e2b4d2a42ab1f23fa

In case anyone else wants to earn EBT from PoW mining...

Thanks for mining on gagapool, currently we are still fixing some bugs. In the coming days there will be maintanance with down time of 15min. I will announce it and make sure your miners reconnect after that.

[EBT]

4.0.1.2 and 4.0.1.3 seemed to be working fine.  I installed 4.0.1.4 and it just hangs, puts the cpu's at 100%.  Tried rebooting and restarting, so far I haven't been able to get it to open.

Any suggestions for 4.0.1.4?

If you have a lot of mature coins, the CPU usage might be from staking coins. That will hang your computer. You wouldn't have been able to stake with 4.0.1.2 and 4.0.1.3.

If you believe that staking is not causing the sluggish behavior, please

• Stop your 4.0.1.4 client
• Dete the debug.log file in your roaming folder
• Restart your client and wait a while
• Paste the contents of your log file or PM us with a private link (google drive) if you'd like to keep the log private

It finally opened after close to an hour.  Will close it tonight after work and try again to check the open time.

Notes on High CPU and Memory Usage

The high CPU usage you see when opening the wallet is most likely a result of loading and validating the block index. High CPU and memory usage is also expected when synchronizing the chain because each block must be validated by re-calculating the block hash and Merkle tree. These activities take considerable resources. Remember that this data structure was originally calculated by GPUs over the course of months.

Bear in mind that it takes 1 to 2 weeks to sync a BTC wallet from the genesis block. EBT may take 6 to 8 hours, which is very fast by comparison.

Synchronization may be faster (3-4 hours) with better connected nodes (nodes that have a dedicated IP, lots of peers, a public open port 3133, and fast internet speeds). In such cases, the CPU usage will be very high because synchronization speed is dependent largely on the computational burden of validating blocks.

For EBT, also expect high memory usage during and after synchronization. The block index is 180 MB and the block database is 166 MB. These large sizes are a consequence of the short block times (30 seconds). Short block times produce fast transactions and confirmations but the tradeoff is that they require computational resources to maintain. In return for expending these resources, EBT holders are awarded PoS interest if they keep their wallets open for minting.

We have tested the 4.0.1.4 wallets thoroughly and all resource usage has appeared normal. Several clients on both Mac and Windows have synchronized reasonably fast and with complete success. If your synchronization hangs for more than an hour, please delete your peers.dat and try the following nodes in your EBT.conf file:

Code:

addnode=192.211.62.50
addnode=114.22.28.17
addnode=95.43.216.142
addnode=68.35.89.205
addnode=50.125.168.242

If the synchronization still hangs (after the splash screen), you may have to resync the full chain.

You can also speed up synchronization by adding the following line into your EBT.conf file:

Code:

stake=0

This prevents the stake minting thread from starting. Once synchronized, you can quit the client, remove the line from EBT.conf, and restart the client. The block index will take from 2 minutes to 1 hour to load depending on your system. Expect high CPU and memory usage during this time.

[khuram8494]

 i just see not much people taking interest there Doesn't seem like a lot of people are jumping in... We'll see whether this takes off.  

[Nullu]

i just see not much people taking interest there Doesn't seem like a lot of people are jumping in... We'll see whether this takes off.  

The coin is going through changes and adapting to the market. I hold a sizeable stake in the currency. If I didn't believe EBT had potential, I would have sold it long ago.

[mashac]

Lol, I'm one of the earliest adopters(day 1) of EBT..... Never sold a single EBT, and have massive faith in the dev. EBT obviously take some time to get to it's full form.. So be patient and hold your coins...

[tx42]

Lol, I'm one of the earliest adopters(day 1) of EBT..... Never sold a single EBT, and have massive faith in the dev. EBT obviously take some time to get to it's full form.. So be patient and hold your coins...

Me too. I started hashing less than 24 hours in.

If you look at the price charts on poloniex, EBT is one of the few coins that have kept its value consistently over time. Most coins go on a steady decline, but if you take EBT prices and exclude just the initial pump at poloniex, you'll see that it has been a good buy. About the only people who would have lost money are speculators who bought at the top of the poloniex peak. We've all done that at one time or another.

EBT

The first peak after the initial pump (which should probably be considered part of the pump) was about 49 sat and the prices have been moving towards having a floor at that peak.  If price data were taken prior to the pump (from another exchange), then EBT would would look phenomenal on a price chart.

Also, look at the posts by the devs. They clearly care about this coin and keep it under constant maintenance and add constant improvements. What other coins have this kind of developer presence right here in the midst of the community? There have never been any truly forked block chains and any and all problems have been fixed very fast, if you look at the previous posts here.

And it looks like the devs have plans as well if you read the thread. Of course they won't say what the plans are.

This coin is even the payout coin for gagapool.pw. When I get my miner configured correctly for it, I'll be hashing it 24/7 for EBT.

This is definitely one to have some stake in.


[addendum]

Here are a couple of coins based on the same concept (quick PoW phase followed by pure PoS):

Mint over the same part of the life cycle (starting at the first bounce and excluding the initial pump):

MINT

Cash (Poloniex data only, starting at the first bounce from cryptsy, excluding the initial pump)

CASH

[makemebeat]

I'm earliest too. And still hold all coins.

[DannyTom]

Want to buy a yacht with your EBT?

Well it's not a yacht but...

http://miami.craigslist.org/brw/bar/4519979694.html

also accepting BTQ.

I wish there were more users of the coin.

[Nullu]

tx42 is correct. EBT has stability and consistency, and just as importantly, an active dev team who are continuing to improve the currency. I like the new changes to the coin, and I'm very interested to see what happens from here on out.

I honestly believe EBT has a great future.  The cryptocurrency market is so saturated with "the next big thing" pump and dump currency. Anything with a modicum of stability is worth holding on to.

[Jonesd]

Several resynchs and twelve hours later, again I get stuck at block 65,000.

The debug log keeps getting bigger with this:

Code:

ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 987e8646591ac9ef440b824408a0d903f68401a354d7f76e9c181a3f07447094
received block a08e86bdf61fcc69d9fac1c33385b3ffb665b57cbfc494648c3250910f75957f
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block a08e86bdf61fcc69d9fac1c33385b3ffb665b57cbfc494648c3250910f75957f
Flushed 3057 addresses to peers.dat  91ms

[EBT]

Several resynchs and twelve hours later, again I get stuck at block 65,000.

The debug log keeps getting bigger with this:

Code:

ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 987e8646591ac9ef440b824408a0d903f68401a354d7f76e9c181a3f07447094
received block a08e86bdf61fcc69d9fac1c33385b3ffb665b57cbfc494648c3250910f75957f
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block a08e86bdf61fcc69d9fac1c33385b3ffb665b57cbfc494648c3250910f75957f
Flushed 3057 addresses to peers.dat  91ms

Can you ensure that you have updated to client 4.0.1.4? These symptoms seem to indicate you have the prior version.

[username here]

I was fine with the new client, it synced up perfectly.

[cindereynolds]

Anyone else have problems getting the mac wallet to synch?

[EBT]

Anyone else have problems getting the mac wallet to synch?

The Mac wallet has been tested on three different versions of OS X. Please ensure you have downloaded version 4.0.1.4.

https://drive.google.com/file/d/0B8rWObF4xz1YZmlFYjhjMFlXenM/edit?usp=sharing

[Jonesd]

Several resynchs and twelve hours later, again I get stuck at block 65,000.

The debug log keeps getting bigger with this:

Code:

ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 987e8646591ac9ef440b824408a0d903f68401a354d7f76e9c181a3f07447094
received block a08e86bdf61fcc69d9fac1c33385b3ffb665b57cbfc494648c3250910f75957f
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block a08e86bdf61fcc69d9fac1c33385b3ffb665b57cbfc494648c3250910f75957f
Flushed 3057 addresses to peers.dat  91ms

Can you ensure that you have updated to client 4.0.1.4? These symptoms seem to indicate you have the prior version.

I do have it, but I will uninstall it and do a clean install with a backup, to see if it helps.

[Jonesd]

Several resynchs and twelve hours later, again I get stuck at block 65,000.

The debug log keeps getting bigger with this:

Code:

ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 987e8646591ac9ef440b824408a0d903f68401a354d7f76e9c181a3f07447094
received block a08e86bdf61fcc69d9fac1c33385b3ffb665b57cbfc494648c3250910f75957f
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block a08e86bdf61fcc69d9fac1c33385b3ffb665b57cbfc494648c3250910f75957f
Flushed 3057 addresses to peers.dat  91ms

Can you ensure that you have updated to client 4.0.1.4? These symptoms seem to indicate you have the prior version.

I do have it, but I will uninstall it and do a clean install with a backup, to see if it helps.

No luck, I've also done the manual install and it keeps stopping synching after a while. Now it's stuck at block 4788.

It keeps enlarging the log with

Code:

Relaying wtx a38cc544ed
received block 5798e94875e31e1f78128836ede67778437daa7a8cf5f44f6ca1b6a81b716044
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 5798e94875e31e1f78128836ede67778437daa7a8cf5f44f6ca1b6a81b716044
received block 4de97194618d42fff89acdbd4d1c15642bb6d4c199c50cfa70540651b81509c8
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 4de97194618d42fff89acdbd4d1c15642bb6d4c199c50cfa70540651b81509c8
received block 039d380765a020eec973ffc8ee7240db1c191496df3d3777982741d1c72d72f7
ERROR: CheckProofOfStake() : INFO: read txPrev failed

I would say a rogue node is messing up the blockchain. It could also be an issue with windows 8.1, but I have not had this problem before.

[Jonesd]

Several resynchs and twelve hours later, again I get stuck at block 65,000.

The debug log keeps getting bigger with this:

Code:

ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 987e8646591ac9ef440b824408a0d903f68401a354d7f76e9c181a3f07447094
received block a08e86bdf61fcc69d9fac1c33385b3ffb665b57cbfc494648c3250910f75957f
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block a08e86bdf61fcc69d9fac1c33385b3ffb665b57cbfc494648c3250910f75957f
Flushed 3057 addresses to peers.dat  91ms

Can you ensure that you have updated to client 4.0.1.4? These symptoms seem to indicate you have the prior version.

I do have it, but I will uninstall it and do a clean install with a backup, to see if it helps.

No luck, I've also done the manual install and it keeps stopping synching after a while. Now it's stuck at block 4788.

It keeps enlarging the log with

Code:

Relaying wtx a38cc544ed
received block 5798e94875e31e1f78128836ede67778437daa7a8cf5f44f6ca1b6a81b716044
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 5798e94875e31e1f78128836ede67778437daa7a8cf5f44f6ca1b6a81b716044
received block 4de97194618d42fff89acdbd4d1c15642bb6d4c199c50cfa70540651b81509c8
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 4de97194618d42fff89acdbd4d1c15642bb6d4c199c50cfa70540651b81509c8
received block 039d380765a020eec973ffc8ee7240db1c191496df3d3777982741d1c72d72f7
ERROR: CheckProofOfStake() : INFO: read txPrev failed

I would say a rogue node is messing up the blockchain. It could also be an issue with windows 8.1, but I have not had this problem before.

Run as administrator seemed to do the trick

Sorry about the inconvenience. Windows is a bastard

[xminer2014]

payments were stalled on gagapool due to DIEM fork, I just resumed it and first batch went out, one more payment today to catch up with missing payment yesterday.

[tx42]

payments were stalled on gagapool due to DIEM fork, I just resumed it and first batch went out, one more payment today to catch up with missing payment yesterday.

Does this include EBT payments? I've got my miner tuned and have been hashing it for about a day and a half, but haven't seen a payout during this time.