Thank you very much for your pointers.

I'll be sure to follow them.

This guy's voice doesn't seem too enthusiastic. Want to give the community a try to voice over this? Post the transcript.

Quote from: FreeTrade on April 15, 2014, 04:41:14 pm

Quote from: tomorrow on April 15, 2014, 07:27:49 am

I would prefer that freetrade agree to keep maintaining the client and be part of the community. It is up to him. Invitation sent and waiting for reply......

I don't see it as a particularly pressing issue. Really quite a small attack area and MC not a big target for an attack. The client should be updated though . . . i'm interested to see if our elected officers can organize it.

If you're back in business (meaning you have time for it now), it would be great to get you reelected to the CTO or CEO role.
The only technical person in the crew is killerbyte and I assume he needs a hand

Welcome back!

Just because FT replies doesn't mean he's going to actively develop again,
You can't get your hopes up so easily like that itzik!

I copied it to C:\ and manually tried to start it inside the command prompt. As soon as I hit enter it crashes.

Interesting, would you mind PM'ing me so I can assist you privately about this matter?

It was your choice to personally invest your time and effort in a coin that had the risk of structural issues.

Now, you're just being overly aggressive towards the same community you decided to adopt.

I think you're being critical of people; despite our DAC label and people from different ethics, just one thing that you witness does not create a person's identity.

If you want to clear out everybody's coin balance, good luck trying!

Quote from: Delinquency on April 14, 2014, 05:36:19 pm

Quote from: stalemate on April 14, 2014, 10:50:20 am

I'm sure someone who is not tech-savvy will download this outdated client by looking at your reply in Bitsharestalk forum. Declare this "Nothing to worry, we handled it" statement in the official page, then. Considering the latest post in the official page goes back in February, this new statement will look weird, definitely but if you CxO guys post something, you can be sure that I will appreciate it.
Guys, show some emphaty and decide yourself. In my opinion, the wallet update is a must and should be done ASAP! even though there is nothing to worry. This is totally unprofessional approach. and if the responsible person is not capable of updating the wallet client, I must tell him/her to resign immediately.

Stale, have you realized this yet?

My attitude or my critics may be harsh and not for everyone - you might notice but I'm really not interested in these kind of excuses anymore. You wrote it just yesterday. Heartbleed bug was first discovered at the beginning of April. The wallet should be updated symbolically, at least. But who's in charge for the wallet development now, seriously? Killerbyte, FreeTrade or you? Nobody gave a proper answer to this question and I gave up this challenge today. If you guys busy with watching the markets, I respect that. Then let's shut down MemoryCoin. What's the point of having MMC on the cryptocoin universe? I have around 2700 MMC left now, would like to sell (selling those on Bittrex just to make some movement there) and leave the community. I think I made some efforts in the past and I'm happy with it. This forum is my first presence in the cryptocoin industry. I was furiously deleting my account yesterday - later I kept calm. I may get angry with any kind of words from this community from now on, therefore it's better for me to leave you in peace.

Stale, the fix for this is just a show for security. I fixed the heartbleed bug on our community forums the morning of, and 12 hours later the updates were pushed out. The Memorycoin blockchain network does not natively use SSL unless on the client with RPC SSL JSON RPC commands. RPC SSL is only an issue because even without proper authentication, the heartbleed bug can ask for other information located in the RAM (at 64K intervals).

The OpenSSL bug may be a problem for you, I understand that. Our CTO had recently resigned, and we are obviously in a very cyclical moment in the coin. Please do not make this worse.

I have asked Killerbyte to look into updating the OpenSSL version for the pre-compiled clients of the OS's but he is also linux-bound. He might have a small issue with doing this.

Stalemate, I assure you that we are very much concerned with the coin as you are; except we are actually committing our attention to the plethora of things that we feel are most appropriate at the moment.


Robonix is about 60 years old as far as I am concerned. Obviously he made his address bold to appear out of the ordinary, and he is the website owner so I can't undo that.

Quote from: Delinquency on April 14, 2014, 12:46:34 am

Quote from: stalemate on April 13, 2014, 04:36:51 pm

I don't know who's responsible with reddit but... as the first merchant accepting MemoryCoin (and no support yet), I think I have the right to criticise. Have a look at reddit page once more and please update it responsibly.

https://imageshack.com/i/jmh7rxj

Yeah I need to find out who owns it.

Pretty sure it's Freetrade

I'll just go ahead and ask him for new login details so I can pass them to our CMO.

So do it! What are you guys waiting for? Should I tell you this after a week since heartbleed is appeared?
There is a serious security bug and most of the other coins' wallets are updated but MemoryCoin is not.
You know what, R.I.P. MemoryCoin! No wonder why it's depreciated so much till this date.

The vulnerabities would be limited to json rpcssl usage on the memorycoin daemon client. Otherwise, it's not that big of a problem unless on web servers, but that has nothing to do with bitcoin.

Everyone limits their rpc allow to 127.0.0.1 so there's really no concern.

I already asked Killerbyte to check on it.