Search content
Sort by
Showing 20 of 278 results by smscotten
So far I have just the one FPGA, but two days ago UPS brought and last night I finished setting up my Beaglebone Black to do the mining so I can shut my electricity-guzzling and noisy desktop computer down when I'm not using it.
The rest can be found here: http://splicer.com/gallery/miner
The rest can be found here: http://splicer.com/gallery/miner
I was going to make a nasty crack about how 2 satoshis to 4 satoshis is 200%, but even trading against LTC (where price is a bit more granular) SAT has climbed over 400% in the last 12 hours or so. Right on.
So what?
I won't invest in each and every shitcoin that is around to ride on a single 400% wave.
Holding that shitcoin is just plain retarded.
By "right on" I meant "congratulations." Or "Good on ya." It sure as hell wasn't meant to be investment advice.
I was going to make a nasty crack about how 2 satoshis to 4 satoshis is 200%, but even trading against LTC (where price is a bit more granular) SAT has climbed over 400% in the last 12 hours or so. Right on.
Re: The official MacMiner thread [BTC/LTC-CPU/GPU/FPGA/ASIC]
I have two feature requests:
First, it would be nice to be able to save pool information using the fancy interface you've put together. I can enter pool information, but if I enter new information, the old info gets deleted. Except of course for the built-in pools. The only way to store multiple pool data is by editing the config file.
Second, the provided config file editor leaves much to be desired. It doesn't need much, but an edit field that doesn't automatically change inch marks to smart quotes would be appreciated.
Other than that, I'm happily mining away. Thanks!
First, it would be nice to be able to save pool information using the fancy interface you've put together. I can enter pool information, but if I enter new information, the old info gets deleted. Except of course for the built-in pools. The only way to store multiple pool data is by editing the config file.
Second, the provided config file editor leaves much to be desired. It doesn't need much, but an edit field that doesn't automatically change inch marks to smart quotes would be appreciated.
Other than that, I'm happily mining away. Thanks!
Re: Merge Mining Scrypt Coins - Get 4 times your hash power! DOGE/LTC/DGC/CAT/42
They aren't claiming that DGC, DOGE, LTC, or any of the "main" coins are merged. Only HUC, ORG, PTC, and USC are claimed as merged. USC and HUC at least are designed to be merge-mined. Don't know about the others without looking.
Nevertheless, this looks very scammy.
72 hours' test (which should be enough to sort out variance even if this is running p2pool underneath) at ~50Kh/s yielded:
DGC 0.34859148 vs ~5 elsewhere
DOGE 60.78225803 vs ~650
LTC 0.00426753 vs ~0.04
42 0.00000050 vs
CAT 0.03166796 vs 1
HUC 0 vs
PTC 0.94306607 vs
ORG 0 vs
POT 0 vs
USC 0.09437904 vs
The total of all that is about 0.00013645 BTC per day total for all coins and being very generous about a guesstimate at the value of USC.
That's about 9¢ per day for 50Kh/s. Coinwarz says 50Kh/s would yield 11¢/day on Catcoin, 32¢/day for 42, 22¢/day for LTC, 27¢/day for DOGE, or 14¢/day for DGC.
Bottom line: you'll get more value out of straight-up mining Catcoin, the worst performer of the bunch.
Maybe not a scam, maybe just incompetent.
I lost about 70¢ running this test. Hopefully it will save others the time of repeating the mistake with real hashpower.
Nevertheless, this looks very scammy.
72 hours' test (which should be enough to sort out variance even if this is running p2pool underneath) at ~50Kh/s yielded:
DGC 0.34859148 vs ~5 elsewhere
DOGE 60.78225803 vs ~650
LTC 0.00426753 vs ~0.04
42 0.00000050 vs
CAT 0.03166796 vs 1
HUC 0 vs
PTC 0.94306607 vs
ORG 0 vs
POT 0 vs
USC 0.09437904 vs
The total of all that is about 0.00013645 BTC per day total for all coins and being very generous about a guesstimate at the value of USC.
That's about 9¢ per day for 50Kh/s. Coinwarz says 50Kh/s would yield 11¢/day on Catcoin, 32¢/day for 42, 22¢/day for LTC, 27¢/day for DOGE, or 14¢/day for DGC.
Bottom line: you'll get more value out of straight-up mining Catcoin, the worst performer of the bunch.
Maybe not a scam, maybe just incompetent.
I lost about 70¢ running this test. Hopefully it will save others the time of repeating the mistake with real hashpower.
Even limiting to five I have to dip in to the ones I'm mostly taking a passing interest in. Really I have a top two:
Peercoin (PPC) I still love SHA but add in PoS and I like it even more.
Digitalcoin (DGC) Developer has put a lot of effort and resources into building trading and marketplace sites. Baritus gets that it's not really a currency if no one actually buys and sells stuff with it.
Then I get into coins about which I have interest in and am watching but for whatever reasons I'm not enthused about:
Namecoin (NMC) Great proof of concept (using the blockchain for practical purposes) and I shouldn't be disappointed if they haven't done more, but as a currency? Meh.
Vertcoin (VTC) Seems to be fighting ASICs the right way. Interesting. Plus it's green.
Then we have "honorable mention" which are coin I like for some reason or another but not enough to really take seriously. I've bought or mined these because I was amused or interested, and I keep my eye on them but ultimately they are nothing special to me. Maybe they have a name or a logo that I could see people using (sorry, so many coins out there won't even be adopted because their names have unfortunate implications) or some kind of buzz going around that caught my attention. I'm listing more than one because all together they all fit into the category of "other." I'm really just too lazy to pick one.
RonPaulcoin (RPC) Yeah, it's Dogecoin with a different meme.
Smartcoin (SMC) Um. Honestly, I think it's just because I find the logo soothing.
Saturncoin (SAT) Everyone's favorite planet, right?
Securecoin (SRC) If you like Quark's technology but hate Quark, then Securecoin is for you.
Now how about the ones I'm actively disinterested in?
Peercoin (PPC) I still love SHA but add in PoS and I like it even more.
Digitalcoin (DGC) Developer has put a lot of effort and resources into building trading and marketplace sites. Baritus gets that it's not really a currency if no one actually buys and sells stuff with it.
Then I get into coins about which I have interest in and am watching but for whatever reasons I'm not enthused about:
Namecoin (NMC) Great proof of concept (using the blockchain for practical purposes) and I shouldn't be disappointed if they haven't done more, but as a currency? Meh.
Vertcoin (VTC) Seems to be fighting ASICs the right way. Interesting. Plus it's green.
Then we have "honorable mention" which are coin I like for some reason or another but not enough to really take seriously. I've bought or mined these because I was amused or interested, and I keep my eye on them but ultimately they are nothing special to me. Maybe they have a name or a logo that I could see people using (sorry, so many coins out there won't even be adopted because their names have unfortunate implications) or some kind of buzz going around that caught my attention. I'm listing more than one because all together they all fit into the category of "other." I'm really just too lazy to pick one.
RonPaulcoin (RPC) Yeah, it's Dogecoin with a different meme.
Smartcoin (SMC) Um. Honestly, I think it's just because I find the logo soothing.
Saturncoin (SAT) Everyone's favorite planet, right?
Securecoin (SRC) If you like Quark's technology but hate Quark, then Securecoin is for you.
Now how about the ones I'm actively disinterested in?
- Litecoin. Sorry, but I think adoption of a currency by people in general is important. Nobody wants their money to be less filling but tastes great. The name fails to inspire confidence.
- Feathercoin. See Litecoin.
- Terracoin. Too many forks to continue trusting. And sounds like "Terrorcoin" so, no.
- Novacoin. Used by your dentist during your root canal.
- Phoenixcoin. Really? You want to inspire confidence in your coin by invoking a mythical creature that burns itself to death periodically?
- Casinocoin. Because currency really ought to be used for only one thing in one context. Riiiight.
- Dogecoin. Yeah, we've all had our fun.
- Maxcoin. Cult of personality. Yawn.
- Devcoin. Can someone explain to me why Devcoin is somehow more "ethical" than other currencies? It's different because it is made for trading in services. Uh, yeah. You're saying it's more ethical than other currencies and unique unlike other currencies because it is a currency. Basicallly, see Casinocoin.
- Mincoin. See Feathercoin.
- Freicoin. Special contempt for Freicoin for one reason: demurrage. A little knowledge of economics is a pathetic and dangerous thing. Here's a cryptocurrency that managed to build in all the worst aspects of fiat currency. Yeah, thanks for the nifty fruitcake, it was delicious. Really, yes, I ate the whole thing.
The talk of email being insecure makes me cringe a bit. Anyone who is smart enough to use a cryptocurrency is smart enough to use encrypted email. It is a dead simple option for Cryptsy to add, and I'm sure that lack of demand is why they haven't done so yet.
https://cryptsy.freshdesk.com/support/discussions/topics/27244
If Cryptsy doesn't implement it, it will be because people didn't demand it, and we will have no one but ourselves to blame.
I don't know that and don't claim that encrypted email would have prevented this theft. I'm not sure that TFA with txt (yeah, super secure txtmsgs, riiiiiight) is a silver bullet either. If there's a keylogger on your system there may be nothing you could have done short of better spyware vigilance. But the very least next step would be to let us upload our public keys and use those keys to encrypt any communications you send to us (if we have uploaded the key of course. Optional.)
https://cryptsy.freshdesk.com/support/discussions/topics/27244
If Cryptsy doesn't implement it, it will be because people didn't demand it, and we will have no one but ourselves to blame.
I don't know that and don't claim that encrypted email would have prevented this theft. I'm not sure that TFA with txt (yeah, super secure txtmsgs, riiiiiight) is a silver bullet either. If there's a keylogger on your system there may be nothing you could have done short of better spyware vigilance. But the very least next step would be to let us upload our public keys and use those keys to encrypt any communications you send to us (if we have uploaded the key of course. Optional.)
Re: Everything working smoothly after your free update to OSX Mavericks today?
I've only updated my laptop and not my desktop in case anything is wonky. Have only hit one serious snag so far, but I don't run the QT client on my laptop; I run Multibit. And Multibit ran fine on Mountain Lion but does not run on Mavericks10/23/13 5:11:55.813 AM
Dock[453]: LSOpenFromURLSpec(file:///Applications/MultiBit.app/) failed with -10658
That looks like it could be a JDK issue but I am kinda stumped.
Dock[453]: LSOpenFromURLSpec(file:///Applications/MultiBit.app/) failed with -10658
That looks like it could be a JDK issue but I am kinda stumped.
Re: The official MacMiner thread [BTC/LTC-CPU/GPU/FPGA/ASIC]
I too have nothing in the table portion. I'm running the FPGA/ASIC miner as you say, with two BEs and a Lancelot FPGA. There is content in the upper part of the window but it doesn't seem to be changing much, and doesn't seem to correspond to anything reported by the FPGA/ASIC miner window.
Yeah, that "when" time is seven hours ago. I've stopped and started the miner (and closed the API window) since then.[/code]
Code:
Reply was 'STATUS=S,When=1378717613,Code=9,Msg=0 GPU(s) - 3 PGA(s) - 0 CPU(s),Description=bfgminer 3.2.0|PGA=0,Name=ICA,ID=0,ProcID=0,Enabled=Y,Status=Alive,MHS av=154.449,MHS 5s=26.291,Accepted=1,Rejected=0,Hardware Errors=0,Utility=11.322,Last Share Pool=0,Last Share Time=1378717610,Total MH=818.4849,Diff1 Work=1,Difficulty Accepted=1.00000000,Difficulty Rejected=0.00000000,Last Share Difficulty=1.00000000,Last Valid Work=1378717610,Device Hardware%=0.0000,Device Rejected%=0.0000|PGA=1,Name=ICA,ID=1,ProcID=0,Enabled=Y,Status=Alive,MHS av=362.681,MHS 5s=55.987,Accepted=0,Rejected=0,Hardware Errors=0,Utility=0.000,Last Share Pool=-1,Last Share Time=0,Total MH=1911.1359,Diff1 Work=0,Difficulty Accepted=0.00000000,Difficulty Rejected=0.00000000,Last Share Difficulty=0.00000000,Last Valid Work=1378717598,Device Hardware%=0.0000,Device Rejected%=0.0000|PGA=2,Name=ICA,ID=2,ProcID=0,Enabled=Y,Status=Alive,MHS av=359.704,MHS 5s=56.236,Accepted=0,Rejected=0,Hardware Errors=0,Utility=0.000,Last Share Pool=-1,Last Share Time=0,Total MH=1909.8185,Diff1 Work=0,Difficulty Accepted=0.00000000,Difficulty Rejected=0.00000000,Last Share Difficulty=0.00000000,Last Valid Work=1378717598,Device Hardware%=0.0000,Device Rejected%=0.0000|'
[STATUS] =>
(
[STATUS] => S
[When] => 1378717613
[Code] => 9
[Msg] => 0 GPU(s) - 3 PGA(s) - 0 CPU(s)
[Description] => bfgminer 3.2.0
)
[PGA0] =>
(
[PGA] => 0
[Name] => ICA
[ID] => 0
[ProcID] => 0
[Enabled] => Y
[Status] => Alive
[MHS av] => 154.449
[MHS 5s] => 26.291
[Accepted] => 1
[Rejected] => 0
[Hardware Errors] => 0
[Utility] => 11.322
[Last Share Pool] => 0
[Last Share Time] => 1378717610
[Total MH] => 818.4849
[Diff1 Work] => 1
[Difficulty Accepted] => 1.00000000
[Difficulty Rejected] => 0.00000000
[Last Share Difficulty] => 1.00000000
[Last Valid Work] => 1378717610
[Device Hardware%] => 0.0000
[Device Rejected%] => 0.0000
)
[PGA1] =>
(
[PGA] => 1
[Name] => ICA
[ID] => 1
[ProcID] => 0
[Enabled] => Y
[Status] => Alive
[MHS av] => 362.681
[MHS 5s] => 55.987
[Accepted] => 0
[Rejected] => 0
[Hardware Errors] => 0
[Utility] => 0.000
[Last Share Pool] => -1
[Last Share Time] => 0
[Total MH] => 1911.1359
[Diff1 Work] => 0
[Difficulty Accepted] => 0.00000000
[Difficulty Rejected] => 0.00000000
[Last Share Difficulty] => 0.00000000
[Last Valid Work] => 1378717598
[Device Hardware%] => 0.0000
[Device Rejected%] => 0.0000
)
[PGA2] =>
(
[PGA] => 2
[Name] => ICA
[ID] => 2
[ProcID] => 0
[Enabled] => Y
[Status] => Alive
[MHS av] => 359.704
[MHS 5s] => 56.236
[Accepted] => 0
[Rejected] => 0
[Hardware Errors] => 0
[Utility] => 0.000
[Last Share Pool] => -1
[Last Share Time] => 0
[Total MH] => 1909.8185
[Diff1 Work] => 0
[Difficulty Accepted] => 0.00000000
[Difficulty Rejected] => 0.00000000
[Last Share Difficulty] => 0.00000000
[Last Valid Work] => 1378717598
[Device Hardware%] => 0.0000
[Device Rejected%] => 0.0000
)
[STATUS] =>
(
[STATUS] => S
[When] => 1378717613
[Code] => 9
[Msg] => 0 GPU(s) - 3 PGA(s) - 0 CPU(s)
[Description] => bfgminer 3.2.0
)
[PGA0] =>
(
[PGA] => 0
[Name] => ICA
[ID] => 0
[ProcID] => 0
[Enabled] => Y
[Status] => Alive
[MHS av] => 154.449
[MHS 5s] => 26.291
[Accepted] => 1
[Rejected] => 0
[Hardware Errors] => 0
[Utility] => 11.322
[Last Share Pool] => 0
[Last Share Time] => 1378717610
[Total MH] => 818.4849
[Diff1 Work] => 1
[Difficulty Accepted] => 1.00000000
[Difficulty Rejected] => 0.00000000
[Last Share Difficulty] => 1.00000000
[Last Valid Work] => 1378717610
[Device Hardware%] => 0.0000
[Device Rejected%] => 0.0000
)
[PGA1] =>
(
[PGA] => 1
[Name] => ICA
[ID] => 1
[ProcID] => 0
[Enabled] => Y
[Status] => Alive
[MHS av] => 362.681
[MHS 5s] => 55.987
[Accepted] => 0
[Rejected] => 0
[Hardware Errors] => 0
[Utility] => 0.000
[Last Share Pool] => -1
[Last Share Time] => 0
[Total MH] => 1911.1359
[Diff1 Work] => 0
[Difficulty Accepted] => 0.00000000
[Difficulty Rejected] => 0.00000000
[Last Share Difficulty] => 0.00000000
[Last Valid Work] => 1378717598
[Device Hardware%] => 0.0000
[Device Rejected%] => 0.0000
)
[PGA2] =>
(
[PGA] => 2
[Name] => ICA
[ID] => 2
[ProcID] => 0
[Enabled] => Y
[Status] => Alive
[MHS av] => 359.704
[MHS 5s] => 56.236
[Accepted] => 0
[Rejected] => 0
[Hardware Errors] => 0
[Utility] => 0.000
[Last Share Pool] => -1
[Last Share Time] => 0
[Total MH] => 1909.8185
[Diff1 Work] => 0
[Difficulty Accepted] => 0.00000000
[Difficulty Rejected] => 0.00000000
[Last Share Difficulty] => 0.00000000
[Last Valid Work] => 1378717598
[Device Hardware%] => 0.0000
[Device Rejected%] => 0.0000
)
Yeah, that "when" time is seven hours ago. I've stopped and started the miner (and closed the API window) since then.[/code]
Re: [ANN][DGC] DigitalCoin.Co | Instant \ Stable \ Reliable | Usable for Purchases
Why difficulty just went from 0.9 to 3.3?
0.9 must have been a blip. It's been around 3-4 for the last couple weeks. There's been a lot of fluctuation lately, which is the reason for the recent mandatory client update. But from what I've seen 3.3 (admittedly not watching 24/7) has been more the rule than the exception.
Think I'm number 100!
You're #100 in the thread, but #76 was Techbytes giving an update on the payments and #1 was Baritus with the original post. So I think yours was the 98th request.
Works great. You should have your 100DGC, though I had to split it into four payments due to the transaction size limit and the fact that my DGC all comes from P2Pool mining.
Thank you!
Thank you!
Re: [ANN][DGC] DigitalCoin.Co | Instant \ Stable \ Reliable | Usable for Purchases
My guess is that the transactions are too large due to being from a lot of little p2pool mining payments. But there ought to be some way around it. Having all the DGC I've mined be unspendable is not cool.
I'll buy them how much?I appreciate the offer but I'm not sure how that helps. I'd still have to send the DGC to you somehow.
Re: [ANN][DGC] DigitalCoin.Co | Instant \ Stable \ Reliable | Usable for Purchases
Same here, except I'm only trying to send 100 DGC. And it's not prompting me for any fees.
My guess is that the transactions are too large due to being from a lot of little p2pool mining payments. But there ought to be some way around it. Having all the DGC I've mined be unspendable is not cool.
My guess is that the transactions are too large due to being from a lot of little p2pool mining payments. But there ought to be some way around it. Having all the DGC I've mined be unspendable is not cool.
Replying to myself. *sigh*
Anyway, it seems I was right about that.
For the not-faint-of-heart there is a way to clean up "dust" transactions: https://bitcointalk.org/index.php?topic=218447.20
I took the easy way out. I split it up into smaller chunks and bit the bullet with my transaction fees.
I sent four payments: 50 DGC, 20 DGC, 15 DGC and 15 DGC. Total cost: 126 DGC with fees.
It might be time for me to give up the p2pools.
Re: [ANN][DGC] DigitalCoin.Co | Instant \ Stable \ Reliable | Usable for Purchases
I've been trying to transfer 5000 DGC to Cryptsy for the past couple of days and constantly getting "Error: Transaction creation failed."
I've previously transferred multiples of 5000 DGC without issue. Any ideas?
Edit.... I'm able to transfer small amounts, however it appears the fee charged for the transaction is completely random, example 1000DGC first attempt 5.90DGC fee, clicked cancel and tried again 3.30DGC, tried again 1.80DGC, tried again 5.50 DGC - what the hell is going on - is this a joke, with shit like this going on I'm considering moving my miners back to LTC.
I've previously transferred multiples of 5000 DGC without issue. Any ideas?
Edit.... I'm able to transfer small amounts, however it appears the fee charged for the transaction is completely random, example 1000DGC first attempt 5.90DGC fee, clicked cancel and tried again 3.30DGC, tried again 1.80DGC, tried again 5.50 DGC - what the hell is going on - is this a joke, with shit like this going on I'm considering moving my miners back to LTC.
Same here, except I'm only trying to send 100 DGC. And it's not prompting me for any fees.
My guess is that the transactions are too large due to being from a lot of little p2pool mining payments. But there ought to be some way around it. Having all the DGC I've mined be unspendable is not cool.
OK, this is what I've done:
Then I had a similar error:
And yeah, my berkeleydb is version5. So I followed the instructions here:
http://bitcoin.stackexchange.com/questions/3672/trouble-compiling-bitcoind-on-osx-with-homebrew
except that I already had a homebrew recipe for berkeleydb-4 so instead of downloading the older replacement, I did:
Which put the older berkeley-db4 where Digitalcoin expected it.
This led to a trickier one:
Which also looks like a version conflict. I have boost 1.54.0 from homebrew. I tried rebuilding boost with the --with-c++11 flag, just grasping at straws thinking you might have compiled with clang which expected some special support to be built in to boost. Unfortunately that didn't do the trick.
Similar message regarding a litecoin install http://trac.macports.org/ticket/39820
Another here: https://groups.google.com/forum/#!msg/mongodb-user/9hqzGYuPcsA/PUtTCgV94uQJ which suggests finding an older version of boost. Though the final message in that thread says, "fixed via binaries" which is about as unhelpful as can be.
Fortunately there is an older version of boost in brew:
Unfortunately in order to get Digitalcoin-Qt to run I have to link the 1.49 version and unlink the 1.54 version. Hopefully that won't screw up anything else that is already running.
*sigh* in most development realms I find that having a Mac means I have versions from 2010 that are too old to work with the newest source code. With everything descended from Bitcoin I have to find 2005 versions of software. Anyway, next message:
...and this is where I hit the dead end. Any thoughts?
Code:
ln -s /usr/local/Cellar/openssl/1.0.1e /usr/local/opt/openssl
to take care of the openssl error.Then I had a similar error:
Code:
Dyld Error Message:
Library not loaded: /usr/local/opt/berkeley-db4/lib/libdb_cxx-4.8.dylib
Referenced from: /Applications/Digitalcoin-Qt.app/Contents/MacOS/Digitalcoin-Qt
Reason: image not found
Library not loaded: /usr/local/opt/berkeley-db4/lib/libdb_cxx-4.8.dylib
Referenced from: /Applications/Digitalcoin-Qt.app/Contents/MacOS/Digitalcoin-Qt
Reason: image not found
And yeah, my berkeleydb is version5. So I followed the instructions here:
http://bitcoin.stackexchange.com/questions/3672/trouble-compiling-bitcoind-on-osx-with-homebrew
except that I already had a homebrew recipe for berkeleydb-4 so instead of downloading the older replacement, I did:
Code:
brew install berkeley-db4
Which put the older berkeley-db4 where Digitalcoin expected it.
This led to a trickier one:
Code:
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Symbol not found: __ZN5boost6detail13once_epoch_cvE
Referenced from: /Applications/Digitalcoin-Qt.app/Contents/MacOS/Digitalcoin-Qt
Expected in: /usr/local/lib/libboost_thread-mt.dylib
in /Applications/Digitalcoin-Qt.app/Contents/MacOS/Digitalcoin-Qt
dyld: launch, loading dependent libraries
Dyld Error Message:
Symbol not found: __ZN5boost6detail13once_epoch_cvE
Referenced from: /Applications/Digitalcoin-Qt.app/Contents/MacOS/Digitalcoin-Qt
Expected in: /usr/local/lib/libboost_thread-mt.dylib
in /Applications/Digitalcoin-Qt.app/Contents/MacOS/Digitalcoin-Qt
Which also looks like a version conflict. I have boost 1.54.0 from homebrew. I tried rebuilding boost with the --with-c++11 flag, just grasping at straws thinking you might have compiled with clang which expected some special support to be built in to boost. Unfortunately that didn't do the trick.
Similar message regarding a litecoin install http://trac.macports.org/ticket/39820
Another here: https://groups.google.com/forum/#!msg/mongodb-user/9hqzGYuPcsA/PUtTCgV94uQJ which suggests finding an older version of boost. Though the final message in that thread says, "fixed via binaries" which is about as unhelpful as can be.
Fortunately there is an older version of boost in brew:
Code:
brew install boost149 --with-c++11
Unfortunately in order to get Digitalcoin-Qt to run I have to link the 1.49 version and unlink the 1.54 version. Hopefully that won't screw up anything else that is already running.
*sigh* in most development realms I find that having a Mac means I have versions from 2010 that are too old to work with the newest source code. With everything descended from Bitcoin I have to find 2005 versions of software. Anyway, next message:
Code:
Dyld Error Message:
Symbol not found: __ZN5boost10filesystem4path7codecvtEv
Referenced from: /Applications/Digitalcoin-Qt.app/Contents/MacOS/Digitalcoin-Qt
Expected in: /usr/local/lib/libboost_filesystem-mt.dylib
Symbol not found: __ZN5boost10filesystem4path7codecvtEv
Referenced from: /Applications/Digitalcoin-Qt.app/Contents/MacOS/Digitalcoin-Qt
Expected in: /usr/local/lib/libboost_filesystem-mt.dylib
...and this is where I hit the dead end. Any thoughts?
Thank you!
The DGC client crashed on startup for me. Looks like in all my attempts to get QT clients to compile on my machine I may have screwed up some dependencies. Hopefully I can fix this myself, but thought it best to share the report here:
Yeah, OK. I have a brew install of openssl at /usr/local/Cellar/openssl/1.0.1e/lib/ and the default OS X binary at /usr/bin/openssl. I'll start with a symlink to make it look like the Homebrew version is where the binary expects it, and let you know how that goes.
The DGC client crashed on startup for me. Looks like in all my attempts to get QT clients to compile on my machine I may have screwed up some dependencies. Hopefully I can fix this myself, but thought it best to share the report here:
Code:
Process: Digitalcoin-Qt [17813]
Path: /Applications/Digitalcoin-Qt.app/Contents/MacOS/Digitalcoin-Qt
Identifier: com.yourcompany.Digitalcoin-Qt
Version: ???
Code Type: X86-64 (Native)
Parent Process: launchd [309]
User ID: 501
Date/Time: 2013-09-07 15:05:03.323 -0700
OS Version: Mac OS X 10.8.4 (12E55)
Report Version: 10
Interval Since Last Report: 52988 sec
Crashes Since Last Report: 3
Per-App Crashes Since Last Report: 3
Anonymous UUID: FD7D3C27-6AE0-48FA-67B1-7F63C126A019
Crashed Thread: 0
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: /usr/local/opt/openssl/lib/libssl.1.0.0.dylib
Referenced from: /Applications/Digitalcoin-Qt.app/Contents/MacOS/Digitalcoin-Qt
Reason: image not found
Binary Images:
0x100daf000 - 0x1012d3fe7 +com.yourcompany.Digitalcoin-Qt (???) <57B2E2E0-1F69-3FBA-8A37-777930CF319E> /Applications/Digitalcoin-Qt.app/Contents/MacOS/Digitalcoin-Qt
0x1017fb000 - 0x101802fff +libminiupnpc.9.dylib (0) /usr/local/lib/libminiupnpc.9.dylib
0x7fff609af000 - 0x7fff609e393f dyld (210.2.3) /usr/lib/dyld
0x7fff840e5000 - 0x7fff84d12fff com.apple.AppKit (6.8 - 1187.39) <199962F0-B06B-3666-8FD5-5C90374BA16A> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x7fff870ad000 - 0x7fff8740cfff com.apple.Foundation (6.8 - 945.18) <1D7E58E6-FA3A-3CE8-AC85-B9D06B8C0AA0> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff8af28000 - 0x7fff8af28fff com.apple.ApplicationServices (45 - 45) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
Model: MacPro3,1, BootROM MP31.006C.B05, 8 processors, Quad-Core Intel Xeon, 2.8 GHz, 24 GB, SMC 1.25f4
Graphics: NVIDIA GeForce 8800 GT, NVIDIA GeForce 8800 GT, PCIe, 512 MB
Memory Module: DIMM Riser B/DIMM 1, 4 GB, DDR2 FB-DIMM, 800 MHz, 0x80CE, 0x000000463732353142363245353830304600
Memory Module: DIMM Riser B/DIMM 2, 4 GB, DDR2 FB-DIMM, 800 MHz, 0x80CE, 0x000000463732353142363245353830304600
Memory Module: DIMM Riser A/DIMM 1, 4 GB, DDR2 FB-DIMM, 800 MHz, 0x80CE, 0x000000463732353142363245353830304600
Memory Module: DIMM Riser A/DIMM 2, 4 GB, DDR2 FB-DIMM, 800 MHz, 0x80CE, 0x000000463732353142363245353830304600
Memory Module: DIMM Riser A/DIMM 3, 4 GB, DDR2 FB-DIMM, 800 MHz, 0x80CE, 0x000000463732353142363245353830304600
Memory Module: DIMM Riser A/DIMM 4, 4 GB, DDR2 FB-DIMM, 800 MHz, 0x80CE, 0x000000463732353142363245353830304600
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x88), Broadcom BCM43xx 1.0 (5.10.131.36.16)
Bluetooth: Version 4.1.4f2 12041, 2 service, 18 devices, 1 incoming serial ports
Network Service: Ethernet 1, Ethernet, en0
PCI Card: NVIDIA GeForce 8800 GT, sppci_displaycontroller, Slot-1
PCI Card: Apple RAID Card, sppci_raid, Slot-4
Parallel ATA Device: PIONEER DVD-RW DVR-112D
USB Device: USB2.0 Hub, 0x05e3 (Genesys Logic, Inc.), 0x0608, 0xfd500000 / 3
USB Device: iPod, apple_vendor_id, 0x1260, 0xfd520000 / 12
USB Device: Apple Optical USB Mouse, apple_vendor_id, 0x0304, 0xfd510000 / 7
USB Device: USB2.0 Hub, 0x05e3 (Genesys Logic, Inc.), 0x0608, 0xfd400000 / 2
USB Device: FT232R USB UART, 0x0403 (Future Technology Devices International Limited), 0x6001, 0xfd440000 / 11
USB Device: XD-0608-U, 0x056a (WACOM Co., Ltd.), 0x0042, 0xfd430000 / 5
USB Device: USB2.0 Hub Controller, 0x0409 (NEC Corporation), 0x0058, 0xfd420000 / 4
USB Device: Griffin PowerMate, 0x077d, 0x0410, 0xfd424000 / 9
USB Device: SoundSticks, 0x05fc (Harman International), 0x7849, 0xfd423000 / 8
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8206, 0x5d200000 / 2
USB Device: Block Erupter Sapphire (Black), 0x10c4 (Silicon Laboratories, Inc.), 0xea60, 0x1d100000 / 3
USB Device: Block Erupter Sapphire (Black), 0x10c4 (Silicon Laboratories, Inc.), 0xea60, 0x1d200000 / 2
USB Device: DasKeyboard, 0x04d9 (Holtek Semiconductor, Inc.), 0x1919, 0x3d100000 / 2
FireWire Device: iSight, Apple Computer, Inc., 200mbit_speed
FireWire Device: built-in_hub, 800mbit_speed
Path: /Applications/Digitalcoin-Qt.app/Contents/MacOS/Digitalcoin-Qt
Identifier: com.yourcompany.Digitalcoin-Qt
Version: ???
Code Type: X86-64 (Native)
Parent Process: launchd [309]
User ID: 501
Date/Time: 2013-09-07 15:05:03.323 -0700
OS Version: Mac OS X 10.8.4 (12E55)
Report Version: 10
Interval Since Last Report: 52988 sec
Crashes Since Last Report: 3
Per-App Crashes Since Last Report: 3
Anonymous UUID: FD7D3C27-6AE0-48FA-67B1-7F63C126A019
Crashed Thread: 0
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: /usr/local/opt/openssl/lib/libssl.1.0.0.dylib
Referenced from: /Applications/Digitalcoin-Qt.app/Contents/MacOS/Digitalcoin-Qt
Reason: image not found
Binary Images:
0x100daf000 - 0x1012d3fe7 +com.yourcompany.Digitalcoin-Qt (???) <57B2E2E0-1F69-3FBA-8A37-777930CF319E> /Applications/Digitalcoin-Qt.app/Contents/MacOS/Digitalcoin-Qt
0x1017fb000 - 0x101802fff +libminiupnpc.9.dylib (0) /usr/local/lib/libminiupnpc.9.dylib
0x7fff609af000 - 0x7fff609e393f dyld (210.2.3) /usr/lib/dyld
0x7fff840e5000 - 0x7fff84d12fff com.apple.AppKit (6.8 - 1187.39) <199962F0-B06B-3666-8FD5-5C90374BA16A> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x7fff870ad000 - 0x7fff8740cfff com.apple.Foundation (6.8 - 945.18) <1D7E58E6-FA3A-3CE8-AC85-B9D06B8C0AA0> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff8af28000 - 0x7fff8af28fff com.apple.ApplicationServices (45 - 45) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
Model: MacPro3,1, BootROM MP31.006C.B05, 8 processors, Quad-Core Intel Xeon, 2.8 GHz, 24 GB, SMC 1.25f4
Graphics: NVIDIA GeForce 8800 GT, NVIDIA GeForce 8800 GT, PCIe, 512 MB
Memory Module: DIMM Riser B/DIMM 1, 4 GB, DDR2 FB-DIMM, 800 MHz, 0x80CE, 0x000000463732353142363245353830304600
Memory Module: DIMM Riser B/DIMM 2, 4 GB, DDR2 FB-DIMM, 800 MHz, 0x80CE, 0x000000463732353142363245353830304600
Memory Module: DIMM Riser A/DIMM 1, 4 GB, DDR2 FB-DIMM, 800 MHz, 0x80CE, 0x000000463732353142363245353830304600
Memory Module: DIMM Riser A/DIMM 2, 4 GB, DDR2 FB-DIMM, 800 MHz, 0x80CE, 0x000000463732353142363245353830304600
Memory Module: DIMM Riser A/DIMM 3, 4 GB, DDR2 FB-DIMM, 800 MHz, 0x80CE, 0x000000463732353142363245353830304600
Memory Module: DIMM Riser A/DIMM 4, 4 GB, DDR2 FB-DIMM, 800 MHz, 0x80CE, 0x000000463732353142363245353830304600
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x88), Broadcom BCM43xx 1.0 (5.10.131.36.16)
Bluetooth: Version 4.1.4f2 12041, 2 service, 18 devices, 1 incoming serial ports
Network Service: Ethernet 1, Ethernet, en0
PCI Card: NVIDIA GeForce 8800 GT, sppci_displaycontroller, Slot-1
PCI Card: Apple RAID Card, sppci_raid, Slot-4
Parallel ATA Device: PIONEER DVD-RW DVR-112D
USB Device: USB2.0 Hub, 0x05e3 (Genesys Logic, Inc.), 0x0608, 0xfd500000 / 3
USB Device: iPod, apple_vendor_id, 0x1260, 0xfd520000 / 12
USB Device: Apple Optical USB Mouse, apple_vendor_id, 0x0304, 0xfd510000 / 7
USB Device: USB2.0 Hub, 0x05e3 (Genesys Logic, Inc.), 0x0608, 0xfd400000 / 2
USB Device: FT232R USB UART, 0x0403 (Future Technology Devices International Limited), 0x6001, 0xfd440000 / 11
USB Device: XD-0608-U, 0x056a (WACOM Co., Ltd.), 0x0042, 0xfd430000 / 5
USB Device: USB2.0 Hub Controller, 0x0409 (NEC Corporation), 0x0058, 0xfd420000 / 4
USB Device: Griffin PowerMate, 0x077d, 0x0410, 0xfd424000 / 9
USB Device: SoundSticks, 0x05fc (Harman International), 0x7849, 0xfd423000 / 8
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8206, 0x5d200000 / 2
USB Device: Block Erupter Sapphire (Black), 0x10c4 (Silicon Laboratories, Inc.), 0xea60, 0x1d100000 / 3
USB Device: Block Erupter Sapphire (Black), 0x10c4 (Silicon Laboratories, Inc.), 0xea60, 0x1d200000 / 2
USB Device: DasKeyboard, 0x04d9 (Holtek Semiconductor, Inc.), 0x1919, 0x3d100000 / 2
FireWire Device: iSight, Apple Computer, Inc., 200mbit_speed
FireWire Device: built-in_hub, 800mbit_speed
Yeah, OK. I have a brew install of openssl at /usr/local/Cellar/openssl/1.0.1e/lib/ and the default OS X binary at /usr/bin/openssl. I'll start with a symlink to make it look like the Homebrew version is where the binary expects it, and let you know how that goes.
Re: [DGC] digitalcoin Client Version 0.2 released | MANDATORY UPDATE | < 2 Weeks
I just put a 100 DGC bounty up for someone (probably/hopefully maxpower) to make the new binaries for OS X.
https://bitcointalk.org/index.php?topic=216672.msg3103244#msg3103244
If anyone is inclined to match/exceed that it would help keep DGC viable on the Mac platform.
https://bitcointalk.org/index.php?topic=216672.msg3103244#msg3103244
If anyone is inclined to match/exceed that it would help keep DGC viable on the Mac platform.
And FYI there is a mandatory update to Digitalcoin: https://bitcointalk.org/index.php?topic=289818.0
I'll put 100 DGC up for the updated Mac binary. It's not much, but maybe others will match it.
I'll put 100 DGC up for the updated Mac binary. It's not much, but maybe others will match it.
1850 blocks in 105 minutes? A block every 3.4 seconds if launched when the post says it did.
OK, Announcement at Cryptocointalk was 10:17pm PST. It's now roughly four hours later and we're on block 2067. 240 minutes or 14,400 seconds divided by 2067, that's roughly seven seconds per block.
The blockchain will tell the real story.