Joshwaa
|
 |
January 01, 2014, 01:07:31 AM |
|
I am having trouble getting other computers to mine on the same wallet. What needs to be in the primecoin.conf in order for it to work? Also what would be the best miner to use on i7-2700k and i7-3770k cpus?
|
Like what I said : 1JosHWaA2GywdZo9pmGLNJ5XSt8j7nzNiF Don't like what I said : 1FuckU1u89U9nBKQu4rCHz16uF4RhpSTV
|
|
|
|
|
|
|
|
"Governments are good at cutting off the heads of a centrally
controlled
networks like Napster, but pure P2P networks like Gnutella and Tor seem
to be holding their own." -- Satoshi
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
Exocyst
Sr. Member
  
Offline
Activity: 266
Merit: 250
Science!
|
 |
January 01, 2014, 02:14:15 AM |
|
Here's my fix for the issue with shared wallets I discovered earlier: https://github.com/mikaelh2/primecoin/commit/a1c3f5854e9970d2f9f13ff75601dc7c87bf83c3Basically this should help people who are running lots of miners using the same shared wallet. My fix is to initialize the extra nonce value using the current value of a nanosecond-precision clock. That should give a unique value on every machine. Boost.Chrono is now required for compiling and I have updated the makefiles to reflect that. Thanks!! Someone please compile x86 and x64 builds. Edit: unable to compile on centos 6.4 x64 : ain.cpp: In function ‘void BitcoinMiner(CWallet*)’: main.cpp:4578: error: ‘boost::chrono’ has not been declared main.cpp:4578: error: expected ‘;’ before ‘time_now’ main.cpp:4579: error: ‘boost::chrono’ has not been declared boost_1_55_0 compiled successfully. You can get it to compile on CentOS but it's a bit more tricky than before. You need to have a newer version of boost installed. Then you need to tell the compiler where you installed the newer boost. By default it goes into /usr/local. Then you need to modify the makefile like this: cp makefile.unix makefile.my sed -i -e 's/$(OPENSSL_INCLUDE_PATH))/$(OPENSSL_INCLUDE_PATH) \/usr\/local\/include)/' makefile.my sed -i -e 's/$(OPENSSL_LIB_PATH))/$(OPENSSL_LIB_PATH) \/usr\/local\/lib)/' makefile.my sed -i -e 's/$(LDHARDENING) $(LDFLAGS)/$(LDHARDENING) -Wl,-rpath,\/usr\/local\/lib $(LDFLAGS)/' makefile.my And then you type 'make -f makefile.my' to compile. Official binaries will be coming soon. I want to see if I can downgrade my glibc version first somehow. If I can get the glibc version down to 2.12, the binaries should work on CentOS. I would like to confirm that the above instructions fix an identical compilation issue on Ubuntu 13.04
|
|
|
|
CarPro
Newbie
Offline
Activity: 15
Merit: 0
|
 |
January 03, 2014, 06:58:03 AM |
|
how much money can we make off primecoin?
|
|
|
|
manawenuz
Member

Offline
Activity: 76
Merit: 10
|
 |
January 03, 2014, 06:28:32 PM |
|
Has anyone compiled the latest git version for windows 64 ?
|
|
|
|
ReCat
|
 |
January 03, 2014, 09:31:55 PM |
|
If anyone can compile and run this on windows i'll rip one of my ears out.
|
BTC: 1recatirpHBjR9sxgabB3RDtM6TgntYUW Hold onto what you love with all your might, Because you can never know when - Oh. What you love is now gone.
|
|
|
bearmeat
Newbie
Offline
Activity: 15
Merit: 0
|
 |
January 03, 2014, 09:40:16 PM Last edit: January 03, 2014, 09:59:25 PM by bearmeat |
|
So I compiled this on ubuntu 13.10 and I seem to get a segmentation error/can't connect to server as at approaches or reaches difficulty 10 (when downloading the block). Is anyone else seeing this? I have another server running the non updated version for multi-wallet.
error: couldn't connect to server [1]+ Segmentation fault (core dumped) ./primecoind
This is in the debug.log ERROR: mempool transaction missing input
EDIT: I was able to start it up for a very shot period of time before it failed again but I noticed this occurs somewhere between 279042 - 279060 blocks. I figured it was too much of a coincidence if two separate PCs experienced this at the same time.
|
|
|
|
teknohog
|
 |
January 03, 2014, 10:39:50 PM |
|
how much money can we make off primecoin?
If you really want to strike gold with primes, try mersenne.org, they give you a few thousand bucks for each new Mersenne prime 
|
|
|
|
Trillium
|
 |
January 04, 2014, 03:45:08 AM |
|
how much money can we make off primecoin?
If you really want to strike gold with primes, try mersenne.org, they give you a few thousand bucks for each new Mersenne prime  If you don't have any computers with half decent CPUs, then you are out of luck. If you have a bunch of computers around with at least core2duo era CPU then you may be able to make a small profit or attain break even against electricity costs. With my systems at home, in Australia with $0.30/kWh and a bunch of core2/i5/i7 CPUs I was able to only just reach break even against my entire electricity bill (including hot water etc). ie. mining on average $7 to $8 per day and paying that much per day in electricity. However, this was BEFORE diff=10, so it's probably a lot different now. If you have no electricity costs then you might be able to scrape together a few $/day. Then it purely becomes "how much hardware do you have" and "how cheaply can you attain new hardware". You probably cannot sustain profitable VPS mining if you had to ask this question. Only consider VPS mining if you run the figures in great detail before you purchase anything. A lot of VPS miners ran at a loss even during the earlier days of primecoin mining, I suspect not too many do it these days now we are past diff 10. The market bolstering caused by BTC-e adding XPM to their site, probably helps a lot if anyone still does VPS mining. I suppose some early VPS miners may have held all their mined XPM and now that the XPM market and BTC price have exploded then they may have done quite well for themselves, but this is a gamble I'd say most people are unlikely to make lightly. If you want to mine with large profit margins (larger than mining BTC or other SHA-256 altcoins with ASIC) then you should look at scrypt coins "shitcoin flavour of the day" which according to my own (personal situation re electricity) calculations can have margins of 3:1 or 4:1 vs electricity costs and reach "ROI" within 60-90 days. To the best of my knowledge no one mining CPU coins (XPM/PTS/Quark-based) or SHA-256 (inc BTC) can claim such high margins. The biggest downside to scrypt coins seems to be that if you aim to make absolutely maximum return then you need to devote a (un?)reasonable amount of time each day to monitoring the best coin to mine / preparing to mine newly released coins etc... This is only becoming more true as new coins (and even old ones) are adjusting to negate the effects of profit-switching pools, which means that you can no longer even take that lazy option.
|
BTC:1AaaAAAAaAAE2L1PXM1x9VDNqvcrfa9He6
|
|
|
SStalin
|
 |
January 04, 2014, 08:03:36 AM |
|
Who can explain as complexity grows, in how many complexity 10.5 is more than complexity 10?
|
|
|
|
|
mikaelh (OP)
|
 |
January 04, 2014, 10:37:58 AM |
|
So I compiled this on ubuntu 13.10 and I seem to get a segmentation error/can't connect to server as at approaches or reaches difficulty 10 (when downloading the block). Is anyone else seeing this? I have another server running the non updated version for multi-wallet.
error: couldn't connect to server [1]+ Segmentation fault (core dumped) ./primecoind
This is in the debug.log ERROR: mempool transaction missing input
EDIT: I was able to start it up for a very shot period of time before it failed again but I noticed this occurs somewhere between 279042 - 279060 blocks. I figured it was too much of a coincidence if two separate PCs experienced this at the same time.
I haven't seen this issue before but similar issues have happened with Bitcoin before. They seems to be related to the wallet mining code, so try starting the wallet without the miner.
|
|
|
|
mikaelh (OP)
|
 |
January 04, 2014, 11:40:18 AM |
|
Has anyone compiled the latest git version for windows 64 ?
I have (obviously) but I'm not quite ready to make a release yet. I've been working on some other improvements that I want to get done before I make a release. I pushed a whole bunch of commits to github if someone wants to have a look.
|
|
|
|
primer-
Legendary
Offline
Activity: 1092
Merit: 1000
|
 |
January 04, 2014, 12:23:02 PM Last edit: January 04, 2014, 12:45:20 PM by primer- |
|
Has anyone compiled the latest git version for windows 64 ?
I have (obviously) but I'm not quite ready to make a release yet. I've been working on some other improvements that I want to get done before I make a release. I pushed a whole bunch of commits to github if someone wants to have a look. New debug.log chain statistics look great! EDIT: We are also seeing a slight increase in speed(chainsperday). Should we leave new sieve options default or is it ok to use modified options that worked well in previous version ?
|
|
|
|
madmartin
Newbie
Offline
Activity: 5
Merit: 0
|
 |
January 04, 2014, 02:24:56 PM |
|
I've been working on some other improvements that I want to get done before I make a release. I pushed a whole bunch of commits to github if someone wants to have a look.
You have been busy as a bee - looks very good and compiles without problems on my gentoo linux!
|
|
|
|
SStalin
|
 |
January 04, 2014, 07:11:51 PM |
|
d = k + (pk-r)/pk I so have understood, that d - - complexity how properly to use the formula, to define the future complexity concerning today's hardware?
|
|
|
|
primer-
Legendary
Offline
Activity: 1092
Merit: 1000
|
 |
January 04, 2014, 09:27:08 PM |
|
Has anyone compiled the latest git version for windows 64 ?
I have (obviously) but I'm not quite ready to make a release yet. I've been working on some other improvements that I want to get done before I make a release. I pushed a whole bunch of commits to github if someone wants to have a look. Make sure new official build is difficulty 11 ready, at the current rate we will be hitting 11 diff. early Feb. 
|
|
|
|
bearmeat
Newbie
Offline
Activity: 15
Merit: 0
|
 |
January 05, 2014, 02:07:23 AM |
|
So I compiled this on ubuntu 13.10 and I seem to get a segmentation error/can't connect to server as at approaches or reaches difficulty 10 (when downloading the block). Is anyone else seeing this? I have another server running the non updated version for multi-wallet.
error: couldn't connect to server [1]+ Segmentation fault (core dumped) ./primecoind
This is in the debug.log ERROR: mempool transaction missing input
EDIT: I was able to start it up for a very shot period of time before it failed again but I noticed this occurs somewhere between 279042 - 279060 blocks. I figured it was too much of a coincidence if two separate PCs experienced this at the same time.
I haven't seen this issue before but similar issues have happened with Bitcoin before. They seems to be related to the wallet mining code, so try starting the wallet without the miner. Thanks that works.
|
|
|
|
AnhBen
|
 |
January 05, 2014, 07:03:52 AM |
|
Has anyone compiled the latest git version for windows 64 ?
I have (obviously) but I'm not quite ready to make a release yet. I've been working on some other improvements that I want to get done before I make a release. I pushed a whole bunch of commits to github if someone wants to have a look. Make sure new official build is difficulty 11 ready, at the current rate we will be hitting 11 diff. early Feb.  Any scripts that can automate this on VPS?
|
|
|
|
primer-
Legendary
Offline
Activity: 1092
Merit: 1000
|
 |
January 06, 2014, 02:48:13 PM |
|
Has anyone compiled the latest git version for windows 64 ?
I have (obviously) but I'm not quite ready to make a release yet. I've been working on some other improvements that I want to get done before I make a release. I pushed a whole bunch of commits to github if someone wants to have a look. Please compile the current beta version for windows x86.
|
|
|
|
mhps
|
 |
January 06, 2014, 11:49:36 PM |
|
Has anyone compiled the latest git version for windows 64 ?
I have (obviously) but I'm not quite ready to make a release yet. I've been working on some other improvements that I want to get done before I make a release. I pushed a whole bunch of commits to github if someone wants to have a look. Please compile the current beta version for windows x86. current algorithms uses 64bit capablity to accelerate mining. x86 is so slow you mighy as well use old miners that came with x86 binaries.
|
|
|
|
|