So I think the Linux crashes, database/wallet corruption issues all stem from the same cause - a memory leak.

It almost certainly occurs in the momentum.cpp code, and might be a memory leak in the opensll lib's AES routine for some platforms. I don't know yet - I'm trying to track it down.

I'm gathering information for it here -
If you're getting a crash on linux, it would be useful to know what platform you're on, what version of openssl you're using, how many threads you're running and how many cores you have.

Candidates for a memorycoin pool server

Good candatites for pool servers are the simplier ones like, pushpool https://github.com/jgarzik/pushpool adding the method that memorycoin uses could be possible.  Also p2pool https://github.com/forrestv/p2pool which is python based, should be easier to work with, since it's you know python.  I've been digging around but haven't come up with much yet.

Other things being equal, I'd prefer a pool that doesn't require users to login. I'll build a menu option into the GUI to allow users to launch pool mining right from the desktop app to help out any pools if no login is required.

How does that work. Do we have to upgrade clients?

Not yet. But you're on notice that an update will be required shortly. I'll let you know when it is available.

There's a lot of interest in the MemoryCoin community for a pool miner.

As the code is based on the latest ProtoShares code, infrastructure built for ProtoShares should be easily adaptable to run with MemoryCoin too.

So I want to invite ProtoShares pool owners to consider starting pools for MemoryCoin. Any questions you need answered please post here or PM me.

Quote from: adamino on December 15, 2013, 02:45:30 pm

What is the minimum amount of protoshares in the private key when importing to mmc 2.0?

Quote

1:10 basis - so if you have 10 ProtoShares, you'll receive 1 MemoryCoin. Fractional amounts will be awarded, but some lower limit may be enforced due to size constraints.

No lower limit was applied.

FreeTrade... will you please solve the Wallet Syncing issue as it appears to affect both PTS and MemoryCoin 2.0 both of which you built.   I suspect that the fix for MemoryCoin will also help PTS.

It seems like PTS will start syncing within 30 minutes based upon latest reports.

Block 1 is 1.5MB - filled with PTS distribution balances! I think that's causing the syncing issues with MC - a lot of new miners trying to download the blockchain at the same time from a limited number of full nodes. I'll keep an eye out for any problems that may be related to PS though.

Quote from: bytemaster on December 13, 2013, 09:04:30 am

Great work FreeTrade and thank you for helping test the concept and I am sure we will learn a lot from your experience.

Not having looked at FreeTrade's code I can only describe how I would implement it... I would simply copy my wallet.dat file from ~/.protoshares to ~/.memorycoin2 as I doubt FreeTrade has changed the wallet format.

Unfortunately this won't work - the private key internally uses a different special byte, and this seems to be stored in the wallet.

Actually I've just tested this again and my apologies, this will work.

The wallet contains a lot of extra stuff like transactions and addresses that are not valid on the network, so continuing to use the wallet may cause stability problems if it tries to propogate the invalid info, but a quick way to import your coins, this will work very nicely.

If using this method, I suggest sending the coins to a fresh MC wallet as the first transaction.

I have mixed feelings... will delegate to marketing team.

Not sure what your management structure is there on such things. My advice is that the person making the decision on whether to change the logo should not be the same person responsible for the new logo, especially not if the person has already made a new logo. This would create a conflict of interest as it may be satisfying to see a new logo of your own design on a product, even if the product would be harmed by a change. Separate those decisions please!