Holy Orangutangs... it's true!

   OrangeCoin is 5th on cryptsy.

smoking past hundreds of other coins and the US dollar (running 6th)

   This puppy is only a few weeks old!?!

the orange devs are super-citric and OC is a young monster
and still at this fresh-squeezed 'back in the truck' price.  Is cc the land of op or what?

OrangeCoin is a lunar launch on afterburner wheels
and don't forget.... the moon is already orange,
so no need to repaint.

fyi ppl who say it's yellow must be thinking about the sun ;/

bluemedic

i didn't mean to besmirch the current logo,
could be a little more orange and less yellow, and maybe more distinctive when viewed as a small icon
yet i actually think it's pretty good, way above average, orange could live with it forever if needed

but what i had in mind was a new monster-mofo-magic-class coin face!
as in 'omg what a great logo.... let's go buy some #%$&ing coins!!!'

maybe i'm thinking too big here, maybe OC's 'one & only actual image' is not all that important.

well i guess you could have 3 addresses for donators to hit,
but i encourage ppl to pump 1st place...  because that is the candy that could bring 'em in from out of town
which is what we are going for i think

Re: Art Contest  (OC Logo redesign)

Since name and logo are the only two parts of any coin that ppl will actually ever see,
and image is everything in cc,

i think we should spend more than 3000 OC (currently about 3 bucks) to develop the logo.
and also extend the deadline to july 1

maybe devs should post a receiving address for 1st place (screw 2nd and 3rd, ie why dilute the prize to pay losers)
and advertise the bounty as it increases.

I'll kick in 10k myself
if we can get even 50 or 100 more ppl to pony up a little, we could attract some real talent here,
i'm sure a first class logo would have a profound influence on the value of the coin.
The idea being that any money we spend here comes back 1000x over the years.

Any of you orange heads that think this makes sense should chime in here.
Are we serious about promoting this coin or is it just a $3 notion.

bluemedic

[don't let my name throw ya, i'm orange on the inside]

         NEWS FLASH!!!!!!!

I received the above PM from BlueCoiner

bluemedic

blue devs,

Can you give us a new ETA on the blue PC wallet?
Do you have the compiler yet?

If we could get these questions answered everyone would be equally well informed.

[Sometimes we have a day or two communication lag going through bluecoiner
so I thought I would put this one where you devs and blue fans can see it today.]

bluemedic

OrangeCoin OC has been going vertical all day on Bittrex, not on your excellent list though

The extra conformations are temporary and due to the problem last week with the wallet.  The new coding and mac wallet were released a few days ago, but the windows build was delayed due to a compiler access problem.  

So the PC wallet will be out any minute now, the meantime looks like a great time to just 'get the blues.'

bluemedic

BlueCoiner, Can you forward my last PM to the devs and acknowledge.

bluemedic

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
 

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