[ANN] MemoryCoin | CPU Coin | Paid Dev Team | Limited Supply [MMC]

[ManeBjorn]

I know not ideal if you want offline cold storage but so far they have been good.
https://mmc-wallet.com/

I love this coin but can we please please please have a Mac osx wallet plllllzzzzzzzzz

[1713260534]

1713260534

[1713260534]

1713260534

[1713260534]

1713260534

[Shuxy]

I did a quick writeup of how I've been mining MemoryCoin with some free credits/trial from different cloud providers here: https://bitcointalk.org/index.php?topic=445491.0. Do take a look ! I generate on average 12 MMC a day with this setup, not much but it's almost free

[itsik78]

I love this coin but can we please please please have a Mac osx wallet plllllzzzzzzzzz

Hey, try this:
https://bitsharestalk.org/index.php?topic=2722.0
(It's from our CTO team)

Enjoy

[3ds]

Still no hashes of the client avaiable?

I have downloaded 'memorycoin.zip' and get this hashes:

sha256: 73b5fff921c75f781d3b7d191ae6cda1d986e99ff5a7ab5de95caaa4ae0700b1
sha1: 628070f9c5d36827d73f21b062c802674a9edcdb
md5: 3dd4048ad05e0f5406d5886eb6836377

scan results:
https://www.virustotal.com/en/file/73b5fff921c75f781d3b7d191ae6cda1d986e99ff5a7ab5de95caaa4ae0700b1/analysis/
http://virusscan.jotti.org/en/scanresult/4b7ad76e7e9b7b26ceb011d5c29154ae899e5c6c

Virustotal hits:

Symantec    WS.Reputation.1    20140129
TrendMicro-HouseCall    TROJ_GEN.F47V0111    20140129

Why does the developer not make this info public???

[bittick]

Hey guys,

MMC is really low on votes on our Poll.
Does the community not want it to be listed?

[ManeBjorn]

Hi,
What is the poll link again please?
Thanks

Hey guys,

MMC is really low on votes on our Poll.
Does the community not want it to be listed?

[itsik78]

Here's a great 24 hours comparison done by ReviewOutlaw for ALL CPU COINS.
http://www.reviewoutlaw.com/most-profitable-cpu-coin-list-alt-coin-profits-24-hours-mining/

Guess who the winner is?
MemoryCoin of course!

Here's another thread explaining how to CPU mine MMC efficiently:
https://bitcointalk.org/index.php?topic=439874

[ManeBjorn]

Nice!

Here's a great 24 hours comparison done by ReviewOutlaw for ALL CPU COINS.
http://www.reviewoutlaw.com/most-profitable-cpu-coin-list-alt-coin-profits-24-hours-mining/

Guess who the winner is?
MemoryCoin of course!

Here's another thread explaining how to CPU mine MMC efficiently:
https://bitcointalk.org/index.php?topic=439874

[Shuxy]

Although my HPM has gone up to about 22, my shares and payout are actually decreasing, seems like we are getting a bit of miners now . Go MMC!

[linolis]

Although my HPM has gone up to about 22, my shares and payout are actually decreasing, seems like we are getting a bit of miners now . Go MMC!

Yeah, almost double the network hashrate over the past two days. Great things are in store for Memorycoin!

[ManeBjorn]

That definitely works.
The more the better.
It's a great coin.

Although my HPM has gone up to about 22, my shares and payout are actually decreasing, seems like we are getting a bit of miners now . Go MMC!

Yeah, almost double the network hashrate over the past two days. Great things are in store for Memorycoin!

[cudido]

Diffuculty UP and price UP.


MMCoin to the moon!!!!!!!!!!! 

[Fiku]

Wrong thead

[tromp]

The Proof of Work is a modified Momentum based algorithm. It has a small SHA512 component, and a large AES component - chips with AES-NI instruction sets will fare *much* better. Each hash requires 1GB of Memory to perform and encrypts 50GB of data. By contrast, the verification only requires 128K and less than one 10th of a second.

Here's how Cuckoo Cycle at 2^{28} nodes compares:

It has the tiniest possible SHA256 component (one call), and a moderate siphash-2-4 component.
Each instance requires 1GB of memory to perform and hashes 1GB of data.
By contrast, the verification only requires 1/3 KB and takes less than one 10th of  a *micro* second.

Each instance has about a 5% probability of having a solution at the default setting.

Memory access in Cuckoo is maximally random, so it's constrained by memory latency
rather than bandwidth, and caches are irrelevant. The amount of computation is minimized
relative to memory access. See https://github.com/tromp/cuckoo for a paper and implementation.

[ManeBjorn]

So how do I we use this to mine MMC?
It looks very interesting. 

The Proof of Work is a modified Momentum based algorithm. It has a small SHA512 component, and a large AES component - chips with AES-NI instruction sets will fare *much* better. Each hash requires 1GB of Memory to perform and encrypts 50GB of data. By contrast, the verification only requires 128K and less than one 10th of a second.

Here's how Cuckoo Cycle at 2^{28} nodes compares:

It has the tiniest possible SHA256 component (one call), and a moderate siphash-2-4 component.
Each instance requires 1GB of memory to perform and hashes 1GB of data.
By contrast, the verification only requires 1/3 KB and takes less than one 10th of  a *micro* second.

Each instance has about a 5% probability of having a solution at the default setting.

Memory access in Cuckoo is maximally random, so it's constrained by memory latency
rather than bandwidth, and caches are irrelevant. The amount of computation is minimized
relative to memory access. See https://github.com/tromp/cuckoo for a paper and implementation.

[primer-]

What is the best cpu miner for this coin ? Is it gpu mineable ? If so, by a factor of how much is gpu mining faster ?

[ManeBjorn]

I use mc2miner 0.1e version.
https://bitsharestalk.org/index.php?topic=2042.0

It gets about 20% out of my CPU and seems to stay steady where as the others were not quite as quick or had larger swings in output.
The miner integrated with the wallet though is nice and the last couple releases has improved it alot.  I have not used it recently though.
They also support GPU mining as well.

What is the best cpu miner for this coin ? Is it gpu mineable ? If so, by a factor of how much is gpu mining faster ?

[tromp]

So how do I we use this to mine MMC?
It looks very interesting. 

The Proof of Work is a modified Momentum based algorithm. It has a small SHA512 component, and a large AES component - chips with AES-NI instruction sets will fare *much* better. Each hash requires 1GB of Memory to perform and encrypts 50GB of data. By contrast, the verification only requires 128K and less than one 10th of a second.

Here's how Cuckoo Cycle at 2^{28} nodes compares:

It has the tiniest possible SHA256 component (one call), and a moderate siphash-2-4 component.
Each instance requires 1GB of memory to perform and hashes 1GB of data.
By contrast, the verification only requires 1/3 KB and takes less than one 10th of  a *micro* second.

Each instance has about a 5% probability of having a solution at the default setting.

Memory access in Cuckoo is maximally random, so it's constrained by memory latency
rather than bandwidth, and caches are irrelevant. The amount of computation is minimized
relative to memory access. See https://github.com/tromp/cuckoo for a paper and implementation.

I just design the PoW. It's up to other people to launch new coins that use it:-)

They should go with a relatively long block interval though (10min), so they can increase the
memory requirement to 4GB or more (where running a single instance takes over a minute).

I'm also a proponent of fixed rewards, since the rate of lost coins is a probably a few percent,
so even a fixed reward coin can't remain inflationary for long.

[sunfree]

Finally see publicized！

[ManeBjorn]

Where??

Finally see publicized！