Thanks both for your replies, but that's not the case. I had installed the dependencies prior to compiling the code. Just to confirm: apt-get install libgmp-dev libmpfr-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libgmp-dev is already the newest version.
libmpfr-dev is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
|
|
|
|
Has anyone had any trouble compiling this coin from source on Ubuntu 14.04? I've got all the dependencies covered - I've compiled and built who-knows-how-many coin daemons on this and OS X. However, with this coin I run into problems. I do the usual: and end up with this: g++ -c -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -D_FILE_OFFSET_BITS=64 -DOPENSSL_NO_SSL2=1 -I/home/miner/WLC/src -I/home/miner/WLC/src/obj -DUSE_UPNP=0 -DUSE_IPV6=1 -I/home/miner/WLC/src/leveldb/include -I/home/miner/WLC/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2 -MMD -MF obj/db.d -o obj/db.o db.cpp
In file included from /usr/include/boost/atomic/detail/gcc-x86.hpp:198:0,
from /usr/include/boost/atomic/detail/platform.hpp:20,
from /usr/include/boost/atomic/atomic.hpp:17,
from /usr/include/boost/atomic.hpp:12,
from /usr/include/boost/thread/pthread/once_atomic.hpp:20,
from /usr/include/boost/thread/once.hpp:20,
from /usr/include/boost/thread.hpp:17,
from util.h:26,
from bignum.h:21,
from main.h:8,
from db.h:8,
from db.cpp:6:
/usr/include/boost/atomic/detail/base.hpp:396:13: error: ‘ptrdiff_t’ does not name a type
typedef ptrdiff_t difference_type;
^
/usr/include/boost/atomic/detail/base.hpp:452:26: error: ‘difference_type’ has not been declared
value_type fetch_add(difference_type v, memory_order /*order*/ = memory_order_seq_cst) volatile BOOST_NOEXCEPT
^
/usr/include/boost/atomic/detail/base.hpp:461:26: error: ‘difference_type’ has not been declared
value_type fetch_sub(difference_type v, memory_order /*order*/ = memory_order_seq_cst) volatile
^
/usr/include/boost/atomic/detail/base.hpp:476:5: error: ‘difference_type’ has not been declared
BOOST_ATOMIC_DECLARE_POINTER_OPERATORS
^
/usr/include/boost/atomic/detail/base.hpp:476:5: error: ‘difference_type’ has not been declared
BOOST_ATOMIC_DECLARE_POINTER_OPERATORS
^
/usr/include/boost/atomic/detail/base.hpp:488:13: error: ‘ptrdiff_t’ does not name a type
typedef ptrdiff_t difference_type;
^
/usr/include/boost/atomic/detail/base.hpp:551:26: error: ‘difference_type’ has not been declared
value_type fetch_add(difference_type v, memory_order /*order*/ = memory_order_seq_cst) volatile BOOST_NOEXCEPT
^
/usr/include/boost/atomic/detail/base.hpp:562:26: error: ‘difference_type’ has not been declared
value_type fetch_sub(difference_type v, memory_order /*order*/ = memory_order_seq_cst) volatile
^
/usr/include/boost/atomic/detail/base.hpp:573:5: error: ‘difference_type’ has not been declared
BOOST_ATOMIC_DECLARE_VOID_POINTER_OPERATORS
^
/usr/include/boost/atomic/detail/base.hpp:573:5: error: ‘difference_type’ has not been declared
BOOST_ATOMIC_DECLARE_VOID_POINTER_OPERATORS
^
In file included from /usr/include/boost/atomic/detail/platform.hpp:20:0,
from /usr/include/boost/atomic/atomic.hpp:17,
from /usr/include/boost/atomic.hpp:12,
from /usr/include/boost/thread/pthread/once_atomic.hpp:20,
from /usr/include/boost/thread/once.hpp:20,
from /usr/include/boost/thread.hpp:17,
from util.h:26,
from bignum.h:21,
from main.h:8,
from db.h:8,
from db.cpp:6:
/usr/include/boost/atomic/detail/gcc-x86.hpp:1025:13: error: ‘ptrdiff_t’ does not name a type
typedef ptrdiff_t difference_type;
^
/usr/include/boost/atomic/detail/gcc-x86.hpp:1094:15: error: ‘difference_type’ has not been declared
fetch_add(difference_type v, memory_order order = memory_order_seq_cst) volatile BOOST_NOEXCEPT
^
/usr/include/boost/atomic/detail/gcc-x86.hpp:1106:15: error: ‘difference_type’ has not been declared
fetch_sub(difference_type v, memory_order order = memory_order_seq_cst) volatile BOOST_NOEXCEPT
^
In file included from /usr/include/boost/atomic/detail/gcc-x86.hpp:198:0,
from /usr/include/boost/atomic/detail/platform.hpp:20,
from /usr/include/boost/atomic/atomic.hpp:17,
from /usr/include/boost/atomic.hpp:12,
from /usr/include/boost/thread/pthread/once_atomic.hpp:20,
from /usr/include/boost/thread/once.hpp:20,
from /usr/include/boost/thread.hpp:17,
from util.h:26,
from bignum.h:21,
from main.h:8,
from db.h:8,
from db.cpp:6:
/usr/include/boost/atomic/detail/gcc-x86.hpp:1111:5: error: ‘difference_type’ has not been declared
BOOST_ATOMIC_DECLARE_VOID_POINTER_OPERATORS
^
/usr/include/boost/atomic/detail/gcc-x86.hpp:1111:5: error: ‘difference_type’ has not been declared
BOOST_ATOMIC_DECLARE_VOID_POINTER_OPERATORS
^
In file included from /usr/include/boost/atomic/detail/platform.hpp:20:0,
from /usr/include/boost/atomic/atomic.hpp:17,
from /usr/include/boost/atomic.hpp:12,
from /usr/include/boost/thread/pthread/once_atomic.hpp:20,
from /usr/include/boost/thread/once.hpp:20,
from /usr/include/boost/thread.hpp:17,
from util.h:26,
from bignum.h:21,
from main.h:8,
from db.h:8,
from db.cpp:6:
/usr/include/boost/atomic/detail/gcc-x86.hpp:1123:13: error: ‘ptrdiff_t’ does not name a type
typedef ptrdiff_t difference_type;
^
/usr/include/boost/atomic/detail/gcc-x86.hpp:1193:15: error: ‘difference_type’ has not been declared
fetch_add(difference_type v, memory_order order = memory_order_seq_cst) volatile BOOST_NOEXCEPT
^
/usr/include/boost/atomic/detail/gcc-x86.hpp:1206:15: error: ‘difference_type’ has not been declared
fetch_sub(difference_type v, memory_order order = memory_order_seq_cst) volatile BOOST_NOEXCEPT
^
In file included from /usr/include/boost/atomic/detail/gcc-x86.hpp:198:0,
from /usr/include/boost/atomic/detail/platform.hpp:20,
from /usr/include/boost/atomic/atomic.hpp:17,
from /usr/include/boost/atomic.hpp:12,
from /usr/include/boost/thread/pthread/once_atomic.hpp:20,
from /usr/include/boost/thread/once.hpp:20,
from /usr/include/boost/thread.hpp:17,
from util.h:26,
from bignum.h:21,
from main.h:8,
from db.h:8,
from db.cpp:6:
/usr/include/boost/atomic/detail/gcc-x86.hpp:1217:5: error: ‘difference_type’ has not been declared
BOOST_ATOMIC_DECLARE_POINTER_OPERATORS
^
/usr/include/boost/atomic/detail/gcc-x86.hpp:1217:5: error: ‘difference_type’ has not been declared
BOOST_ATOMIC_DECLARE_POINTER_OPERATORS
^
make: *** [obj/db.o] Error 1
I initially thought I might be missing some boost libraries, but confirmed that all are properly installed: apt-get install libboost-dev libboost-system-dev libboost-filesystem-dev libboost-program-options-dev libboost-thread-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libboost-dev is already the newest version.
libboost-dev set to manually installed.
libboost-filesystem-dev is already the newest version.
libboost-filesystem-dev set to manually installed.
libboost-program-options-dev is already the newest version.
libboost-program-options-dev set to manually installed.
libboost-system-dev is already the newest version.
libboost-system-dev set to manually installed.
libboost-thread-dev is already the newest version.
libboost-thread-dev set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Thanks in advance. |
|
|
|
Has anyone compiled a complete list of all p2pool merge-mine coins, their respective ports and exchanges on which they can be traded? I know of the following coins: NMC IXC (no new coins for finding blocks as all have been generated) I0C GRP DVC HUC FSC (coin is dead) UNO WLC As has been previously pointed out, to add a coin to be merge-mined, once your coin's daemon is up and running and synched, you just start your p2pool instance with the following additional parameter (assuming all coin daemons are running on the same machine as p2pool): --merged http://[rpc_user_name]:[rpc_password]@127.0.0.1:port
|
|
|
|
Hi all just abit offtopic. I started using p2pool got it setup and running on my local node. Now just a quick qustion how to make my node public so that i can have some of my friends connect to it.
Thanks in advance.
Not off topic at all. Assuming you have a BTC p2pool node setup, you'll need to open up port 9332. To be a "good" citizen, you should have the following ports open: 8333 - BTC peers 9333 - p2pool peers 9332 - p2pool miners Note that opening up 8333 and 9333 will allow multiple peers to connect and you will see higher bandwidth usage. |
|
|
|
I haven't seen any evidence of miners intentionally mining empty blocks. To me, they just seem to be a byproduct of their mining operations which probably aren't all that optimized so mining empty blocks still allows them to be competitive. Of course, if they are mining empty blocks intentionally, then they are also losing some Bitcoin from fees (not enough to have a large impact) and hurting the network.
You won't see it, either. A miner doesn't control whether or not the block is empty, the pool does. One could argue that as a solo miner, I could configure my bitcoind to do something silly like "do not include any transactions that have a fee lower than 100 BTC". In that case, if I ever happened to find a solo block, then it would very likely be empty. Also, for Chinese miners and pools, that overhead does matter. They might have a powerful server, probably not a well tuned bitcoind or they have poorly written custom software, and they most likely have a shitty internet connection due to the Great Firewall. This makes them find every possible way to make a profit, which includes having to SPV mine and mine empty blocks.
If they have a poorly tuned bitcoind, poorly written custom software, etc. shouldn't they address those problems? They don't. Instead they remain lazy. Bitmain has proven time and again they can't write software worth a damn, and they just don't do anything about it. Even with kano including the Bitmain drivers in mainline cgminer, Bitmain still uses its own crap fork. There are pools and pool software out there proven to work faster and be better for the health of the ecosystem. If these players are so worried about their profit, don't you think they'd do everything they can to maximize it? SPV mining and empty blocks is not the answer, yet these pools and their operators fall back on it just the same. |
|
|
|
|
LOL... which goes right back to what I stated... there's no way to definitively identify the block finder since you cannot connect to every single node out there.
|
|
|
|
So are you stating the Blockchain.info doesn't necessary have the correct information too?
Yes, I am using the standard core API
That's exactly what I'm stating. Blockchain.info, whomined.com, my code... we all make best guesses based upon evaluating the coinbase script, the BTC addresses of the coinbase transaction, counting the number of vouts in the coinbase transaction, etc. There simply is no definitive way to describe who found the blocks with 100% accuracy. |
|
|
|
|
No problem. I just happened to check the blocks and saw that was orphaned... and I was like, "Huh? I swear I got BTC for that... let me check."
|
|
|
|
|
I've done this... there are a number of things that contribute to getting who mined data. The coinbase signature isn't necessarily reliable because you can put whatever you want there. Sure, a lot of pools advertise they solved a block by putting some identifier in there. You can also use the BTC address of the generation transaction. Sometimes you can use the fact that the coinbase transaction has a ton of outputs (p2pool). It's a messy process where you need to scrape the data and analyze it, and even then you aren't guaranteed to figure out who actually solved the block.
If you're using standard core APIs:
getblockhash
getblock
getrawtransaction
|
|
|
|
|
An S5 (or S1, S2, S3, S4, S4+, U2, U3) can be used to mine any coin that uses SHA256D. For example, BTC, NMC, HUC, MZC, CURE, TAK, PPC... all can be mined with that hardware.
Coins like LTC, DOGE, DASH, etc cannot be mined with that because they use different hashing algorithms (Scrypt, X11, etc).
|
|
|
|
Not sure why your front-end is doing this windpath, but it's showing the latest block found by p2pool as orphaned:  That block wasn't orphaned... |
|
|
|
thanks for all your answers I know , I'am not that old so I guess I really can hold my bitcoins till 5-10 years without having any issues. Speaking about cloud mining which I never understood and never will most likely , how the hell and why the hell someone would pay BTC to get BTC ? I just don't understand. Cloud mining is letting companies mine for you , correct ? so you give them money so you generate BTC , well why do I pay BTC to get BTC (probably less) ?  im only one not getting it ? You actually understand it perfectly  . Legit cloud mining companies own hardware and they mine with it. They sell you shares of that mining equipment. For example, let's say I'm a cloud mining provider. I have a very small operation with only a single 1TH/s miner. I'm going to sell you that 1TH/s contract. So, in our example, I as the provider paid 1 BTC for the miner. I'm selling you that same 1TH/s for 1.5 BTC. As the provider, I've now made my money back plus some profit. Earnings from the miner are now paid out to you... and oh yeah, I probably am going to charge you maintenance fees (I've got to cover the operating costs after all). Now, I've got 1.5 BTC, so I go and buy myself another 1TH/s miner. I've still got 0.5 BTC profit and I've got another miner that I can sell a contract for to somebody else. You as the person who bought the contract are getting paid out based on whatever the miner earns minus any operating costs. You are hoping that this contract will make you back more than the 1 BTC you initially paid for it. Typically, if and when the cost to operate the miner exceeds what the miner pays out, the contract is terminated. The primary difference between cloud mining and having somebody host your gear is that with cloud mining, you don't own the hardware. The cloud mining provider has already made his profit from selling you the contract. Basically it's a game where you're hedging against the cloud mining provider. |
|
|
|
Any answers to taxation questions are going to be varied and inconsistent. The regulations around virtual currencies are not clearly defined by any stretch of the imagination. @notlist3d, I'd disagree with this statement you made: What does successfully mine mean? I consider sucessfully mining once I sell for USD. I don't see it as successful when you just have BTC, as you don't know at time of sale if it's gain or loss.
If you're mining, the instant you acquired that coin it is a gain. There is no loss incurred by the action. You can certainly try to offset the gain by factoring in the cost of electricity to have mined the coin, but that implies you've set yourself up as a mining business, and are incurring expenses related to the operation of that business. Short answer: do what notlist3d stated and find yourself a CPA who is versed in virtual currency tax laws. |
|
|
|
I'm on 0.11 as well... having just updated and rebuilt the client, this is what I see: miner@devildog:~/RelayNode/c++$ ./relaynetworkclient 127.0.0.1 8333
Server 0 (public.us-east.relay.mattcorallo.com) took 2036 ms to respond 20 times.
Server 1 (public.us-west.relay.mattcorallo.com) took 24449 ms to respond 20 times.
Server 2 (public.eu.relay.mattcorallo.com) took 1676 ms to respond 20 times.
Server 3 (public.sgp.relay.mattcorallo.com) took 5156 ms to respond 20 times.
Server 4 (public.jpy.relay.mattcorallo.com) took 3309 ms to respond 20 times.
Using server public.02.relay.mattcorallo.com
Connected to relay node with protocol version sponsor printer
Connected to bitcoind with version 70002
Finished connect handshake with bitcoind
Sent transaction of size 373 (out-of-band) to relay server
Sent transaction of size 374 (out-of-band) to relay server
Sent transaction of size 743 (out-of-band) to relay server
Sent transaction of size 191 (out-of-band) to relay server
Sent transaction of size 407 (out-of-band) to relay server
Sent transaction of size 373 (out-of-band) to relay server
Sent transaction of size 223 (out-of-band) to relay server
Sent transaction of size 14798 (out-of-band) to relay server
Sent transaction of size 225 (out-of-band) to relay server
Sent transaction of size 782 (out-of-band) to relay server
Sent transaction of size 225 (out-of-band) to relay server
Sent transaction of size 257 (out-of-band) to relay server
Sent transaction of size 14787 (out-of-band) to relay server
Sent transaction of size 226 (out-of-band) to relay server
Sent transaction of size 257 (out-of-band) to relay server
Sent transaction of size 192 (out-of-band) to relay server
Sent transaction of size 225 (out-of-band) to relay server
Sent transaction of size 373 (out-of-band) to relay server
Sent transaction of size 226 (out-of-band) to relay server
Sent transaction of size 226 (out-of-band) to relay server
Sent transaction of size 404 (out-of-band) to relay server
Sent transaction of size 226 (out-of-band) to relay server
Sent transaction of size 225 (out-of-band) to relay server
Sent transaction of size 14790 (out-of-band) to relay server
Sent transaction of size 259 (out-of-band) to relay server
Sent transaction of size 3379 (out-of-band) to relay server
Sent transaction of size 438 (out-of-band) to relay server
Sent transaction of size 369 (out-of-band) to relay server
Sent transaction of size 14787 (out-of-band) to relay server
Sent transaction of size 521 (out-of-band) to relay server
Sent transaction of size 191 (out-of-band) to relay server
Sent transaction of size 225 (out-of-band) to relay server
Sent transaction of size 372 (out-of-band) to relay server
Sent transaction of size 340 (out-of-band) to relay server
Sent transaction of size 14799 (out-of-band) to relay server
I haven't seen a single received transaction.EDIT: Just got my first received transaction: [2015-07-16 15:15:54+00] 00000000000000000e76821cb710d1a40878ead2e83fa8a0ec26b31f92263b09 recv'd, size 592138 with 597877 bytes on the wire
|
|
|
|
|
As of right now, an S3 expects to earn you 0.004332BTC a day. That number changes based upon difficulty adjustments. For example, if the next adjustment brings the difficulty up to 53G, that S3 would expect to then earn 0.004175BTC a day. At the current exchange rate and current difficulty level, that's about $1.24 a day.
|
|
|
|
|
You're living with your parents. Even if the electric costs them only $0.05 per kWh, you start plugging in miners and they're going to notice the increase in the bill.
An S3 will cost them about $12.41 a month. An S5 will run them about $21.54 a month. This assumes that $0.05 is what they actually pay.
|
|
|
|
|
Wasn't the design of the S2 supposed to be that modular machine? A bunch of boards on a backplane that could easily be swapped out. Unfortunately, they (Bitmain) never followed through with any upgrade kits. That kind of setup would be great for the datacenter guys. Keep the chassis and just upgrade the boards.
|
|
|
|
That was you who hit the block right before the pool went down? Congrats!!!! |
|
|
|
Here is the best strategy to earn big money with ASIC miners...
<snip>
i love this ^^ and i want to borrow your time machine... i promise to give you back in a blink of an eye, u wont even notice i'm gone... If you do it right, you can return the time machine before you borrow it! Or will that cause a rip in the time-space continuum? Btw, you must kill Hitler if you borrow the time machine. But everyone already knows that. It's Time Travel 101. And clearly, nobody's invented the time machine yet since history records Hitler causing havoc. Speaking of rips in the time-space continuum, wouldn't killing Hitler cause a pretty nasty one? Of course, there's always the problem of the paradox... imagine I create a time machine that can only see 1 minute into the past. I see myself and decide on a whim that I can't take it anymore and shoot my former self. So, now my former self is dead, which in turn means I died a minute before I shot myself. Wait... who pulled the trigger then? |
|
|
|
|
Show Posts
