|
altcoinherald
|
 |
May 05, 2014, 08:16:12 PM |
|
Those attacks against most scrypt coins will happen every day!
If some jerk buys 9000 $ asic toy, then he/she wants to play with it... and it's so easy to f*** those scrypt clones and make some money - like take a candy from child...
The only ways to sustain your coin is move to another (safer) algo or by a powerful asic to secure network. Period. There are no other options!
Agreed. I've been monitoring multiple networks and you WOULDN'T believe what's going on. Luckily everyone is asleep at the wheel, so the deaths should be painless. |
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
gigabyted
|
|
May 05, 2014, 09:52:19 PM |
|
Those attacks against most scrypt coins will happen every day!
If some jerk buys 9000 $ asic toy, then he/she wants to play with it... and it's so easy to f*** those scrypt clones and make some money - like take a candy from child...
The only ways to sustain your coin is move to another (safer) algo or by a powerful asic to secure network. Period. There are no other options!
Agreed. I've been monitoring multiple networks and you WOULDN'T believe what's going on. Luckily everyone is asleep at the wheel, so the deaths should be painless. Curious, how are you monitoring this? |
|
|
|
|
|
qumatru
|
|
May 06, 2014, 08:05:55 AM |
|
do we have anything going for us with this coin? dev? are you handling the issues with the exchanges?
|
|
|
|
|
Trestle
Member
 Offline
Activity: 102
Merit: 10
Rockem Sockem
|
|
May 06, 2014, 08:59:39 AM |
|
Blucoiner has not responded much and the facebook and twitter accounts are basically unchanged since put up. The only two exchanges the coin is on have frozen it due to problems. My take is they are in over their head don't know how to fix the problem so they are running away as quick as possible after selling off their coins before the markets crashed. I might be wrong and I hope the Devs prove me wrong but I think you would be nuts to throw any hash power at this coin right now.
|
|
|
|
|
akk123
|
|
May 06, 2014, 09:27:48 AM |
|
Dev, i know you logged in yesterday and knew the situation (Last Active: 05-05-2014, 13:21:31). So assure the the supporters of this coin that you working on the problems to get it right.
|
|
|
|
|
|
Samai
|
|
May 06, 2014, 09:32:29 AM |
|
So, dev isn't responding, very sad...
Network hashrate is decrease. Where we can sell our coins now?
|
|
|
|
|
|
BlueCoiner (OP)
|
|
May 06, 2014, 10:08:11 AM |
|
We are updated to every post on this thread all the time and we will be responding in detail to everyone shortly. Don't lose faith, Thank you!
|
|
|
|
|
altcoinherald
|
|
May 06, 2014, 10:14:34 AM |
|
Those attacks against most scrypt coins will happen every day!
If some jerk buys 9000 $ asic toy, then he/she wants to play with it... and it's so easy to f*** those scrypt clones and make some money - like take a candy from child...
The only ways to sustain your coin is move to another (safer) algo or by a powerful asic to secure network. Period. There are no other options!
Agreed. I've been monitoring multiple networks and you WOULDN'T believe what's going on. Luckily everyone is asleep at the wheel, so the deaths should be painless. Curious, how are you monitoring this? Custom rolled tools to check network health, also multiple information sources that are doing the same. Double Spend is a big problem for exchanges for obvious reasons. Unfortunately, there are way too many blockchains out there to even find out what's happening. I urge community members of each coin to pay attention to hash rates, any spikes, and even to basic info like confirmations. If confirmations start disappearing - watch out! |
|
|
|
|
lisalee
Newbie
Offline
Activity: 53
Merit: 0
|
|
May 06, 2014, 01:23:19 PM |
|
I like blue the colour.
|
|
|
|
|
|
Samai
|
|
May 06, 2014, 03:01:43 PM |
|
All exchanges (w/o Europex) closed Bluecoin deposit and trade  |
|
|
|
|
sl0819
Newbie
Offline
Activity: 42
Merit: 0
|
|
May 06, 2014, 03:13:49 PM |
|
What happened to blue?
The market is frozen now
|
|
|
|
|
|
BlueCoiner (OP)
|
|
May 06, 2014, 08:12:09 PM |
|
We have reviewed the situation and there was indeed a fork.
This happens to alt coins when the hash rate gets too low and an attacker with enough hashing power uses his footprint on the network to double spend transactions.
There is nothing we (or ANY Altcoin) for the matter can do to prevent this from happening, other than recruiting more miners. When the POS period comes into effect (roughly 70 days from now) this will obviously no longer be an issue (of course PoS brings its own set of disadvantages).
We are communicating with all the exchangers to get BLU reinstated ASAP and are here actively and vigilantly reviewing the situation...
We appreciate all of your collective patience during this rough start-up phase.
|
|
|
|
noled
Newbie
Offline
Activity: 2
Merit: 0
|
|
May 07, 2014, 03:02:25 AM |
|
Will there be a hardfork?
|
|
|
|
|
|
kololo
|
|
May 07, 2014, 03:09:10 AM |
|
A new color-coin. Can't see any innovation.
|
|
|
|
|
|
Samai
|
|
May 07, 2014, 04:30:09 AM
Last edit: May 07, 2014, 04:50:54 AM by Samai |
|
Where i can sell my Blu coins? Who want it buy??
|
|
|
|
|
Luyis Gevia
Newbie
Offline
Activity: 20
Merit: 0
|
|
May 07, 2014, 04:51:29 AM |
|
So many color coins. with no innovation, just copy the existing code and modify the parameter and then rush launch, doomed to die soon.
|
|
|
|
|
|
KryptoKings
|
|
May 07, 2014, 01:11:44 PM |
|
Is this coin dead? I got about 40,000 I mined and needed to dump. Are we DOA yet?
|
|
|
|
|
bluemedic
Newbie
Offline
Activity: 13
Merit: 0
|
|
May 07, 2014, 03:08:40 PM |
|
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
|
|
|
|
|
luckiy
Member
Offline
Activity: 88
Merit: 10
luck
|
|
May 07, 2014, 03:21:54 PM |
|
Polo how can not be traded
|
Great TheSmurfsCoin：TZXBCrED3VzGy28V328bmXkvkd4s9hxVsC
|
|
|
bluemedic
Newbie
Offline
Activity: 13
Merit: 0
|
|
May 07, 2014, 04:36:57 PM |
|
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
|
|
|
|
|
|
