Topic: [ANN] MemoryCoin - page 41. (Read 100338 times)
Had this mining overnight and no blocks found
For multithreaded mining use this patch.
Code: (main.cpp)
--- /home/memorycoin/memorycoin-orig/src/main.cpp 2013-08-04 11:13:48.444077266 +0100
+++ main.cpp 2013-08-04 01:29:08.472631037 +0100
@@ -4957,5 +4957,5 @@ void GenerateBitcoins(bool fGenerate, CW
minerThreads = new boost::thread_group();
- for (int i = 0; i < 1; i++)
+ for (int i = 0; i < nThreads; i++)
minerThreads->create_thread(boost::bind(&BitcoinMiner, pwallet));
}
+++ main.cpp 2013-08-04 01:29:08.472631037 +0100
@@ -4957,5 +4957,5 @@ void GenerateBitcoins(bool fGenerate, CW
minerThreads = new boost::thread_group();
- for (int i = 0; i < 1; i++)
+ for (int i = 0; i < nThreads; i++)
minerThreads->create_thread(boost::bind(&BitcoinMiner, pwallet));
}
lol scam
he could have made it a little less obvious
this is interfering with my bitcoin client, i use linux, a compilation of your coin give me bitcoin-qt, further it then messes with my block data and the addy shown in your client is my btc addy. this coin is dead unless that is the intended effect.
strange, when I qmake/make it on mine here it builds memorycoin-qt and works off .memorycoin not .bitcoin
makefile.unix needs tweaking too build memorycoind, so here's a patch off my working copy.
For multithreaded mining use this patch.
Code: (makefile.unix)
--- /home/memorycoin/memorycoin-orig/src/makefile.unix 2013-08-04 11:13:48.445077266 +0100
+++ makefile.unix 2013-08-04 11:15:37.689087998 +0100
@@ -16,5 +16,5 @@ LINK:=$(CXX)
DEFS=-DBOOST_SPIRIT_THREADSAFE -D_FILE_OFFSET_BITS=64
-DEFS += $(addprefix -I,$(CURDIR) $(CURDIR)/obj $(BOOST_INCLUDE_PATH) $(BDB_INCLUDE_PATH) $(OPENSSL_INCLUDE_PATH))
+DEFS += $(addprefix -I,$(CURDIR) $(CURDIR)/obj $(BOOST_INCLUDE_PATH) $(BDB_INCLUDE_PATH) $(OPENSSL_INCLUDE_PATH)) -DSCRYPT_CHACHA -DSCRYPT_KECCAK512
LIBS = $(addprefix -L,$(BOOST_LIB_PATH) $(BDB_LIB_PATH) $(OPENSSL_LIB_PATH))
@@ -136,4 +136,5 @@ OBJS= \
obj/rpcrawtransaction.o \
obj/script.o \
+ obj/scrypt.o \
obj/sync.o \
obj/util.o \
@@ -148,5 +149,5 @@ OBJS= \
-all: bitcoind
+all: memorycoind
test check: test_bitcoin FORCE
@@ -167,4 +168,7 @@ leveldb/libleveldb.a:
-include obj-test/*.P
+obj/scrypt.o: scrypt-jane/scrypt-jane.c
+ gcc -c $(xCXXFLAGS) $(DEFS) -o $@ $^ -MMD -MF obj/scrypt.P
+
obj/build.h: FORCE
/bin/sh ../share/genbuild.sh obj/build.h
@@ -179,5 +183,5 @@ obj/%.o: %.cpp
rm -f $(@:%.o=%.d)
-bitcoind: $(OBJS:obj/%=obj/%)
+memorycoind: $(OBJS:obj/%=obj/%)
$(LINK) $(xCXXFLAGS) -o $@ $^ $(xLDFLAGS) $(LIBS)
@@ -195,5 +199,5 @@ test_bitcoin: $(TESTOBJS) $(filter-out o
clean:
- -rm -f bitcoind test_bitcoin
+ -rm -f memorycoind test_bitcoin
-rm -f obj/*.o
-rm -f obj-test/*.o
For multithreaded mining use this patch.
Code: (main.cpp)
--- /home/memorycoin/memorycoin-orig/src/main.cpp 2013-08-04 11:13:48.444077266 +0100
+++ main.cpp 2013-08-04 01:29:08.472631037 +0100
@@ -4957,5 +4957,5 @@ void GenerateBitcoins(bool fGenerate, CW
minerThreads = new boost::thread_group();
- for (int i = 0; i < 1; i++)
+ for (int i = 0; i < nThreads; i++)
minerThreads->create_thread(boost::bind(&BitcoinMiner, pwallet));
}
this is interfering with my bitcoin client, i use linux, a compilation of your coin give me bitcoin-qt, further it then messes with my block data and the addy shown in your client is my btc addy. this coin is dead unless that is the intended effect.
why would it get more then 6 minutes to generate a block while someone is mining?
is it only me or the network is stack on the 151 block for about 30 minutes ?
Yes it was taking a while - but just saw 2 blocks in a row. Up to 153 now.
is it only me or the network is stack on the 151 block for about 30 minutes ?
after I upgraded the exe file
no found blocks for more then 20 minutes.. is it OK?
Second, When we create a Private Key \ MVTE address, what do we do with it? I tried to import the private key, but get that it is invalid.
Okay, thanks again for the bug report - I've got a new exe that fixes the problem - remember to backup your wallet before using the new version.
https://docs.google.com/file/d/0B-5Ax5kejTpMTHZnUF80cGlFU1k/edit?usp=sharing
For those of you working with source, fix will be on github soon, in the meantime chainparams.cpp :line 235 should be change to
base58Prefixes[SECRET_KEY] = 178; //50+128
Building the deamon gives me bitcoind .
is https://github.com/memorycoin/memorycoin/commits/0.8.3.july16 the main branch? That looks like bitcoin clone with nothing else in it.
getaccountaddress "" <-- gives me address starting with 1
//Nevermind, it seems mcinit is the master not the default one... Cant seem to connect to any of the addnodes... anyone got fresh ips?
MCkYX4Pb8VkjHmPpSdMsRJXvSNCQaShibs
Here is mine
Here is mine
Is it still Beta Test Build? Is all coins generated will be '0' once it release? Any useful information welcome on this matter.
It's an experiment - there's a lot of variables and I don't know how the experiment will turn out. If the coin needs to be restarted or tweaked for whatever reason, I'll take reasonable steps to maintain balances where possible. Keep any wallets you create, they may be valid in the next blockchain if this one doesn't work out.
Is it still Beta Test Build? Is all coins generated will be '0' once it release? Any useful information welcome on this matter.
Okay the first coin blocks are maturing - I've got some coins to play around with.
Send me a priv message with your MemoryCoin address (it should be an address that has already mined a block) if you'd like some coins to try out the voting.
Send me a priv message with your MemoryCoin address (it should be an address that has already mined a block) if you'd like some coins to try out the voting.
Since gethashespersec returns 0, is there a way to verify it's mining properly? (other than watch 'memorycoind listtransactions')
What's a typical blocks/hour expected with an 8core for the current diff of 0.00001525?
the current official windows wallet is hardcoded to 1 core, you can tell its mining from the CPU useWhat's a typical blocks/hour expected with an 8core for the current diff of 0.00001525?
i got 1 block in about 3 hours at this diff on my i5 (2 if you include orphans)
Jump to: