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

[3ds]

My first request of the hash values is from December 16, 2013:

Where can i find the hashes of the client download???

I get for 'memorycoin.zip' this:

sha256: fbd1553a2babe9755c79bc33177a15fe8c92f7972f373e51ca54b9f8604de965
sha1: af10bcdfce8e80887ea29bcb6c0e77beed4f36d2
md5: 68c37aa751148bd1a78e55ca441cf02f

Why does mostly developer doesn't protect the users?

And still there is no official hash values posted. Why?

[1713604287]

1713604287

[1713604287]

1713604287

[1713604287]

1713604287

[1713604287]

1713604287

[trankil]

there is a new version of client or not for windows?

because when i download i have the 0.8.54

[truckythin]

diff is pretty high now, it take 10-15 minutes to solve a block now 

[superresistant]

will it be worth the same as PTS in near future`? anyone?

Compare the two :
ProtoShares
POW Hash: Momentum (2^26 / 2^50) with SHA512 Generation
Block target: 5 minutes
Difficulty Retargeting: 1 Week
Codebase: Bitcoin 0.8.5
No premine.
Block reward: 50 PTS, 5% reduction every week
Total coins: Around 2 million, with 1% inflation after 2 years
VS
MemoryCoin
POW Hash: Momentum (64K XOR AES-CBC x 50) with SHA512 Generation
Block target: 6 minutes
Codebase: ProtoShares 0.8.6 (Bitcoin 0.8.5)
Block reward: 280 MMC, 5% reduction every 1680 blocks
Total Coins: 10 Million coins in the first 2 years, 2% inflation thereafter
Difficulty Retargeting: Every block with the Kimoto 'Gravity Well'

I think 1 MemoryCoin will be about 6-7 USD (if you consider a price of Bitcoin of 1300USD/BTC and a ratio 0.025BTC/PTS like it was before the China crash).

[FreeTrade]

FWIW, the newest git source as of 3 hours prior to this post is working on linux with no indication whatsoever of the memory leak, but I also rewrote my self-monitoring script a bit, as I noticed purely by accident that the CPU drops near zero when votes are being tabulated (my script may have been killing and restarting the process while votes were being counted, which is probably what caused the large number of corrupt blockchain issues I was having). Not sure if my stable systems are due to new source or to something I did... but I'm quite certain it wasn't 100% me.

Thanks for this. There are some extra 'delete thread_group' statements in there that were recommended on another post, so they might be making the difference. You're right, the mining will stop while the votes are calculated, this will happen around blocks divisible by 20. It should only happen once per vote. 

[Hyko0]

I really dont know where all your problems come from =/


I started 3 days ago with the version 0.8.54 on 4 dedicated servers with Intel Xeon E5-1650 3.50GHz which gets 3.96 hpm each and I found 7 blocks so far without a single crash or get stucked on a block.

Everything wents fine here.

Balance: 1680 MMC  =)


Edit: Perhaps it runs better with more than 8 connections. My clients got more than 40 connections each. I just opend the firewall for the Port 1968.

[3ds]

I didn't know why it's so costly to build some checksum after every compiling???


I downloaded the client from both sources, now:
http://www.memorycoin.org/downloads/memorycoin.zip
https://drive.google.com/file/d/0B-5Ax5kejTpMOWZjXzE1UEs0bG8/edit?usp=sharing

Has the same checksum:
sha256: ae7969d681ce775c4cae5c2939ee223125454c51523478fde0d944f3e76bbefb
sha1: 0fb629562eb573531bdac9ed77fc5db7a430e88e
md5: 746669a259a04a61548bb57a6a81b268

It's v0.8.52.0 from 20.12.2013 - 02:32

Scan results: http://virusscan.jotti.org/en/scanresult/1210a156db9ef752be1534048bb8a0302abe5889 is clear...


Can anyone confirm?

[jeroenn13]

I didn't know why it's so costly to build some checksum after every compiling???


I downloaded the client from both sources, now:
http://www.memorycoin.org/downloads/memorycoin.zip
https://drive.google.com/file/d/0B-5Ax5kejTpMOWZjXzE1UEs0bG8/edit?usp=sharing

Has the same checksum:
sha256: ae7969d681ce775c4cae5c2939ee223125454c51523478fde0d944f3e76bbefb
sha1: 0fb629562eb573531bdac9ed77fc5db7a430e88e
md5: 746669a259a04a61548bb57a6a81b268

It's v0.8.52.0 from 20.12.2013 - 02:32

Scan results: http://virusscan.jotti.org/en/scanresult/1210a156db9ef752be1534048bb8a0302abe5889 is clear...


Can anyone confirm?

One thing. If you scan a .zip or .rar file in doesnt recognize any infections. Its recommended to scan the files in the compressed folder.

[x0rcist]

found a bug when transferring funds.

> if you split the funds when sendtoaddress it gives a zero (0) balance after the first transfer. rest funds are still there but not listed. After transferring the rest of your funds it gives a negative balance.

Code:

./memorycoind listaccounts   {
    "" : -279.00000000
}

[3ds]

Its recommended to scan the files in the compressed folder.

That should a good antivirus programm do by himself...

[jeroenn13]

Its recommended to scan the files in the compressed folder.

That should a good antivirus programm do by himself...

As you can see he is using Jotti which doesn't scan inside the compressed folders.........

[srwt]

Guys, don't you know how to hide wallet? I don't want someone see it.

[frga13]

This is a miner script for linux.

I just pushed up a new MMC block miner that uses the default daemon with customizability.

• Fast and easy installation
• Recompile from source (github)
• Easy Restarter
• Delete Block database (if it becomes corrupt)
• Get mining information without forcing a command every 2 seconds
• Read the last few lines of your debug log

[Fixed if I make new updates]

Code:

cd ~; rm mmc-beta.sh; wget https://dl.dropboxusercontent.com/u/50880632/mmc-beta.sh; chmod +x mmc-beta.sh;./mmc-beta.sh

Tips welcome @ MMt59REmPF9w9a7uBp6hHKtWKvMRvKUX1h

This worked for me on Ubuntu 12 x86_64
There is one thing though
before I run

Code:

cd ~; rm mmc-beta.sh; wget https://dl.dropboxusercontent.com/u/50880632/mmc-beta.sh; chmod +x mmc-beta.sh;./mmc-beta.sh

I run

Code:

apt-get update

donations will be sent if when I mine block 

[reorder]

Current git coredumps on me on blockchain resync around block 271

Code:

(gdb) bt
#0  0x00000000004341d8 in construct (
    mainMemoryPsuedoRandomData=0x7f4eebfff010 "\022\262\021\261#\016\302/\001\236|ؿD\252\224\207\031Z\204m\347?\001\341\257\203\240\371\262u\002\275\036~ͬ\310G\372]\312\326k2\374W\351\001\307Z\215\216\332\177\353\311w8ad\200h$j\303+]\251'K\026\020\066\232K#K\230\067\017\335k\222\231\252!\370\301\324\252\223\001\215\303\343@'e\t\365\017g&\030@\330\312T3\271\240\020\247E>\004\r\333\340\341\331\376\316\344zjL\352Hڟ\231\350\017\202AP\346F\353\063\"ڗ\342\344\244J\324Tc7,\250\250\254\244|\251i\211\250[\177Xޫ\362\020\367\035&\363\234C\352!2\254\317xީX\006Z\177\r\342F\307\360j\303\031.\326˷"..., threadNumber=12, totalThreads=<value optimized out>, isComplete=0x7f4f2c00ade0 "\360\243\001,O\001", results=0x7f4f717fa830)
    at /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/ext/new_allocator.h:105
#1  push_back (
    mainMemoryPsuedoRandomData=0x7f4eebfff010 "\022\262\021\261#\016\302/\001\236|ؿD\252\224\207\031Z\204m\347?\001\341\257\203\240\371\262u\002\275\036~ͬ\310G\372]\312\326k2\374W\351\001\307Z\215\216\332\177\353\311w8ad\200h$j\303+]\251'K\026\020\066\232K#K\230\067\017\335k\222\231\252!\370\301\324\252\223\001\215\303\343@'e\t\365\017g&\030@\330\312T3\271\240\020\247E>\004\r\333\340\341\331\376\316\344zjL\352Hڟ\231\350\017\202AP\346F\353\063\"ڗ\342\344\244J\324Tc7,\250\250\254\244|\251i\211\250[\177Xޫ\362\020\367\035&\363\234C\352!2\254\317xީX\006Z\177\r\342F\307\360j\303\031.\326˷"..., threadNumber=12, totalThreads=<value optimized out>, isComplete=0x7f4f2c00ade0 "\360\243\001,O\001", results=0x7f4f717fa830)
    at /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/bits/stl_vector.h:737
#2  mc::aesSearch (
    mainMemoryPsuedoRandomData=0x7f4eebfff010 "\022\262\021\261#\016\302/\001\236|ؿD\252\224\207\031Z\204m\347?\001\341\257\203\240\371\262u\002\275\036~ͬ\310G\372]\312\326k2\374W\351\001\307Z\215\216\332\177\353\311w8ad\200h$j\303+]\251'K\026\020\066\232K#K\230\067\017\335k\222\231\252!\370\301\324\252\223\001\215\303\343@'e\t\365\017g&\030@\330\312T3\271\240\020\247E>\004\r\333\340\341\331\376\316\344zjL\352Hڟ\231\350\017\202AP\346F\353\063\"ڗ\342\344\244J\324Tc7,\250\250\254\244|\251i\211\250[\177Xޫ\362\020\367\035&\363\234C\352!2\254\317xީX\006Z\177\r\342F\307\360j\303\031.\326˷"..., threadNumber=12, totalThreads=<value optimized out>, isComplete=0x7f4f2c00ade0 "\360\243\001,O\001", results=0x7f4f717fa830) at momentum.cpp:136
#3  0x00007f4fb7b01d47 in thread_proxy () from /usr/lib64/libboost_thread-mt.so.5
#4  0x00007f4fb6b18851 in start_thread () from /lib64/libpthread.so.0
#5  0x00007f4fb60c694d in clone () from /lib64/libc.so.6

[badbonez]

If you download my beta bash script and run it, you can point the script to your .memorycoin folder, which you will have to find yourself. it seems that the daemon cannot find the memorycoin.conf folder which is located in the default .memorycoin folder on your server.

OK, ran that new script last night, but as it was starting up something happened and I was disconnected from my server.  This morning I ran

Code:

root@mmc2:/home/ubuntu/memorycoin/src# watch './bitcoind getinfo && ./bitcoind getmininginfo'

and now I see:

Code:

Every 2.0s: ./bitcoind getinfo && ./bitcoind getmin...  Fri Dec 20 13:29:52 2013

{
    "version" : 85400,
    "protocolversion" : 70001,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 1198,
    "timeoffset" : -338,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 0.00000522,
    "testnet" : false,
    "keypoololdest" : 1387521649,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "errors" : ""
}
{
    "blocks" : 1198,
    "currentblocksize" : 1000,
    "currentblocktx" : 0,
    "difficulty" : 0.00000522,
    "errors" : "",

Working now?  Does this indicate my hash rate?

Also, when I started your new script it asked me how many threads or processes to use?  I'm not sure how to answer that with a cloud server.  My cloud server is 2 VCPU 2GB RAM, 30 GB Vdisk.  Using    Ubuntu Server 13.10 (amd64 20131030) - Partner Image.

Thanks again!

[frga13]

If you download my beta bash script and run it, you can point the script to your .memorycoin folder, which you will have to find yourself. it seems that the daemon cannot find the memorycoin.conf folder which is located in the default .memorycoin folder on your server.

OK, ran that new script last night, but as it was starting up something happened and I was disconnected from my server.  This morning I ran

Code:

root@mmc2:/home/ubuntu/memorycoin/src# watch './bitcoind getinfo && ./bitcoind getmininginfo'

and now I see:

Code:

Every 2.0s: ./bitcoind getinfo && ./bitcoind getmin...  Fri Dec 20 13:29:52 2013

{
    "version" : 85400,
    "protocolversion" : 70001,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 1198,
    "timeoffset" : -338,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 0.00000522,
    "testnet" : false,
    "keypoololdest" : 1387521649,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "errors" : ""
}
{
    "blocks" : 1198,
    "currentblocksize" : 1000,
    "currentblocktx" : 0,
    "difficulty" : 0.00000522,
    "errors" : "",

Working now?  Does this indicate my hash rate?

Also, when I started your new script it asked me how many threads or processes to use?  I'm not sure how to answer that with a cloud server.  My cloud server is 2 VCPU 2GB RAM, 30 GB Vdisk.  Using    Ubuntu Server 13.10 (amd64 20131030) - Partner Image.

Thanks again!

to see hashrate, just expand SSH window

[Delinquency]

If you download my beta bash script and run it, you can point the script to your .memorycoin folder, which you will have to find yourself. it seems that the daemon cannot find the memorycoin.conf folder which is located in the default .memorycoin folder on your server.

OK, ran that new script last night, but as it was starting up something happened and I was disconnected from my server.  This morning I ran

Code:

root@mmc2:/home/ubuntu/memorycoin/src# watch './bitcoind getinfo && ./bitcoind getmininginfo'

and now I see:

Code:

Every 2.0s: ./bitcoind getinfo && ./bitcoind getmin...  Fri Dec 20 13:29:52 2013

{
    "version" : 85400,
    "protocolversion" : 70001,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 1198,
    "timeoffset" : -338,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 0.00000522,
    "testnet" : false,
    "keypoololdest" : 1387521649,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "errors" : ""
}
{
    "blocks" : 1198,
    "currentblocksize" : 1000,
    "currentblocktx" : 0,
    "difficulty" : 0.00000522,
    "errors" : "",

Working now?  Does this indicate my hash rate?

Also, when I started your new script it asked me how many threads or processes to use?  I'm not sure how to answer that with a cloud server.  My cloud server is 2 VCPU 2GB RAM, 30 GB Vdisk.  Using    Ubuntu Server 13.10 (amd64 20131030) - Partner Image.

Thanks again!

to see hashrate, just expand SSH window

I recommend two threads for two CPU cores on your cloud server.

I will be implementing the installation as a one time only setup so that you can spend less time rebuilding the blocks and compiling after a disconnect.

[badbonez]

If you download my beta bash script and run it, you can point the script to your .memorycoin folder, which you will have to find yourself. it seems that the daemon cannot find the memorycoin.conf folder which is located in the default .memorycoin folder on your server.

OK, ran that new script last night, but as it was starting up something happened and I was disconnected from my server.  This morning I ran

Code:

root@mmc2:/home/ubuntu/memorycoin/src# watch './bitcoind getinfo && ./bitcoind getmininginfo'

and now I see:

Code:

Every 2.0s: ./bitcoind getinfo && ./bitcoind getmin...  Fri Dec 20 13:29:52 2013

{
    "version" : 85400,
    "protocolversion" : 70001,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 1198,
    "timeoffset" : -338,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 0.00000522,
    "testnet" : false,
    "keypoololdest" : 1387521649,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "errors" : ""
}
{
    "blocks" : 1198,
    "currentblocksize" : 1000,
    "currentblocktx" : 0,
    "difficulty" : 0.00000522,
    "errors" : "",

Working now?  Does this indicate my hash rate?

Also, when I started your new script it asked me how many threads or processes to use?  I'm not sure how to answer that with a cloud server.  My cloud server is 2 VCPU 2GB RAM, 30 GB Vdisk.  Using    Ubuntu Server 13.10 (amd64 20131030) - Partner Image.

Thanks again!

to see hashrate, just expand SSH window

Lol...I am such a newb.  Thanks!  (Says no information yet...)

[trankil]

Considering I mine at 0.4 kh I gave up on solo mining since its impossible.
When will poor people will be able to get some coins? when are the pools coming??

How about I give you tons of VPS mining power? This should keep you going until pool is ready https://bitsharestalk.org/index.php?topic=887.0

I've used most of these trials and they work great! They will ask you for your credit card number and most of them will call the phone number you provided to verify that you are a real person, but this is so much mining power!!

could you tell me witch offer you choose (system, core etc)

[FreeTrade]

I really dont know where all your problems come from =/


I started 3 days ago with the version 0.8.54 on 4 dedicated servers with Intel Xeon E5-1650 3.50GHz which gets 3.96 hpm each and I found 7 blocks so far without a single crash or get stucked on a block.

Everything wents fine here.

Balance: 1680 MMC  =)


Edit: Perhaps it runs better with more than 8 connections. My clients got more than 40 connections each. I just opend the firewall for the Port 1968.

I'm glad to hear it's working well for you. The problems seemed to be highly dependent on the operating system used. Anyway, I think we've got a lot of the issues addressed now and expecting smoother sailing from here on.