Topic: [ANN] MemoryCoin - page 15. (Read 100357 times)

If i could get it to sync that would be good for starters. 

Reluctantly I have to add my experiences - I have trouble when the program is starting, often getting 'quit in an unexpected way' messages whilst it is updating. But once it gets going it seems to be largely OK. I don't know whether it is relevant or not, but the machine I've been using from the beginning seems to be the best behaved ~ did the older versions leave something behind?

I kind of have to agree with this.
Although improvements have been made on the client, it's still far from stable.
To mine Memorycoin you have to keep an eye on your miners all the time and restart when they hang or crash.

Thanks for your input - here's my take on the different issues -


More exchanges would certainly be helpful, but its the first exchange that makes the big difference - we've got a way for the market to express its opinion on the price of MEG, even if that price is low, it's important that it is there.


If you only read the forums, you'd be convinced the client is flaky. It's not. It's very stable now, and that's come from a process of being open about the problems and encouraging people to report them. We've still got an occasional problem with hanging on blocks that's I'm looking at, but most people are not having a problem with stability now.


Also, we've got a $100 bounty for a pool now -
https://bitcointalksearch.org/topic/memorycoin-pool-100-usd-expires-soon-278782

Because we've got grants built into the blockchain, we're likely to be able to offer continuing grants for new projects - something that will keep MC going, while other coins wither through lack of dev.


Yes we could probably do with a re-launch at some point. I think the people who are most confident with MC are just accumulating at the moment.



Yes, could do with a writeup on this.

Care to elaborate?  Without anything to back it up you can't expect anyone to take you seriously.

Freetrade is a scam artist.

Coming at this from the point of view of a relative newcomer to the cryptocurrency world, while I really like this coin, it has a few things going against it right now that I'd bet are the reason it isn't seeing the adoption rate of other new coins  (just giving my opinion, hopefully it'll help).

1)  only one small-ish exchange currently carrying it.  any update on efforts to get MEG on cryptsy/mcxnow/etc.?  If we as a group help to increase awareness and demand by asking for inclusion on exchanges, it should help speed up the process.

2)  comparatively unreliable client + no pool.  I can only hope Freetrade is hunting down the instabilities, and for the pool I think we need to start a grant (I would have already if I knew how) simply to stockpile coins as a reward for someone to make a pool.  Eventually the reward should be large enough for someone to actually do it.

3)  almost no publicity, which in the face of XPM, QRK, and newly released SRC (granted just a better organized QRK), is making difficulty plummet right now.  I think a lot could be done on this front just from periodic development updates (I wouldn't even understand most of it, but guaranteed it makes your average user feel better knowing that the dev is actively working on things, not to mention the updates would be a nice bump in the forums)

4)  lack of information on voting system.  There are some decent guidelines, but for me the explanations still leave a lot to be desired (hell I don't even know if sending Satoshis is referring to sending BTC or MEG to the target address, but I'm a newbie at this stuff).  For this kind of feature to be truly highlighted and showcased, you'd need to figure out a way to incorporate it into the miner GUI for ease of use, at least the voting part (probably not the easiest thing to implement, but it'd do wonders for public adoption and encouraging voting).  There definitely needs to be a central forum where grants/proposals are listed, so people understand their options.

Again, just my opinion, and if there's any way I can help I'd be glad to.  Beer time.

I think that if you send a transaction from a wallet that is not up to date with the blockchain, it doesn't get sent and can corrupt the wallet. I think this is a general issue with all QT wallets, rather than something specific to MC . . . although if MC is getting stuck on a block, there's more chance of it happening.
For now you should be careful to ensure the block chain is up to date before sending.

To fix a problem wallet, I think you'll need to either, use a backup of the wallet. Or if you don't have one, export the private key of the main address, then start a new wallet, and import the private key into it.

FreeTrade,
I think you are not using the same code in the QT wallet than in the rpc one :
The rpc tell me that I can't send coin because of insufficient fund (because the change sent to itself in the previous transaction is not taken into account (the previous transaction didn't receive a confirmation yet )),
 whereas it work in the qt one.

Restart did not fix it. So, I've deleted everything in .memorycoin and started a new.

The download took a while, but at some time the same error has appeared again. Stuck at Block 5039.

This is a default Ubuntu x64 digital ocean droplet with nothing else besides memory coin. I guess it's broken.

Recommend a restart, or a re-index if that doesn't fix it.

There is no Bitcoin installed on the client (Ubuntu 13.04 x64), only Memorycoin.

Here is the pastebins:

http://paste.ubuntu.com/6034420/
http://paste.ubuntu.com/6034429/
http://paste.ubuntu.com/6034432/

Yes, it's a kludge, but we incurred some technical debt when we forked rather than restarted at 1566, so this file is going to be required going forward, it's just a question of finding the most elegant way of including it. Open to suggestions on that. Also the trustedhashlookup.txt file is increasingly going to be required for new client to get synced in a reasonable time, so I think we'll end up including the two files in the same way.

Also, will get the 21st Century peer node included in Github in the next update.

One of the clients I have running appears to have shutdown recently, these were the last lines in debug.log:


I would delve deeper into the code if I had time right now.

I've posted into the thread you've suggested.

Have not mined yet, because the application crashes always after 15 minutes. I think you have a memory leak in your program, that cause the crash. Look in your program code please. I couldnt mine a coin, so only wasted my time with the previous version and also with the new version. It was Windows X64.

There have not been any changes that should require an upgrade since that was built.

There are a few things that can cause that message, including crosstalk with bitcoin. Do you run bitcoin as well?

Can you do something like

memorycoind getinfo | pastebinit
memorycoind getpeerinfo | pastebinit
tail -100 ~/.memorycoin/debug.log | pastebinit


or dpaste or whatever pastebin  util you use.

Then send us the urls you pasted that to?

We will be updating the linux builds later this week, but that should not be a factor for that message.

BTW, can you please use the thread http://21stcenturymoneytalk.org/index.php/topic,23.0.html for support on our builds.  We are much less likely to miss the post and it keeps this thread uncluttered with things that are probably of interest only to those using our builds.

Haha, yeah, I agree.  The data file is awkward, especially since the code does not search the path, so you need to cd first to be in the directory with the file before you run it.   Not sure how it would work with the mac app packaging either.   I am hoping it is a temporary kludge and not a permanent fixture.

IRC was removed from bitcoin, for a number of good reasons.  Since this was forked from bitcoin, it no longer has irc for seeding either.  However we did add in dnsseed support to our builds for memorycoin.  So I am curious why you say they are failing?   They should be working. It would be nice to get some more seeds to add to it though. So a report on why it is failing would be good to fix things if needed.

only by adding funds to the A. OK

so there is no way to switch preferences between A and B?!