Topic: BlueCoin (ß) |Hybrid Cold Staking | Bluetooth | 3% Annual Rewards - page 71. (Read 192232 times)

I wouldn't be surprised if in a few days gonna be 200 - 300 

They can't, there already is a GreenCoin 

mmm 4hours and you cry?
if you choose a coin for mine, do it for midle/long time.
if tomorrow blu join yc/wc/bc, you ll cry forever. btw if blu join yc thats will be great.

another scam, im realy sorry, that i give my 4 mh about 4 hour to this scam coin(((( I will never do this more!!! CAI IS A BEST NOW!

Looks like problems with Poloniex fixed, trading enabled!
Bittrex next, I think.

so for the entier blu coins its about 1.92 btc lolll

so how it's going with this ? good start but then...

I'm interested,. PM me if you get to me first...

Tnx

1 satoshi?

Want to buy :
1.2 mil blue for  0,012 btc
P.M.

I think dev didn't have relations with us  

Want to sell my BLU coins 246,355.3680021 for 20sat each. PM me

Believe it when i see it. Sorry for being cautious but thats the way it is.

You can keep the faith, all you blueLovers out there!

There are a half dozen guys working on the blue wallet update right now,
it will be available soon (mandatory actually) for everyone.

In the mean time, any fan with the blues should be aware,
BlueCoin has some big fat protectors the market hasn't heard from yet ;]
It's a very popular color you know, ask any Babe, boy, or Angel.

bluemedic

Have a new coin and its name is blue.
bet ya five dollars it's a good coin too.
Flyyyyy Hiiiiigh  Bluuuuuuuuuuue...
Yoooou good coin yooooooooou.

Bluecoiner you say keep faith but day after day nothing is done at all. Why would these people keep faith. Solid information is the only way to save your coin. There has been some great suggestions in this thread. Also If you look in the poloniex thread they explain why your coin is failing on their site.

Wheres the linux build?

I guess I forgot [in my above post] to put in the headline that:

This 'RECEIVING ADDRESS BUG' is the CAUSE of the DUPLICATE ADDRESSES.

There were no '2x spend' attacks. No one would launch an attack hoping to scam 249 blu, less than 3 cents. These so-called attacks were for random insignificant amounts.

Any real attack would be for a least a few bucks, not a few cents. No scammer would even waste perfectly good attacks on such small amounts. This is obviously the program making 'dup adrs errors' involving random transactions of blue.

bluemedic
 

Polo how can not be traded

BUG report (and FIX) for bluecoin wallet

This notice is for the devs of BlueCoin.
-----------
BUG REPORT BLU BlueCoin wallet
-----------

While trying to create a new receiving address through the 'Receive coins' tab, [after entering password] I repeatedly get this msg from MS:

=======================
MS Visual C++ Runtime Library
The application has requested the Runtime to terminate in an unusual way.
Please contact the application support team for more information.
=======================
(If you press OK here, MS will close the wallet.)

If you ignore the MS msg and wait a while you get another msg in the bluecoin readout that says the new address failed:
=============================
EXCEPTION: St 13runtine_error
CWallet::GenerateNewKey():AddKey failed
C:\Users\pc\desk1\bluecoin-qt.exe\bluecoin-qt.exe in ThreadStakeMinter()
=============================

The interesting part is that the new address DID NOT fail.

It is in the menu and appears to be usable. The fact the program said it failed means the address was not registered as a 'taken address' by the network in the usual way. This is the source of the dup adrs. 

This wallet problem is an obvious programming error occurring in the minting processing, which should not have even begun yet. Just having ThreadStakeMinter in the program line at this point is a programing error.]

Notice in the error msg that ThreadStakeMinter is where the problem occurred, and that this minting routine is causing the problem with this wallet.
--------
BUG FIX
--------
The wallet problem is occurring because mining and minting routines are not integrating well, but the good news is, they don't have to be integrated at all, they do not in fact overlap at any time.

The fix is to neutralize all calls for minting procedures based on the block count.  In other words place a command at the top of each minting routine instructing the program line to return immediately to the call point (without taking action) if mining is not completed (i.e. the block count is less than max mining limits), which conveniently is the very moment when PoS kicks in.

This will fix the wallet, and you won't have to upgrade when PoS starts. 

Notice that minting does not begin until mining is over, this fix will avoid any integration conflict, because the program will never be attempting to do both at the same time.

It might even work to just put a 'block count check' at the beginning of ThreadStakeMinter, but it would be optimal to try and 'block count check' any routine that obviously only applies to minting. 

An alternate fix would be to remove all calls for ThreadStakeMinter (and any other minting routines) from the program.  You have over two months to work out an upgrade to minting.

(NOTE: I'm detecting the bug and getting the error messages on the Vista OS, they do not seem to occur on Win7, so you may not be able to recreate the bug and error messages with just any OS)

bluemedic

Is this coin dead? I got about 40,000 I mined and needed to dump. Are we DOA yet?

So many color coins. with no innovation, just copy the existing code and modify the parameter and then rush launch, doomed to die soon.