|
Far cleaner looking setup in the vertical configuration. The hood for evacuating the heat is a good idea, too.
|
|
|
|
just to clear things..
stealing blocks when renting rigs is not possible.
but blocking minergear to submit high shares to pool is possible,
or blocking rentalsite submitting high share from miner to pool is possible.
this will only gain waste of energy and leaving the possible blocks to other miners.
correct me if im wrong.
Yes you can't steal a block, but that is not what we've mentioned in any of this or at my link. You can't leave a block to someone else. You can simply stop a block by not submitting it and no pool can identify that you didn't submit it. If you are mining at 1,000 difficulty, a 1,000 difficulty share is worth the same as a 10,000,000,000 difficulty share, so stopping high shares is pretty much irrelevant. talking about the same thing. possible but irrelevant and stupid if done. only way to measure possible blocking attacks is to compare your bestshare at long period, or pools expected shares when block is found, (ck solo has no expected shares stats and shares does not matter..). and suchs attacks are really hard to identify, too many variables and the so much missed/called: "can vary greatly depending on your luck.." Exactly, probably impossible to identify. And since all PPS pools (and others to some extent) are voulnerable to this type of attack (and PPS pools being here for several years) - the big question is, why this question was 'opened' by kano regarding rentals? To me, it looks like an attempt to discredit certain rental sites. All rental sites together have less than 10 PHs, but major PPS pools have more than 50 PHs. If anyone should be worried about this are large PPS pools rather than rentals, because these pools have the most to loose in events of such attacks. Kano didn't open any question. I raised this very same point months ago. It is not a dig against any rental site in particular but rather is a risk people take when renting gear. When I rent I take the chance that the person who owns the gear is not acting maliciously. The gear owner could be doing exactly what is described: running hardware/software that either by design or by accident is withholding block solutions. There is absolutely no risk to the gear owner since he is getting paid by the rental site as long as he is providing shares. There is nothing you as the rental site owner can do to validate whether or not this is taking place. Let's say that I write some code to the effect of "do not submit any shares that are of 40B or greater". How would you know that I'm withholding that? To you I'm still hashing away and regularly submitting shares. You think all is good and pay me. The renter is still getting the hash rate he paid for. |
|
|
|
The difference is in the density of the installation. Bitcoin miners can or usually are burning more watts per square foot of space for obvious reasons. A building that is consuming 1,000,000 watts will have to dissipate 1,000,000 watts worth of heat. You will find you can pack 1,000,000 watts of miners into a much smaller space than you could with enterprise level server equipment, making it seem like it makes more heat. But the amount of heat they will generate compared to each other power usage being equal will be identical due to the first law of thermodynamics. You can't get more energy (in this case heat) out of a something that is using the same amount of energy for work. Energy cannot be created, only moved. What you are suggesting means we could build a perpetual motion machine with bitcoin miners.
Pretty much this. A miner is far different in power consumption than your typical enterprise class server. Yes, 1MW is 1MW as we can't get away from the first law; however, looking at rackspace and density, a cabinet full of SP3X will produce far more heat than the same cabinet full of Dell Poweredge because that cabinet of SP3X is running full tilt burning those kW at 100% of the time, whereas those Dell servers are very likely not. |
|
|
|
hum.. look at your wallet "balance" field...: dont you have a great "0.00" ? overwise i'm not english native , but what does mean "stake" field in this case ?  stake The stake means that this coin is a proof of stake coin. This means that he probably has minted coins and thus they are in the stake field. hum.. look at your wallet "balance" field...: dont you have a great "0.00" ? overwise i'm not english native , but what does mean "stake" field in this case ? stake I have 238 coins but they are stuck in stake mode  Correct me if I'm wrong, since I don't know much about proof of stake, but wouldn't the coins in the stake field mean that they were coins that you minted from your stake in the network? If so, these coins need to mature, and you need to wait some time in order to spend them. I believe that this is similar to the 100 confirmations required for Bitcoin from a coinbase transaction to be spent. You aren't wrong... that's exactly why OP can't send any coins... because they are all tied up in the stake. OP, you need to wait until those staked coins have matured (typically 101 confirmations). Then you'll be able to spend them. By the way, this entire thread belongs in the alt-coins boards... |
|
|
|
How can I import the Bitcoin Source Code easily into an Development Environment e.g. KDevelop ?
I download the source code from GitHub, unzip it, but there is no .project File or anything like that.
That's because there is no IDE-specific project file included as part of the source. If you want to use one, it's up to you to create your own project in whatever specific IDE you want to use. |
|
|
|
How can we be part of this ck solo club??  give us 25btc and you get a full membership joking mate! come back to this thread in 23h and you will find out if the club will live on! LE: jonnybravo0311 forgot the entrance fee of 1 block  Lol... Didn't want to scare him away right off the bat by mentioning the entrance fee  |
|
|
|
|
I've got no idea why you'd split orders like that unless you were running some kind of service for people? I tell you I'll sell you a "cloud" contract of X TH/s for Y time for Z coins... I rent hash with your coins... keeping a bit for myself as a "fee"... then point all of those rental orders to some pool of my liking... and make payouts to you based on some agreed upon earnings rate. Now I can even show you actual mining stats, like submitted shares.
Anyway, that's my guess. I see a ton of 5TH/s orders currently on NH that follow the same pattern you described, Phil.
|
|
|
|
How can we be part of this ck solo club?? There are very strict guidelines, by-laws, and application processes that must be followed exactly, and then if you make it that far, there are 3 separate votes by the current members which you must win unanimously. Kidding... it was just a bunch of us who decided to combine our coins into a single hash rental and split the rewards when we find blocks. |
|
|
|
I can double post as I am sans signature campaign! this is a fixed 5th order on west hash so we will always be hashing this is on my dime. http://solo.ckpool.org/users/1CqbvmuJcLFDFzFewKmBVAaghXEtByzY9Yorder 393769 fixed 5th on my dime westhash---------on me order 393756 200th set at 0.0096 westhash-------idle 2 btc - fees order 393760 800th set at 0.0096 nicehash-------idle 8 btc - fees Looking forward to the fun... Already we've got a 9.7G share... Let's pop a few blocks today! |
|
|
|
I see. So that transaction fee is added on to a block which contains 25 Bitcoins already to make it 25.95 BTC. So unless that block is mined your transaction is not "approved" ?
Sort of... let me try to explain it a bit more clearly. People are constantly creating transactions to move coins around. These transactions contain inputs and outputs. The inputs are what you as the sender are combining together to come up with the desired amount of coin you wish to send. The outputs are the receiver(s) of those coins and change addresses. The difference between the inputs and the outputs are the fees. Using my example above, I had two inputs, each of 1 BTC and only one output for 1.05 BTC. Because there was 0.95 BTC leftover, that becomes what we refer to as the fee. Now, pools - and individual miners if they're going at it solo - are taking some number of those transactions, and attempting to find a hash that satisfies the network difficulty, so that those transactions can be added to the public ledger known as the blockchain. When a miner is successful in doing so, a new block is created and added to the chain. The reward for creating that new block is the generation of 25 brand new coins. Additionally, because there is a difference between the inputs and outputs (in our example, 0.95 BTC), that is also awarded as part of that transaction which creates the 25 BTC. So, assuming our transaction was the only one included in a block, the end result you would see by looking at the blockchain is a block with TWO transactions. The first transaction is the 25.95 BTC of generated coins, the second is our transaction sending 1.05 BTC. There really is no "approval" here, but rather "confirmation". Your transaction, once it gets included into a block becomes confirmed. Those 25.95 BTC are referred to as generated coins and you must wait 101 confirmations before they become spendable coin. Make sense? |
|
|
|
|
Last week p2pool found a block seconds after the payout from NastyPoP and I stated then that it would impact this week's luck numbers because I didn't catch the value before that block was found. This week, the 7 day luck looks to be 84.97%, so if we average out the two numbers, we get 106.41%.
In terms of the miners, my S3 on the standard NastyP2P payout went on strike apparently, finding very few shares, and hence the payouts were lower than expected. As usual, the miner on NastyPoP was much less variant. Here are the numbers for the week:
5/8 - 5/15
NastyPoP - 0.03472755BTC
NastyP2P - 0.02216391BTC
Expected - 0.0325BTC
Luck - 84.97%
OP updated
|
|
|
|
It's not about "deciding" to add a block. If you're mining, you are in a race with many other people to "add a block". This answer has more detail: The transaction fees are calculated by the pool when they decide to add the transactions into a block they are trying to mine. The fees are not specified by a number tagged on to a transaction. It is actually the difference between the inputs and outputs, the unused amount of the inputs.
So the fees are in there when you find a block. As the mining computer (or pool), you get to keep the difference between inputs and outputs in the transactions which are in the block. You can make decisions about which transactions to try to include in the block as you go looking for a block and receiving transaction broadcasts on the network. About starting your own pool, you're going to be in tough competition. Since you're just learning the very basics here right now, it's doubtful that you're ready to compete with the big players out there. But nice enthusiasm tho! Zetaray makes a very good point, and I've bolded it to add some emphasis. We constantly talk about including fees with our transactions, and that higher fees tend to lead to transactions being included in blocks sooner. The reality is that the fees are nothing more than the difference between the inputs and the outputs. For example, if I use two inputs of 1 BTC each and my output is only 1.05 BTC then I have generously given 0.95 BTC as a fee to whoever includes my transaction in a block. Unless you're creating your own raw transactions, that stuff is hidden from you. You just say, "Send XX BTC to some address and pay YY BTC as a fee for doing it." |
|
|
|
I want to know how can i create my own cloud mining service, is there any scrpt for this?
LOL... is there a script for this. You need more than a script to make a cloud mining service. You need a boatload of hardware to mine stuff. Unless of course you just want to setup a Ponzi scam, in which case I'll offer no assistance. Come back when you've got multiple PH/s of BTC mining gear up and running. Then we'll discuss how to create a cloud mining service. |
|
|
|
Thank you ! One clarification to the latter answer you've provided :
There are a number of sites out there dedicated to crypto in one fashion or another. Most coins have their own boards and websites. There are dedicated news sites. Twitter is another large forum for spreading information.
are there additional site/board for advice/collaboration specifically for and/or about Bitcoin miners that you know of (other than twitter)? Even this site isn't exclusively dedicated to Bitcoin miners. There are plenty of other discussions going on about alternate coins, services, markets, etc. I don't know of a site that is absolutely exclusive to Bitcoin miners. Maybe it exists, but I've never been there  . If you're going to broaden the scope a bit and allow for discussion of other coins, in addition to Bitcoin, then you can include sites like cryptocointalk, gethashing, etc. |
|
|
|
Any one can help please Phuongs-MacBook-Pro:Californium-master TradeRet$ make
cd /Users/TradeRet/Desktop/Coin/Californium-master/src/leveldb && CC=/usr/bin/clang CXX=/usr/bin/clang++ /Applications/Xcode.app/Contents/Developer/usr/bin/make OPT="-pipe -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2" libleveldb.a libmemenv.a
make[1]: `libleveldb.a' is up to date.
make[1]: `libmemenv.a' is up to date.
cd /Users/TradeRet/Desktop/Coin/Californium-master; /bin/sh share/genbuild.sh /Users/TradeRet/Desktop/Coin/Californium-master/build/build.h
fatal: Not a git repository (or any of the parent directories): .git
/opt/local/bin/rcc -name bitcoin src/qt/bitcoin.qrc -o qrc_bitcoin.cpp
/usr/bin/clang++ -c -pipe -fstack-protector-all -D_FORTIFY_SOURCE=2 -O2 -arch x86_64 -Xarch_x86_64 -mmacosx-version-min=10.10 -pthread -fdiagnostics-show-option -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -Wstack-protector -DQT_GUI -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE -DUSE_IPV6 -DUSE_QRCODE -DUSE_UPNP=1 -DSTATICLIB -DUSE_IPV6=1 -DHAVE_BUILD_INFO -DMAC_OSX -DMSG_NOSIGNAL=0 -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/opt/local/share/qt4/mkspecs/macx-g++ -Ibuild -I/opt/local/Library/Frameworks/QtCore.framework/Versions/4/Headers -I/opt/local/Library/Frameworks/QtNetwork.framework/Versions/4/Headers -I/opt/local/Library/Frameworks/QtGui.framework/Versions/4/Headers -Isrc -Isrc/json -Isrc/qt -Isrc/leveldb/include -Isrc/leveldb/helpers -I/opt/local/include/db48 -I/opt/local/Library/Frameworks/QtGui.framework/Versions/4/Headers -I/opt/local/Library/Frameworks/QtNetwork.framework/Versions/4/Headers -I/opt/local/Library/Frameworks/QtCore.framework/Versions/4/Headers -I/opt/local/include -Ibuild -F/opt/local/Library/Frameworks -F/opt/local/lib -o build/qrc_bitcoin.o qrc_bitcoin.cpp
/usr/bin/clang++ -headerpad_max_install_names -fstack-protector-all -arch x86_64 -pthread -Xarch_x86_64 -mmacosx-version-min=10.10 -o Californium-Qt.app/Contents/MacOS/Californium-Qt build/macdockiconhandler.o build/macnotificationhandler.o build/bitcoin.o build/bitcoingui.o build/transactiontablemodel.o build/addresstablemodel.o build/optionsdialog.o build/sendcoinsdialog.o build/addressbookpage.o build/signverifymessagedialog.o build/aboutdialog.o build/editaddressdialog.o build/bitcoinaddressvalidator.o build/alert.o build/chainparams.o build/version.o build/sync.o build/util.o build/hash.o build/netbase.o build/key.o build/script.o build/core.o build/main.o build/init.o build/net.o build/bloom.o build/checkpoints.o build/addrman.o build/db.o build/walletdb.o build/clientmodel.o build/guiutil.o build/transactionrecord.o build/optionsmodel.o build/monitoreddatamapper.o build/transactiondesc.o build/transactiondescdialog.o build/bitcoinstrings.o build/bitcoinamountfield.o build/wallet.o build/keystore.o build/transactionfilterproxy.o build/transactionview.o build/walletmodel.o build/walletview.o build/walletstack.o build/walletframe.o build/bitcoinrpc.o build/rpcdump.o build/rpcnet.o build/rpcmining.o build/rpcwallet.o build/rpcblockchain.o build/rpcrawtransaction.o build/overviewpage.o build/csvmodelwriter.o build/crypter.o build/sendcoinsentry.o build/qvalidatedlineedit.o build/bitcoinunits.o build/qvaluecombobox.o build/askpassphrasedialog.o build/protocol.o build/notificator.o build/paymentserver.o build/rpcconsole.o build/noui.o build/leveldb.o build/txdb.o build/splashscreen.o build/intro.o build/qrcodedialog.o build/moc_bitcoingui.o build/moc_transactiontablemodel.o build/moc_addresstablemodel.o build/moc_optionsdialog.o build/moc_sendcoinsdialog.o build/moc_addressbookpage.o build/moc_signverifymessagedialog.o build/moc_aboutdialog.o build/moc_editaddressdialog.o build/moc_bitcoinaddressvalidator.o build/moc_clientmodel.o build/moc_guiutil.o build/moc_optionsmodel.o build/moc_monitoreddatamapper.o build/moc_transactiondesc.o build/moc_transactiondescdialog.o build/moc_bitcoinamountfield.o build/moc_transactionfilterproxy.o build/moc_transactionview.o build/moc_walletmodel.o build/moc_walletview.o build/moc_walletstack.o build/moc_walletframe.o build/moc_overviewpage.o build/moc_csvmodelwriter.o build/moc_sendcoinsentry.o build/moc_qvalidatedlineedit.o build/moc_bitcoinunits.o build/moc_qvaluecombobox.o build/moc_askpassphrasedialog.o build/moc_notificator.o build/moc_paymentserver.o build/moc_rpcconsole.o build/moc_splashscreen.o build/moc_intro.o build/moc_qrcodedialog.o build/moc_macdockiconhandler.o build/moc_macnotificationhandler.o build/qrc_bitcoin.o -F/opt/local/Library/Frameworks -F/opt/local/lib -lqrencode -lpthread -lminiupnpc /Users/TradeRet/Desktop/Coin/Californium-master/src/leveldb/libleveldb.a /Users/TradeRet/Desktop/Coin/Californium-master/src/leveldb/libmemenv.a -framework Foundation -framework ApplicationServices -framework AppKit -framework CoreServices -L/opt/local/lib -L/opt/local/lib/db48 -lssl -lcrypto -ldb_cxx-4.8 -lboost_system-mt -lboost_filesystem-mt -lboost_program_options-mt -lboost_thread-mt -lboost_chrono-mt -F/opt/local/Library/Frameworks -F/opt/local/lib -framework QtGui -framework QtCore -framework QtNetwork
clang: warning: argument unused during compilation: '-pthread'
ld: warning: ld: warning: ld: warning: ignoring file build/bitcoin.o, file was built for unsupported file format ( 0x4C 0x01 0x7C 0x03 0x00 0x00 0x00 0x00 0x90 0x1F 0x03 0x00 0xFB 0x09 0x00 0x00 ) which is not the architecture being linked (x86_64): build/bitcoin.oignoring file build/bitcoingui.o, file was built for unsupported file format ( 0x4C 0x01 0xC0 0x00 0x00 0x00 0x00 0x00 0x40 0x2B 0x01 0x00 0x06 0x03 0x00 0x00 ) which is not the architecture being linked (x86_64): build/bitcoingui.oignoring file build/transactiontablemodel.o, file was built for unsupported file format ( 0x4C 0x01 0x48 0x01 0x00 0x00 0x00 0x00 0xF4 0x44 0x01 0x00 0xFF 0x03 0x00 0x00 ) which is not the architecture being linked (x86_64): build/transactiontablemodel.o
ld: warning: ignoring file build/addresstablemodel.o, file was built for unsupported file format ( 0x4C 0x01 0x7E 0x01 0x00 0x00 0x00 0x00 0xCA 0x7F 0x01 0x00 0x98 0x04 0x00 0x00 ) which is not the architecture being linked (x86_64): build/addresstablemodel.o
ld: warning: ignoring file build/addressbookpage.o, file was built for unsupported file format ( 0x4C 0x01 0x12 0x00 0x00 0x00 0x00 0x00 0xB4 0x6E 0x00 0x00 0xAD 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/addressbookpage.o
ld: warning: ignoring file build/optionsdialog.o, file was built for unsupported file format ( 0x4C 0x01 0x1F 0x00 0x00 0x00 0x00 0x00 0xD4 0x97 0x00 0x00 0xDF 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/optionsdialog.o
ld: warning: ignoring file build/sendcoinsdialog.o, file was built for unsupported file format ( 0x4C 0x01 0xE0 0x00 0x00 0x00 0x00 0x00 0xA6 0xE9 0x00 0x00 0x0F 0x03 0x00 0x00 ) which is not the architecture being linked (x86_64): build/sendcoinsdialog.o
ld: warning: ignoring file build/signverifymessagedialog.o, file was built for unsupported file format ( 0x4C 0x01 0x53 0x01 0x00 0x00 0x00 0x00 0x46 0x88 0x01 0x00 0x51 0x04 0x00 0x00 ) which is not the architecture being linked (x86_64): build/signverifymessagedialog.o
ld: warning: ignoring file build/aboutdialog.o, file was built for unsupported file format ( 0x4C 0x01 0x0C 0x00 0x00 0x00 0x00 0x00 0x44 0x27 0x00 0x00 0x51 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/aboutdialog.o
ld: warning: ignoring file build/editaddressdialog.o, file was built for unsupported file format ( 0x4C 0x01 0x0C 0x00 0x00 0x00 0x00 0x00 0xCE 0x25 0x00 0x00 0x5B 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/editaddressdialog.old: warning:
ignoring file build/bitcoinaddressvalidator.o, file was built for unsupported file format ( 0x4C 0x01 0x06 0x00 0x00 0x00 0x00 0x00 0x52 0x03 0x00 0x00 0x14 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/bitcoinaddressvalidator.old: warning:
ignoring file build/chainparams.o, file was built for unsupported file format ( 0x4C 0x01 0x3C 0x01 0x00 0x00 0x00 0x00 0xB2 0x41 0x01 0x00 0xA4 0x03 0x00 0x00 ) which is not the architecture being linked (x86_64): build/chainparams.o
ld: warning: ignoring file build/alert.o, file was built for unsupported file format ( 0x4C 0x01 0x3B 0x02 0x00 0x00 0x00 0x00 0xE0 0x45 0x02 0x00 0x6D 0x06 0x00 0x00 ) which is not the architecture being linked (x86_64): build/alert.o
ld: warning: ignoring file build/hash.o, file was built for unsupported file format ( 0x4C 0x01 0x17 0x00 0x00 0x00 0x00 0x00 0xE0 0x0A 0x00 0x00 0x55 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/hash.o
ld: warning: ignoring file build/sync.o, file was built for unsupported file format ( 0x4C 0x01 0xBA 0x00 0x00 0x00 0x00 0x00 0x20 0x74 0x00 0x00 0x27 0x02 0x00 0x00 ) which is not the architecture being linked (x86_64): build/sync.old: warning:
ignoring file build/util.o, file was built for unsupported file format ( 0x4C 0x01 0x78 0x02 0x00 0x00 0x00 0x00 0x5A 0xE5 0x02 0x00 0xB5 0x07 0x00 0x00 ) which is not the architecture being linked (x86_64): build/util.o
ld: warning: ignoring file build/netbase.o, file was built for unsupported file format ( 0x4C 0x01 0x33 0x01 0x00 0x00 0x00 0x00 0x30 0x43 0x01 0x00 0x05 0x04 0x00 0x00 ) which is not the architecture being linked (x86_64): build/netbase.o
ld: warning: ignoring file build/key.o, file was built for unsupported file format ( 0x4C 0x01 0x92 0x00 0x00 0x00 0x00 0x00 0xB6 0xA7 0x00 0x00 0xEF 0x01 0x00 0x00 ) which is not the architecture being linked (x86_64): build/key.o
ld: warning: ignoring file build/core.o, file was built for unsupported file format ( 0x4C 0x01 0xD0 0x00 0x00 0x00 0x00 0x00 0x3A 0xC8 0x00 0x00 0x9A 0x02 0x00 0x00 ) which is not the architecture being linked (x86_64): build/core.o
ld: warning: ignoring file build/script.o, file was built for unsupported file format ( 0x4C 0x01 0x88 0x02 0x00 0x00 0x00 0x00 0x84 0x01 0x03 0x00 0x5B 0x07 0x00 0x00 ) which is not the architecture being linked (x86_64): build/script.o
ld: warning: ignoring file build/main.o, file was built for unsupported file format ( 0x4C 0x01 0xDB 0x06 0x00 0x00 0x00 0x00 0x9E 0x9B 0x0A 0x00 0xE8 0x13 0x00 0x00 ) which is not the architecture being linked (x86_64): build/main.o
ld: warning: ignoring file build/init.o, file was built for unsupported file format ( 0x4C 0x01 0x43 0x06 0x00 0x00 0x00 0x00 0x10 0x4D 0x06 0x00 0xA5 0x11 0x00 0x00 ) which is not the architecture being linked (x86_64): build/init.o
ld: warning: ignoring file build/bloom.o, file was built for unsupported file format ( 0x4C 0x01 0xBE 0x00 0x00 0x00 0x00 0x00 0xCC 0x8F 0x00 0x00 0x49 0x02 0x00 0x00 ) which is not the architecture being linked (x86_64): build/bloom.o
ld: warning: ignoring file build/net.o, file was built for unsupported file format ( 0x4C 0x01 0x6D 0x04 0x00 0x00 0x00 0x00 0xBC 0x74 0x05 0x00 0xDE 0x0C 0x00 0x00 ) which is not the architecture being linked (x86_64): build/net.o
ld: warning: ignoring file build/checkpoints.o, file was built for unsupported file format ( 0x4C 0x01 0xCF 0x00 0x00 0x00 0x00 0x00 0xF8 0x98 0x00 0x00 0x76 0x02 0x00 0x00 ) which is not the architecture being linked (x86_64): build/checkpoints.o
ld: warning: ignoring file build/addrman.o, file was built for unsupported file format ( 0x4C 0x01 0xE3 0x00 0x00 0x00 0x00 0x00 0xA6 0xCD 0x00 0x00 0xBB 0x02 0x00 0x00 ) which is not the architecture being linked (x86_64): build/addrman.o
ld: warning: ignoring file build/walletdb.o, file was built for unsupported file format ( 0x4C 0x01 0xE9 0x03 0x00 0x00 0x00 0x00 0x4C 0x1F 0x04 0x00 0x08 0x0B 0x00 0x00 ) which is not the architecture being linked (x86_64): build/walletdb.o
ld: warning: ignoring file build/db.o, file was built for unsupported file format ( 0x4C 0x01 0x71 0x02 0x00 0x00 0x00 0x00 0x34 0x57 0x02 0x00 0x2D 0x07 0x00 0x00 ) which is not the architecture being linked (x86_64): build/db.o
ld: warning: ignoring file build/clientmodel.o, file was built for unsupported file format ( 0x4C 0x01 0xE5 0x01 0x00 0x00 0x00 0x00 0xB2 0xDB 0x01 0x00 0x8C 0x05 0x00 0x00 ) which is not the architecture being linked (x86_64): build/clientmodel.o
ld: warning: ignoring file build/transactionrecord.o, file was built for unsupported file format ( 0x4C 0x01 0x04 0x01 0x00 0x00 0x00 0x00 0xB8 0x0A 0x01 0x00 0x24 0x03 0x00 0x00 ) which is not the architecture being linked (x86_64): build/transactionrecord.o
ld: warning: ignoring file build/guiutil.o, file was built for unsupported file format ( 0x4C 0x01 0xC2 0x00 0x00 0x00 0x00 0x00 0x84 0xCC 0x00 0x00 0xC9 0x02 0x00 0x00 ) which is not the architecture being linked (x86_64): build/guiutil.o
ld: warning: ignoring file build/monitoreddatamapper.o, file was built for unsupported file format ( 0x4C 0x01 0x07 0x00 0x00 0x00 0x00 0x00 0x1E 0x04 0x00 0x00 0x1C 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/monitoreddatamapper.o
ld: warning: ignoring file build/optionsmodel.o, file was built for unsupported file format ( 0x4C 0x01 0xE2 0x00 0x00 0x00 0x00 0x00 0x54 0x00 0x01 0x00 0xEB 0x02 0x00 0x00 ) which is not the architecture being linked (x86_64): build/optionsmodel.o
ld: warning: ignoring file build/transactiondescdialog.o, file was built for unsupported file format ( 0x4C 0x01 0x0A 0x00 0x00 0x00 0x00 0x00 0x22 0x0D 0x00 0x00 0x38 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/transactiondescdialog.o
ld: warning: ignoring file build/bitcoinstrings.o, file was built for unsupported file format ( 0x4C 0x01 0x04 0x00 0x00 0x00 0x00 0x00 0xF4 0x00 0x00 0x00 0x0A 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/bitcoinstrings.o
ld: warning: ignoring file build/transactiondesc.o, file was built for unsupported file format ( 0x4C 0x01 0x7D 0x01 0x00 0x00 0x00 0x00 0x08 0xCD 0x01 0x00 0x80 0x04 0x00 0x00 ) which is not the architecture being linked (x86_64): build/transactiondesc.o
ld: warning: ignoring file build/wallet.o, file was built for unsupported file format ( 0x4C 0x01 0x82 0x05 0x00 0x00 0x00 0x00 0x02 0x47 0x07 0x00 0x7C 0x0F 0x00 0x00 ) which is not the architecture being linked (x86_64): build/wallet.o
ld: warning: ignoring file build/bitcoinamountfield.o, file was built for unsupported file format ( 0x4C 0x01 0x0A 0x00 0x00 0x00 0x00 0x00 0xA6 0x16 0x00 0x00 0x5C 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/bitcoinamountfield.o
ld: warning: ignoring file build/transactionfilterproxy.o, file was built for unsupported file format ( 0x4C 0x01 0x0B 0x00 0x00 0x00 0x00 0x00 0xD0 0x0D 0x00 0x00 0x3D 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/transactionfilterproxy.o
ld: warning: ignoring file build/transactionview.o, file was built for unsupported file format ( 0x4C 0x01 0x1D 0x00 0x00 0x00 0x00 0x00 0x4C 0x63 0x00 0x00 0xE7 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/transactionview.o
ld: warning: ignoring file build/keystore.o, file was built for unsupported file format ( 0x4C 0x01 0x0A 0x02 0x00 0x00 0x00 0x00 0x66 0xD4 0x01 0x00 0xC2 0x05 0x00 0x00 ) which is not the architecture being linked (x86_64): build/keystore.o
ld: warning: ignoring file build/walletmodel.o, file was built for unsupported file format ( 0x4C 0x01 0x4B 0x03 0x00 0x00 0x00 0x00 0xA6 0x59 0x03 0x00 0x6D 0x09 0x00 0x00 ) which is not the architecture being linked (x86_64): build/walletmodel.o
ld: warning: ignoring file build/walletview.o, file was built for unsupported file format ( 0x4C 0x01 0xBA 0x00 0x00 0x00 0x00 0x00 0xEC 0x99 0x00 0x00 0x83 0x02 0x00 0x00 ) which is not the architecture being linked (x86_64): build/walletview.o
ld: warning: ignoring file build/walletstack.o, file was built for unsupported file format ( 0x4C 0x01 0x0F 0x00 0x00 0x00 0x00 0x00 0xAA 0x1B 0x00 0x00 0x6A 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/walletstack.old: warning:
ignoring file build/walletframe.o, file was built for unsupported file format ( 0x4C 0x01 0x0C 0x00 0x00 0x00 0x00 0x00 0xBA 0x0E 0x00 0x00 0x5B 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/walletframe.o
ld: warning: ignoring file build/bitcoinrpc.o, file was built for unsupported file format ( 0x4C 0x01 0x09 0x08 0x00 0x00 0x00 0x00 0xAC 0xD8 0x08 0x00 0xF8 0x16 0x00 0x00 ) which is not the architecture being linked (x86_64): build/bitcoinrpc.o
ld: warning: ignoring file build/rpcdump.o, file was built for unsupported file format ( 0x4C 0x01 0xF0 0x03 0x00 0x00 0x00 0x00 0x94 0xCA 0x03 0x00 0x3B 0x0B 0x00 0x00 ) which is not the architecture being linked (x86_64): build/rpcdump.o
ld: warning: ignoring file build/rpcnet.o, file was built for unsupported file format ( 0x4C 0x01 0xA3 0x01 0x00 0x00 0x00 0x00 0x1A 0x8B 0x01 0x00 0xB6 0x04 0x00 0x00 ) which is not the architecture being linked (x86_64): build/rpcnet.o
ld: warning: ignoring file build/rpcmining.o, file was built for unsupported file format ( 0x4C 0x01 0xAF 0x02 0x00 0x00 0x00 0x00 0x72 0xB2 0x02 0x00 0xB3 0x07 0x00 0x00 ) which is not the architecture being linked (x86_64): build/rpcmining.o
ld: warning: ignoring file build/rpcwallet.o, file was built for unsupported file format ( 0x4C 0x01 0xC3 0x02 0x00 0x00 0x00 0x00 0x48 0x85 0x04 0x00 0x33 0x08 0x00 0x00 ) which is not the architecture being linked (x86_64): build/rpcwallet.o
ld: warning: ignoring file build/rpcblockchain.o, file was built for unsupported file format ( 0x4C 0x01 0xB1 0x01 0x00 0x00 0x00 0x00 0x64 0xA9 0x01 0x00 0xF0 0x04 0x00 0x00 ) which is not the architecture being linked (x86_64): build/rpcblockchain.o
ld: warning: ignoring file build/rpcrawtransaction.o, file was built for unsupported file format ( 0x4C 0x01 0x6F 0x02 0x00 0x00 0x00 0x00 0xF0 0x5E 0x03 0x00 0x26 0x07 0x00 0x00 ) which is not the architecture being linked (x86_64): build/rpcrawtransaction.o
ld: warning: ignoring file build/overviewpage.o, file was built for unsupported file format ( 0x4C 0x01 0x2A 0x00 0x00 0x00 0x00 0x00 0x8E 0x76 0x00 0x00 0x17 0x01 0x00 0x00 ) which is not the architecture being linked (x86_64): build/overviewpage.o
ld: warning: ignoring file build/crypter.o, file was built for unsupported file format ( 0x4C 0x01 0x98 0x00 0x00 0x00 0x00 0x00 0xBC 0xD4 0x00 0x00 0xD2 0x01 0x00 0x00 ) which is not the architecture being linked (x86_64): build/crypter.o
ld: warning: ignoring file build/csvmodelwriter.o, file was built for unsupported file format ( 0x4C 0x01 0x10 0x00 0x00 0x00 0x00 0x00 0x90 0x15 0x00 0x00 0x4B 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/csvmodelwriter.o
ld: warning: ignoring file build/sendcoinsentry.o, file was built for unsupported file format ( 0x4C 0x01 0x1B 0x00 0x00 0x00 0x00 0x00 0x0A 0x3C 0x00 0x00 0xBE 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/sendcoinsentry.o
ld: warning: ignoring file build/qvalidatedlineedit.o, file was built for unsupported file format ( 0x4C 0x01 0x0A 0x00 0x00 0x00 0x00 0x00 0x8E 0x06 0x00 0x00 0x27 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/qvalidatedlineedit.o
ld: warning: ignoring file build/bitcoinunits.o, file was built for unsupported file format ( 0x4C 0x01 0x12 0x00 0x00 0x00 0x00 0x00 0x54 0x22 0x00 0x00 0x5E 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/bitcoinunits.o
ld: warning: ignoring file build/qvaluecombobox.o, file was built for unsupported file format ( 0x4C 0x01 0x08 0x00 0x00 0x00 0x00 0x00 0xB4 0x04 0x00 0x00 0x22 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/qvaluecombobox.o
ld: warning: ignoring file build/notificator.o, file was built for unsupported file format ( 0x4C 0x01 0x08 0x00 0x00 0x00 0x00 0x00 0xD0 0x05 0x00 0x00 0x23 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/notificator.o
ld: warning: ignoring file build/askpassphrasedialog.o, file was built for unsupported file format ( 0x4C 0x01 0x9C 0x00 0x00 0x00 0x00 0x00 0x62 0xF3 0x00 0x00 0x1E 0x02 0x00 0x00 ) which is not the architecture being linked (x86_64): build/askpassphrasedialog.o
ld: warning: ignoring file build/paymentserver.o, file was built for unsupported file format ( 0x4C 0x01 0xCA 0x00 0x00 0x00 0x00 0x00 0xB4 0x94 0x00 0x00 0x93 0x02 0x00 0x00 ) which is not the architecture being linked (x86_64): build/paymentserver.o
ld: warning: ignoring file build/protocol.o, file was built for unsupported file format ( 0x4C 0x01 0xBC 0x00 0x00 0x00 0x00 0x00 0xE2 0x83 0x00 0x00 0x53 0x02 0x00 0x00 ) which is not the architecture being linked (x86_64): build/protocol.o
ld: warning: ignoring file build/noui.o, file was built for unsupported file format ( 0x4C 0x01 0x46 0x02 0x00 0x00 0x00 0x00 0x74 0x1A 0x02 0x00 0x51 0x06 0x00 0x00 ) which is not the architecture being linked (x86_64): build/noui.o
ld: warning: ignoring file build/rpcconsole.o, file was built for unsupported file format ( 0x4C 0x01 0x39 0x01 0x00 0x00 0x00 0x00 0xD2 0x8B 0x01 0x00 0x43 0x04 0x00 0x00 ) which is not the architecture being linked (x86_64): build/rpcconsole.o
ld: warning: ignoring file build/splashscreen.o, file was built for unsupported file format ( 0x4C 0x01 0xBA 0x00 0x00 0x00 0x00 0x00 0x12 0x8E 0x00 0x00 0x54 0x02 0x00 0x00 ) which is not the architecture being linked (x86_64): build/splashscreen.o
ld: warning: ignoring file build/leveldb.o, file was built for unsupported file format ( 0x4C 0x01 0xC1 0x00 0x00 0x00 0x00 0x00 0xB2 0x85 0x00 0x00 0x50 0x02 0x00 0x00 ) which is not the architecture being linked (x86_64): build/leveldb.o
ld: warning: ignoring file build/txdb.o, file was built for unsupported file format ( 0x4C 0x01 0x0D 0x01 0x00 0x00 0x00 0x00 0x42 0x45 0x01 0x00 0x57 0x03 0x00 0x00 ) which is not the architecture being linked (x86_64): build/txdb.o
ld: warning: ignoring file build/intro.o, file was built for unsupported file format ( 0x4C 0x01 0xCB 0x00 0x00 0x00 0x00 0x00 0xF6 0xD1 0x00 0x00 0xE6 0x02 0x00 0x00 ) which is not the architecture being linked (x86_64): build/intro.o
ld: warning: ignoring file build/moc_bitcoingui.o, file was built for unsupported file format ( 0x4C 0x01 0x15 0x00 0x00 0x00 0x00 0x00 0xD0 0x18 0x00 0x00 0x9A 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_bitcoingui.o
ld: warning: ignoring file build/qrcodedialog.o, file was built for unsupported file format ( 0x4C 0x01 0x0E 0x00 0x00 0x00 0x00 0x00 0x2C 0x41 0x00 0x00 0x82 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/qrcodedialog.o
ld: warning: ignoring file build/moc_transactiontablemodel.o, file was built for unsupported file format ( 0x4C 0x01 0x10 0x00 0x00 0x00 0x00 0x00 0x24 0x0A 0x00 0x00 0x5F 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_transactiontablemodel.o
ld: warning: ignoring file build/moc_optionsdialog.o, file was built for unsupported file format ( 0x4C 0x01 0x12 0x00 0x00 0x00 0x00 0x00 0x1E 0x11 0x00 0x00 0x8D 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_optionsdialog.o
ld: warning: ignoring file build/moc_addressbookpage.o, file was built for unsupported file format ( 0x4C 0x01 0x15 0x00 0x00 0x00 0x00 0x00 0x74 0x15 0x00 0x00 0x98 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_addressbookpage.o
ld: warning: ignoring file build/moc_addresstablemodel.o, file was built for unsupported file format ( 0x4C 0x01 0x10 0x00 0x00 0x00 0x00 0x00 0x6A 0x0A 0x00 0x00 0x5F 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_addresstablemodel.o
ld: warning: ignoring file build/moc_sendcoinsdialog.o, file was built for unsupported file format ( 0x4C 0x01 0x12 0x00 0x00 0x00 0x00 0x00 0xEE 0x0E 0x00 0x00 0x85 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_sendcoinsdialog.o
ld: warning: ignoring file build/moc_aboutdialog.o, file was built for unsupported file format ( 0x4C 0x01 0x12 0x00 0x00 0x00 0x00 0x00 0x2E 0x0B 0x00 0x00 0x7E 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_aboutdialog.o
ld: warning: ignoring file build/moc_signverifymessagedialog.o, file was built for unsupported file format ( 0x4C 0x01 0x12 0x00 0x00 0x00 0x00 0x00 0xF2 0x0D 0x00 0x00 0x86 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_signverifymessagedialog.o
ld: warning: ignoring file build/moc_editaddressdialog.o, file was built for unsupported file format ( 0x4C 0x01 0x12 0x00 0x00 0x00 0x00 0x00 0x1E 0x0B 0x00 0x00 0x7D 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_editaddressdialog.o
ld: warning: ignoring file build/moc_clientmodel.o, file was built for unsupported file format ( 0x4C 0x01 0x0C 0x00 0x00 0x00 0x00 0x00 0x16 0x0C 0x00 0x00 0x3D 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_clientmodel.o
ld: warning: ignoring file build/moc_guiutil.o, file was built for unsupported file format ( 0x4C 0x01 0x26 0x00 0x00 0x00 0x00 0x00 0x90 0x16 0x00 0x00 0xC0 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_guiutil.o
ld: warning: ignoring file build/moc_bitcoinaddressvalidator.o, file was built for unsupported file format ( 0x4C 0x01 0x12 0x00 0x00 0x00 0x00 0x00 0xB2 0x07 0x00 0x00 0x46 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_bitcoinaddressvalidator.o
ld: warning: ignoring file build/moc_monitoreddatamapper.o, file was built for unsupported file format ( 0x4C 0x01 0x12 0x00 0x00 0x00 0x00 0x00 0x06 0x09 0x00 0x00 0x47 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_monitoreddatamapper.o
ld: warning: ignoring file build/moc_transactiondesc.o, file was built for unsupported file format ( 0x4C 0x01 0x10 0x00 0x00 0x00 0x00 0x00 0x0C 0x07 0x00 0x00 0x3E 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_transactiondesc.o
ld: warning: ignoring file build/moc_transactiondescdialog.o, file was built for unsupported file format ( 0x4C 0x01 0x12 0x00 0x00 0x00 0x00 0x00 0x62 0x0A 0x00 0x00 0x7D 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_transactiondescdialog.o
ld: warning: ignoring file build/moc_optionsmodel.o, file was built for unsupported file format ( 0x4C 0x01 0x15 0x00 0x00 0x00 0x00 0x00 0x06 0x0D 0x00 0x00 0x6E 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_optionsmodel.o
ld: warning: ignoring file build/moc_bitcoinamountfield.o, file was built for unsupported file format ( 0x4C 0x01 0x18 0x00 0x00 0x00 0x00 0x00 0x9C 0x0F 0x00 0x00 0x8B 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_bitcoinamountfield.o
ld: warning: ignoring file build/moc_transactionfilterproxy.o, file was built for unsupported file format ( 0x4C 0x01 0x17 0x00 0x00 0x00 0x00 0x00 0x0A 0x0D 0x00 0x00 0x7A 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_transactionfilterproxy.o
ld: warning: ignoring file build/moc_walletview.o, file was built for unsupported file format ( 0x4C 0x01 0x17 0x00 0x00 0x00 0x00 0x00 0xC6 0x14 0x00 0x00 0x98 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_walletview.o
ld: warning: ignoring file build/moc_walletframe.o, file was built for unsupported file format ( 0x4C 0x01 0x15 0x00 0x00 0x00 0x00 0x00 0x34 0x13 0x00 0x00 0x91 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_walletframe.o
ld: warning: ignoring file build/moc_transactionview.o, file was built for unsupported file format ( 0x4C 0x01 0x18 0x00 0x00 0x00 0x00 0x00 0x14 0x13 0x00 0x00 0x97 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_transactionview.o
ld: warning: ignoring file build/moc_walletstack.o, file was built for unsupported file format ( 0x4C 0x01 0x19 0x00 0x00 0x00 0x00 0x00 0x80 0x15 0x00 0x00 0xA2 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_walletstack.o
ld: warning: ignoring file build/moc_walletmodel.o, file was built for unsupported file format ( 0x4C 0x01 0x1C 0x00 0x00 0x00 0x00 0x00 0xA0 0x16 0x00 0x00 0x82 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_walletmodel.o
ld: warning: ignoring file build/moc_overviewpage.o, file was built for unsupported file format ( 0x4C 0x01 0x10 0x00 0x00 0x00 0x00 0x00 0xAC 0x0D 0x00 0x00 0x7A 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_overviewpage.o
ld: warning: ignoring file build/moc_csvmodelwriter.o, file was built for unsupported file format ( 0x4C 0x01 0x13 0x00 0x00 0x00 0x00 0x00 0xEA 0x0A 0x00 0x00 0x49 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_csvmodelwriter.o
ld: warning: ignoring file build/moc_sendcoinsentry.o, file was built for unsupported file format ( 0x4C 0x01 0x12 0x00 0x00 0x00 0x00 0x00 0xC4 0x0E 0x00 0x00 0x84 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_sendcoinsentry.o
ld: warning: ignoring file build/moc_bitcoinunits.o, file was built for unsupported file format ( 0x4C 0x01 0x15 0x00 0x00 0x00 0x00 0x00 0xDA 0x0B 0x00 0x00 0x6B 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_bitcoinunits.o
ld: warning: ignoring file build/moc_qvalidatedlineedit.o, file was built for unsupported file format ( 0x4C 0x01 0x1A 0x00 0x00 0x00 0x00 0x00 0x4E 0x0E 0x00 0x00 0x8E 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_qvalidatedlineedit.o
ld: warning: ignoring file build/moc_qvaluecombobox.o, file was built for unsupported file format ( 0x4C 0x01 0x1B 0x00 0x00 0x00 0x00 0x00 0xD2 0x10 0x00 0x00 0x99 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_qvaluecombobox.o
ld: warning: ignoring file build/moc_askpassphrasedialog.o, file was built for unsupported file format ( 0x4C 0x01 0x12 0x00 0x00 0x00 0x00 0x00 0x54 0x0C 0x00 0x00 0x7E 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_askpassphrasedialog.o
ld: warning: ignoring file build/moc_notificator.o, file was built for unsupported file format ( 0x4C 0x01 0x0D 0x00 0x00 0x00 0x00 0x00 0xBA 0x08 0x00 0x00 0x3B 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_notificator.o
ld: warning: ignoring file build/moc_paymentserver.o, file was built for unsupported file format ( 0x4C 0x01 0x11 0x00 0x00 0x00 0x00 0x00 0x58 0x0A 0x00 0x00 0x47 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_paymentserver.o
ld: warning: ignoring file build/moc_intro.o, file was built for unsupported file format ( 0x4C 0x01 0x12 0x00 0x00 0x00 0x00 0x00 0x9E 0x0F 0x00 0x00 0x86 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_intro.o
ld: warning: ignoring file build/moc_splashscreen.o, file was built for unsupported file format ( 0x4C 0x01 0x1A 0x00 0x00 0x00 0x00 0x00 0x38 0x0D 0x00 0x00 0x8D 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_splashscreen.o
ld: warning: ignoring file build/moc_rpcconsole.o, file was built for unsupported file format ( 0x4C 0x01 0x12 0x00 0x00 0x00 0x00 0x00 0x94 0x11 0x00 0x00 0x8B 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_rpcconsole.o
ld: warning: ignoring file build/moc_qrcodedialog.o, file was built for unsupported file format ( 0x4C 0x01 0x12 0x00 0x00 0x00 0x00 0x00 0x7C 0x0D 0x00 0x00 0x83 0x00 0x00 0x00 ) which is not the architecture being linked (x86_64): build/moc_qrcodedialog.o
Undefined symbols for architecture x86_64:
"_main", referenced from:
implicit entry/start for main executable
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [Californium-Qt.app/Contents/MacOS/Calif or http://pastebin.com/UASRbyTDThat what i build : sudo port install autoconf pkgconfig automake sudo port install boost qt4-mac sudo port install db48 openssl miniupnpc qrencode what else do I miss .pro file TEMPLATE = app
TARGET = Californium-qt
macx:TARGET = "Californium-Qt"
VERSION = 0.9.5.9
INCLUDEPATH += src src/json src/qt
QT += core gui network
greaterThan(QT_MAJOR_VERSION, 4): QT += widgets
DEFINES += QT_GUI BOOST_THREAD_USE_LIB BOOST_SPIRIT_THREADSAFE USE_IPV6
CONFIG += no_include_pwd
CONFIG += thread
OBJECTS_DIR = build
MOC_DIR = build
UI_DIR = build
build_macosx64 {
BOOST_INCLUDE_PATH=/opt/local/include/boost
BOOST_LIB_PATH=/opt/local/lib
BDB_INCLUDE_PATH=/opt/local/include/db48
BDB_LIB_PATH=/opt/local/lib/db48
OPENSSL_INCLUDE_PATH=/opt/local/include/openssl
OPENSSL_LIB_PATH=/opt/local/lib
MINIUPNPC_INCLUDE_PATH=/opt/local/include/miniupnpc
MINIUPNPC_LIB_PATH=/opt/local/lib
QRENCODE_INCLUDE_PATH=/opt/local/include
QRENCODE_LIB_PATH=/opt/local/lib
}
# use: qmake "RELEASE=1"
contains(RELEASE, 1) {
SDK=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.7.sdk
# Mac: compile for maximum compatibility (10.7, 32-bit)
macx:QMAKE_CXXFLAGS += -mmacosx-version-min=10.7 -isysroot $$SDK
macx:QMAKE_CFLAGS += -mmacosx-version-min=10.7 -isysroot $$SDK
macx:QMAKE_OBJECTIVE_CFLAGS += -mmacosx-version-min=10.7 $$SDK
!windows:!macx {
# Linux: static link
LIBS += -Wl,-Bstatic
}
}
# use: qmake "RELEASE=1"
contains(RELEASE, 1) {
# Mac: compile for maximum compatibility (10.5, 32-bit)
macx:QMAKE_CXXFLAGS += -mmacosx-version-min=10.5 -arch i386 -isysroot /Developer/SDKs/MacOSX10.5.sdk
macx:QMAKE_CFLAGS += -mmacosx-version-min=10.5 -arch i386 -isysroot /Developer/SDKs/MacOSX10.5.sdk
macx:QMAKE_OBJECTIVE_CFLAGS += -mmacosx-version-min=10.5 -arch i386 -isysroot /Developer/SDKs/MacOSX10.5.sdk
!win32:!macx {
# Linux: static link and extra security (see: https://wiki.debian.org/Hardening)
LIBS += -Wl,-Bstatic -Wl,-z,relro -Wl,-z,now
}
}
!win32 {
# for extra security against potential buffer overflows: enable GCCs Stack Smashing Protection
QMAKE_CXXFLAGS *= -fstack-protector-all
QMAKE_LFLAGS *= -fstack-protector-all
# Exclude on Windows cross compile with MinGW 4.2.x, as it will result in a non-working executable!
# This can be enabled for Windows, when we switch to MinGW >= 4.4.x.
}
# for extra security (see: https://wiki.debian.org/Hardening): this flag is GCC compiler-specific
QMAKE_CXXFLAGS *= -D_FORTIFY_SOURCE=2
# for extra security on Windows: enable ASLR and DEP via GCC linker flags
win32:QMAKE_LFLAGS *= -Wl,--dynamicbase -Wl,--nxcompat
# on Windows: enable GCC large address aware linker flag
win32:QMAKE_LFLAGS *= -Wl,--large-address-aware
# use: qmake "USE_QRCODE=1"
# libqrencode (http://fukuchi.org/works/qrencode/index.en.html) must be installed for support
contains(USE_QRCODE, 1) {
message(Building with QRCode support)
DEFINES += USE_QRCODE
LIBS += -lqrencode -lpthread
}
# use: qmake "USE_UPNP=1" ( enabled by default; default)
# or: qmake "USE_UPNP=0" (disabled by default)
# or: qmake "USE_UPNP=-" (not supported)
# miniupnpc (http://miniupnp.free.fr/files/) must be installed for support
contains(USE_UPNP, -) {
message(Building without UPNP support)
} else {
message(Building with UPNP support)
count(USE_UPNP, 0) {
USE_UPNP=1
}
DEFINES += USE_UPNP=$$USE_UPNP STATICLIB
INCLUDEPATH += $$MINIUPNPC_INCLUDE_PATH
LIBS += $$join(MINIUPNPC_LIB_PATH,,-L,) -lminiupnpc
win32:LIBS += -liphlpapi
}
# use: qmake "USE_DBUS=1"
contains(USE_DBUS, 1) {
message(Building with DBUS (Freedesktop notifications) support)
DEFINES += USE_DBUS
QT += dbus
}
# use: qmake "USE_IPV6=1" ( enabled by default; default)
# or: qmake "USE_IPV6=0" (disabled by default)
# or: qmake "USE_IPV6=-" (not supported)
contains(USE_IPV6, -) {
message(Building without IPv6 support)
} else {
count(USE_IPV6, 0) {
USE_IPV6=1
}
DEFINES += USE_IPV6=$$USE_IPV6
}
contains(BITCOIN_NEED_QT_PLUGINS, 1) {
DEFINES += BITCOIN_NEED_QT_PLUGINS
QTPLUGIN += qcncodecs qjpcodecs qtwcodecs qkrcodecs qtaccessiblewidgets
}
INCLUDEPATH += src/leveldb/include src/leveldb/helpers
LIBS += $$PWD/src/leveldb/libleveldb.a $$PWD/src/leveldb/libmemenv.a
!win32 {
# we use QMAKE_CXXFLAGS_RELEASE even without RELEASE=1 because we use RELEASE to indicate linking preferences not -O preferences
genleveldb.commands = cd $$PWD/src/leveldb && CC=$$QMAKE_CC CXX=$$QMAKE_CXX $(MAKE) OPT=\"$$QMAKE_CXXFLAGS $$QMAKE_CXXFLAGS_RELEASE\" libleveldb.a libmemenv.a
} else {
# make an educated guess about what the ranlib command is called
isEmpty(QMAKE_RANLIB) {
QMAKE_RANLIB = $$replace(QMAKE_STRIP, strip, ranlib)
}
LIBS += -lshlwapi
#genleveldb.commands = cd $$PWD/src/leveldb && CC=$$QMAKE_CC CXX=$$QMAKE_CXX TARGET_OS=OS_WINDOWS_CROSSCOMPILE $(MAKE) OPT=\"$$QMAKE_CXXFLAGS $$QMAKE_CXXFLAGS_RELEASE\" libleveldb.a libmemenv.a && $$QMAKE_RANLIB $$PWD/src/leveldb/libleveldb.a && $$QMAKE_RANLIB $$PWD/src/leveldb/libmemenv.a
}
genleveldb.target = $$PWD/src/leveldb/libleveldb.a
genleveldb.depends = FORCE
PRE_TARGETDEPS += $$PWD/src/leveldb/libleveldb.a
QMAKE_EXTRA_TARGETS += genleveldb
# Gross ugly hack that depends on qmake internals, unfortunately there is no other way to do it.
QMAKE_CLEAN += $$PWD/src/leveldb/libleveldb.a; cd $$PWD/src/leveldb ; $(MAKE) clean
# regenerate src/build.h
!win32|contains(USE_BUILD_INFO, 1) {
genbuild.depends = FORCE
genbuild.commands = cd $$PWD; /bin/sh share/genbuild.sh $$OUT_PWD/build/build.h
genbuild.target = $$OUT_PWD/build/build.h
PRE_TARGETDEPS += $$OUT_PWD/build/build.h
QMAKE_EXTRA_TARGETS += genbuild
DEFINES += HAVE_BUILD_INFO
}
QMAKE_CXXFLAGS_WARN_ON = -fdiagnostics-show-option -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -Wstack-protector
# Input
DEPENDPATH += src src/json src/qt
HEADERS += src/qt/bitcoingui.h \
src/qt/transactiontablemodel.h \
src/qt/addresstablemodel.h \
src/qt/optionsdialog.h \
src/qt/sendcoinsdialog.h \
src/qt/addressbookpage.h \
src/qt/signverifymessagedialog.h \
src/qt/aboutdialog.h \
src/qt/editaddressdialog.h \
src/qt/bitcoinaddressvalidator.h \
src/alert.h \
src/addrman.h \
src/base58.h \
src/bignum.h \
src/chainparams.h \
src/checkpoints.h \
src/compat.h \
src/sync.h \
src/util.h \
src/hash.h \
src/uint256.h \
src/serialize.h \
src/core.h \
src/main.h \
src/net.h \
src/key.h \
src/db.h \
src/walletdb.h \
src/script.h \
src/init.h \
src/bloom.h \
src/mruset.h \
src/checkqueue.h \
src/json/json_spirit_writer_template.h \
src/json/json_spirit_writer.h \
src/json/json_spirit_value.h \
src/json/json_spirit_utils.h \
src/json/json_spirit_stream_reader.h \
src/json/json_spirit_reader_template.h \
src/json/json_spirit_reader.h \
src/json/json_spirit_error_position.h \
src/json/json_spirit.h \
src/qt/clientmodel.h \
src/qt/guiutil.h \
src/qt/transactionrecord.h \
src/qt/guiconstants.h \
src/qt/optionsmodel.h \
src/qt/monitoreddatamapper.h \
src/qt/transactiondesc.h \
src/qt/transactiondescdialog.h \
src/qt/bitcoinamountfield.h \
src/wallet.h \
src/keystore.h \
src/qt/transactionfilterproxy.h \
src/qt/transactionview.h \
src/qt/walletmodel.h \
src/qt/walletview.h \
src/qt/walletstack.h \
src/qt/walletframe.h \
src/bitcoinrpc.h \
src/qt/overviewpage.h \
src/qt/csvmodelwriter.h \
src/crypter.h \
src/qt/sendcoinsentry.h \
src/qt/qvalidatedlineedit.h \
src/qt/bitcoinunits.h \
src/qt/qvaluecombobox.h \
src/qt/askpassphrasedialog.h \
src/protocol.h \
src/qt/notificator.h \
src/qt/paymentserver.h \
src/allocators.h \
src/ui_interface.h \
src/qt/rpcconsole.h \
src/version.h \
src/netbase.h \
src/clientversion.h \
src/txdb.h \
src/leveldb.h \
src/threadsafety.h \
src/limitedmap.h \
src/qt/splashscreen.h \
src/qt/intro.h
SOURCES += src/qt/bitcoin.cpp \
src/qt/bitcoingui.cpp \
src/qt/transactiontablemodel.cpp \
src/qt/addresstablemodel.cpp \
src/qt/optionsdialog.cpp \
src/qt/sendcoinsdialog.cpp \
src/qt/addressbookpage.cpp \
src/qt/signverifymessagedialog.cpp \
src/qt/aboutdialog.cpp \
src/qt/editaddressdialog.cpp \
src/qt/bitcoinaddressvalidator.cpp \
src/alert.cpp \
src/chainparams.cpp \
src/version.cpp \
src/sync.cpp \
src/util.cpp \
src/hash.cpp \
src/netbase.cpp \
src/key.cpp \
src/script.cpp \
src/core.cpp \
src/main.cpp \
src/init.cpp \
src/net.cpp \
src/bloom.cpp \
src/checkpoints.cpp \
src/addrman.cpp \
src/db.cpp \
src/walletdb.cpp \
src/qt/clientmodel.cpp \
src/qt/guiutil.cpp \
src/qt/transactionrecord.cpp \
src/qt/optionsmodel.cpp \
src/qt/monitoreddatamapper.cpp \
src/qt/transactiondesc.cpp \
src/qt/transactiondescdialog.cpp \
src/qt/bitcoinstrings.cpp \
src/qt/bitcoinamountfield.cpp \
src/wallet.cpp \
src/keystore.cpp \
src/qt/transactionfilterproxy.cpp \
src/qt/transactionview.cpp \
src/qt/walletmodel.cpp \
src/qt/walletview.cpp \
src/qt/walletstack.cpp \
src/qt/walletframe.cpp \
src/bitcoinrpc.cpp \
src/rpcdump.cpp \
src/rpcnet.cpp \
src/rpcmining.cpp \
src/rpcwallet.cpp \
src/rpcblockchain.cpp \
src/rpcrawtransaction.cpp \
src/qt/overviewpage.cpp \
src/qt/csvmodelwriter.cpp \
src/crypter.cpp \
src/qt/sendcoinsentry.cpp \
src/qt/qvalidatedlineedit.cpp \
src/qt/bitcoinunits.cpp \
src/qt/qvaluecombobox.cpp \
src/qt/askpassphrasedialog.cpp \
src/protocol.cpp \
src/qt/notificator.cpp \
src/qt/paymentserver.cpp \
src/qt/rpcconsole.cpp \
src/noui.cpp \
src/leveldb.cpp \
src/txdb.cpp \
src/qt/splashscreen.cpp \
src/qt/intro.cpp
RESOURCES += src/qt/bitcoin.qrc
FORMS += src/qt/forms/sendcoinsdialog.ui \
src/qt/forms/addressbookpage.ui \
src/qt/forms/signverifymessagedialog.ui \
src/qt/forms/aboutdialog.ui \
src/qt/forms/editaddressdialog.ui \
src/qt/forms/transactiondescdialog.ui \
src/qt/forms/overviewpage.ui \
src/qt/forms/sendcoinsentry.ui \
src/qt/forms/askpassphrasedialog.ui \
src/qt/forms/rpcconsole.ui \
src/qt/forms/optionsdialog.ui \
src/qt/forms/intro.ui
contains(USE_QRCODE, 1) {
HEADERS += src/qt/qrcodedialog.h
SOURCES += src/qt/qrcodedialog.cpp
FORMS += src/qt/forms/qrcodedialog.ui
}
contains(BITCOIN_QT_TEST, 1) {
SOURCES += src/qt/test/test_main.cpp \
src/qt/test/uritests.cpp
HEADERS += src/qt/test/uritests.h
DEPENDPATH += src/qt/test
QT += testlib
TARGET = Californium-qt_test
DEFINES += BITCOIN_QT_TEST
macx: CONFIG -= app_bundle
}
# Todo: Remove this line when switching to Qt5, as that option was removed
CODECFORTR = UTF-8
# for lrelease/lupdate
# also add new translations to src/qt/bitcoin.qrc under translations/
TRANSLATIONS = $$files(src/qt/locale/bitcoin_*.ts)
isEmpty(QMAKE_LRELEASE) {
win32:QMAKE_LRELEASE = $$[QT_INSTALL_BINS]\\lrelease.exe
else:QMAKE_LRELEASE = $$[QT_INSTALL_BINS]/lrelease
}
isEmpty(QM_DIR):QM_DIR = $$PWD/src/qt/locale
# automatically build translations, so they can be included in resource file
TSQM.name = lrelease ${QMAKE_FILE_IN}
TSQM.input = TRANSLATIONS
TSQM.output = $$QM_DIR/${QMAKE_FILE_BASE}.qm
TSQM.commands = $$QMAKE_LRELEASE ${QMAKE_FILE_IN} -qm ${QMAKE_FILE_OUT}
TSQM.CONFIG = no_link
QMAKE_EXTRA_COMPILERS += TSQM
# "Other files" to show in Qt Creator
OTHER_FILES += README.md \
doc/*.txt \
doc/*.md \
src/bitcoind.cpp \
src/qt/res/bitcoin-qt.rc \
src/test/*.cpp \
src/test/*.h \
src/qt/test/*.cpp \
src/qt/test/*.h
# platform specific defaults, if not overridden on command line
isEmpty(BOOST_LIB_SUFFIX) {
macx:BOOST_LIB_SUFFIX = -mt
win32:BOOST_LIB_SUFFIX = -mgw44-mt-s-1_50
}
isEmpty(BOOST_THREAD_LIB_SUFFIX) {
BOOST_THREAD_LIB_SUFFIX = $$BOOST_LIB_SUFFIX
}
isEmpty(BDB_LIB_PATH) {
macx:BDB_LIB_PATH = /opt/local/lib/db48
}
isEmpty(BDB_LIB_SUFFIX) {
macx:BDB_LIB_SUFFIX = -4.8
}
isEmpty(BDB_INCLUDE_PATH) {
macx:BDB_INCLUDE_PATH = /opt/local/include/db48
}
isEmpty(BOOST_LIB_PATH) {
macx:BOOST_LIB_PATH = /opt/local/lib
}
isEmpty(BOOST_INCLUDE_PATH) {
macx:BOOST_INCLUDE_PATH = /opt/local/include
}
win32:DEFINES += WIN32
win32:RC_FILE = src/qt/res/bitcoin-qt.rc
win32:!contains(MINGW_THREAD_BUGFIX, 0) {
# At least qmake's win32-g++-cross profile is missing the -lmingwthrd
# thread-safety flag. GCC has -mthreads to enable this, but it doesn't
# work with static linking. -lmingwthrd must come BEFORE -lmingw, so
# it is prepended to QMAKE_LIBS_QT_ENTRY.
# It can be turned off with MINGW_THREAD_BUGFIX=0, just in case it causes
# any problems on some untested qmake profile now or in the future.
DEFINES += _MT
QMAKE_LIBS_QT_ENTRY = -lmingwthrd $$QMAKE_LIBS_QT_ENTRY
}
!win32:!macx {
DEFINES += LINUX
LIBS += -lrt
# _FILE_OFFSET_BITS=64 lets 32-bit fopen transparently support large files.
DEFINES += _FILE_OFFSET_BITS=64
}
macx:HEADERS += src/qt/macdockiconhandler.h src/qt/macnotificationhandler.h
macx:OBJECTIVE_SOURCES += src/qt/macdockiconhandler.mm src/qt/macnotificationhandler.mm
macx:LIBS += -framework Foundation -framework ApplicationServices -framework AppKit -framework CoreServices
macx:DEFINES += MAC_OSX MSG_NOSIGNAL=0
macx:ICON = src/qt/res/icons/bitcoin.icns
macx:QMAKE_CFLAGS_THREAD += -pthread
macx:QMAKE_LFLAGS_THREAD += -pthread
macx:QMAKE_CXXFLAGS_THREAD += -pthread
macx:QMAKE_INFO_PLIST = share/qt/Info.plist
# Set libraries and includes at end, to use platform-defined defaults if not overridden
INCLUDEPATH += $$BOOST_INCLUDE_PATH $$BDB_INCLUDE_PATH $$OPENSSL_INCLUDE_PATH $$QRENCODE_INCLUDE_PATH
LIBS += $$join(BOOST_LIB_PATH,,-L,) $$join(BDB_LIB_PATH,,-L,) $$join(OPENSSL_LIB_PATH,,-L,) $$join(QRENCODE_LIB_PATH,,-L,)
LIBS += -lssl -lcrypto -ldb_cxx$$BDB_LIB_SUFFIX
# -lgdi32 has to happen after -lcrypto (see #681)
win32:LIBS += -lws2_32 -lshlwapi -lmswsock -lole32 -loleaut32 -luuid -lgdi32
LIBS += -lboost_system$$BOOST_LIB_SUFFIX -lboost_filesystem$$BOOST_LIB_SUFFIX -lboost_program_options$$BOOST_LIB_SUFFIX -lboost_thread$$BOOST_THREAD_LIB_SUFFIX
win32:LIBS += -lboost_chrono$$BOOST_LIB_SUFFIX
macx:LIBS += -lboost_chrono$$BOOST_LIB_SUFFIX
contains(RELEASE, 1) {
!win32:!macx {
# Linux: turn dynamic linking back on for c/c++ runtime libraries
LIBS += -Wl,-Bdynamic
}
}
system($$QMAKE_LRELEASE -silent $$TRANSLATIONS)
or : http://pastebin.com/DsMhYWNEI'm quite sure you're trying to build Californium. The git repo is a mess... somebody pushed up all of their local object files, and the QT pro is obviously built by somebody on Windows, since every dependency starts with "C:/". Change all the dependencies to point to wherever they reside on your Mac... assuming you're using macports, that's likely some flavor of /opt/local/lib and /opt/local/include. Then, from root directory of the cloned git repo, qmake USE_UPNP=- Then, make clean to get rid of all the object files brought over from the mess in git Finally, try to build with make. By the way, this really should be in the alt-coins boards. |
|
|
|
What do you mean power consumption is not an object? If you put inside 1000 S5 miners, power consumption ll go through the roof and someone will notice it, unless you have your own hydro power or similar.
I just went with the situation as presented by the OP. He wrote that the electricity is "essentially free". That could mean any number of things like, "I get $0.01 or less rates" or "I own my own hydro power plant". As posed the OP basically says, "forget all of those other factors like power and cooling and space and just tell me how to setup a mining farm". |
|
|
|
Hello guys ,
I make a noob experiment for p2pool , i rent miners 2 THs and point that to minefast ( which is the p2pool mining pool ) with user name my wallet add and pass x , in the other side i have miner that run on my own node (wallet) with user name and pass same with the miner that i rent , the target is i just want to know are the hashing power is miner rent + my miner or they run independently each other. The results of that noob experiment is each miner run independently . the question is how the p2pool networks identify each miner ? cause before i join minefast , i check my address wallet and its appear with the hashing of my own miners , after i join the minefast the hashing powers appear only the rent miner.
regards
Assuming I read your post correctly, you've got some hash rate (we'll call it X) pointed to one p2pool node using a BTC address (we'll call it A). You've also got some other hash rate (Y) pointed to another p2pool node using the same address (A). Each node will report only what the node sees for hash rate for the miners pointed to it. So, on node 1 you'll see hash rate X. On node 2, you'll see hash rate Y. If the node tracks expected payouts, then you'll see the combined expected payout on each node. This is because you're using the same address to mine to. The p2pool network as a whole makes payouts to addresses that have valid shares on the share chain. Since both sets of your miners (your own gear and rented gear) use the same address, p2pool itself knows of just the one address and the shares on the share chain for that address. By the way, when you look at stats on coincadence, he guesses hash rate by address based on your expected payout. So, in effect, you'll see about X+Y reported assuming of course you've got a full N value for your shares on the chain. |
|
|
|
Does that mean that if I solo-mine and don't get a block I will get transaction fees? You get nothing unless you solve a block. Assuming the block is not orphaned, you get the full block reward (currently 25 BTC) and all the transaction fees for every transaction included in the block you mined. |
|
|
|
Another lucky winner! Congrats to you for hitting it with authority on just about 12.5TH/s My little U2s have a long way to go yet. Hopefully our group hits a block or two this weekend. |
|
|
|
|
1. To what degree do miners collaborate with each other (for example: purchasing miners in bulk, purchasing datacenter services , electricity etc) ?
I'd say it depends on from where you are getting your hardware and/or services. For example, unless you're purchasing a large quantity of hardware from Bitmain, chances are you're just going to hit their website and place your order. On the other hand, when Spondoolies started selling their SP10 last year, I spoke with Guy (the CEO) via email a number of times, and worked with Zvi (their lead engineer) with some firmware problems that led to the gear not working on p2pool. He addressed the issue and provided me with a fix within 24 hours.
If you're purchasing gear used, then there's typically quite a bit of interaction and collaboration. I'll continue using the SP10 as an example here. When I sold it, I communicated quite a bit with the buyer, and reconfigured the miner to point to his pools prior to shipping it to him. Also, escrow services provided by a number of the trusted users here on the forums lead to greater collaboration between folks. There are also users here who sell services (like providing hosting, power supplies, etc) and run their own hardware projects (GekkoScience is one I can think of off the top of my head).
2. other than Bitcointalk, and reddit forums, are there additional "spaces"/forums/groups/other that miners use to catchup on things and/or use for discussions ?
There are a number of sites out there dedicated to crypto in one fashion or another. Most coins have their own boards and websites. There are dedicated news sites. Twitter is another large forum for spreading information.
|
|
|
|
|
Show Posts
