Very nice! Built fine under MacOS X for me, and once I copied over my Linux blockchain.bin and wallet, it runs merrily away. Much nicer than running Linux in VirtualBox, but surprised that is hashing at almost the same rate...

Wow, they should be fined and taken down as an exchange.

A list of Scamming exchanges should be made, so people know as to avoid them.

The best exchange's I've used so far have been, Cryptsy and Bitstamp.

I've heard stories of BTC-E having taken customers BTC, as well as many other exchanges getting hacked.

When will the official version be released?

Did I get it right - mining is going on despite there is an error?
What to do to get rid of the error? Who's succeed in solving the problem? I am a lit bit panic, sorry

If I reclone and recompile in linux it should fix this bug correct?

Everybody can continue mining and sending money with an updated simplewallet software.

All daemons are ok without any updates because daemons don't care about "extra" field.

Buggy merged mining network is stopped an hour ago.

So are we able to continue mining while a fix is finalized? I'm in no rush to go through the process of updating to a beta wallet if a final one is going to be released soon anyway. I still seem to be synced to the network in the daemon, it's just that obviously the wallet cannot currently receive any new transactions.

It doesn't fail in this case but there is no reason to parse it futher because there is no way to understand it. Your version of wallet that continues to parse unknown data is vulnerable to some possible attacks.

In this case the rest of transation can't be parsed by wallet. This means that wallet has to stop parsing this tx. The proper fix will be issued later after talking to Amphibian who created this tx.

Bug is fixed. Please update from git.

I'm going to ask Takotime to build binaries for Windows.

Not really. When you creates a new wallet you don't need to read all blockchain that have been before, obviously there are can't be a transactions to this address you just created. (and wallet keys file actually keeps creation timestamp inside). You only need a chain of block hashes, that can be fetched very fast(Wallet data file keeps hashes chain to be able detect and handle splits in daemon). So it can be easily implemented in mobile device. Even for bytecoin huge blockchain the hashes in new just created and synchronized wallet takes about 18MB, and it can be reduced without big effort.

I will be collecting the funds for the GUI bounty. It sounds like we have nearly enough.

The donation address is:

Code:
4BBi2mHacZKCVz83FR9YCpRxefprk3TbtixKrPUtxmUFUrYyV1oqpvNdFe9df2yFswR8QiiMvfNHAFr kXutJzEUE76fnCXx

I am only accepting XMR donations at this time. If you want to donate using something else, you will need to convert it.

If you want to be able to get a refund in the event the bounty is not paid out and the project is cancelled, you will need to post or PM your TXIDs and an MRO return address. Any funds received but not accounted for in this way will be donated to some other community cause.

I will post updates of the amounts received.

I can't mine just yet as the deamon is still syncing.

Any way to check just how far it has worked its way through the blockchain?

Cheers

<zone117x> hey I looked at it and it will require substantial refactoring of the codebase and there are many other pressing features needing to be implemented in NOMP
<zone117x> so its pretty low on the priority list.
<zone117x> those who are very eager for specific NOMP feature can place a bounty, and if I accept it then I'll drop the current features I"m working in order to get it implemented
<zone117x> I don't operate any pools myself so pool ops take my open source code, make money off of it, and very few people donate a small amount
<zone117x> so the harder to implement that a feature is, the higher the bounty to get me to implement it. otherwise I'll imeplement it on my own time
<zone117x> currently there are probably months worth of features higher priority to me than getting that type of coin supported
<zone117x> if there is substantial interest in getting that type of coin supported then those who want it should contribute to a bounty

I will be collecting the funds for the pool bounty. It sounds like we have nearly enough.

The donation address is:

Code:
466CVfQvGmELo8Bc7ypDqTcSUg8Ky4WS7EefFdf4JUvWes4GVmAsXgtKPND9WT3p2bVjyEDFvmTA69S kpvuT5wBy1T1ZwWu

I am only accepting MRO donations at this time. If you want to donate using something else, you will need to convert it.

If you want to be able to get a refund in the event the bounty is not paid out and the project is cancelled, you will need to post or PM your TXIDs and an MRO return address. Any funds received but not accounted for in this way will be donated to some other community cause.

I will post updates of the amounts received.

I have created a BTC address for pool bounty donations:


Please do not use this address for any other purpose.

I will not assume return addresses are valid. If you wish to receive a refund if the bounty is cancelled you must provide a return address to me. Any donations not accounted for in this manner will be used for some other community purpose if the pool bounty is cancelled.