|
Well... the guy did post that he was from New Zealand... and there was some pretty interesting research done a page or so ago in this thread that tied things together and supposedly identified him.
Not being from New Zealand myself, I don't have a clue about their cyber laws.
|
|
|
|
|
You mean there might not be a giant backlog of transactions??? INCONCEIVABLE!!!
|
|
|
|
Why are you trying to import a private key using php? Just use the command line. What possible use case is there for having a web page that can collect a private key and import it into your wallet (other than the obvious nefarious ones)? bitcoin-cli importprivkey "yourkey"
|
|
|
|
Ok i have everything working now. But i don't understand all that about the rewards and everything. Here is a screenshot of my pool website, see screenshot http://prntscr.com/98x8bbUnconfirmed reward .12$ what is that? http://prntscr.com/98x8zuSo .12$ is what im going to win and still 89 confirmations left to be filled. That would take all night long right? So .12$ is what im going to win to leave the machine on the entire night? I saw in a bitcoin profit calculator that my 2000GH/S machine, with free electricity and all would make me win .22$ per hour. Wow... you didn't read up at all on how the whole mining thing works, did you? You earned $0.12 for that block. Every block the pool finds you'll earn some BTC as long as you're mining. Let it ride for a while and you'll see the earnings add up. Right now your S4 at 2TH/s would expect to earn just about 0.01383 BTC a day (or ~$4.93 at current exchange rates). That will change in a few days when the network difficulty adjusts. |
|
|
|
If you want to create fresh btc addresses (in bulk) you can use bitcoin core (Without syncing).
on the bitcoin.conf file just add this:
keypoolsize=10000
this will create 10k btc addresses. Sounds great. Thank you very much! But where is " bitcoin.conf"? I'm running a Bitcoin Core on OSX... Sorry, I'm not good on these things  then you can dump this wallet and get these 10k address & priv keys. I get that, thanks, but what do you mean with " ...& priv keys"? To answer your earlier question... bitcoin daemon is just the bitcoin process (to start it in linux you type: bitcoind). Since you're on a Mac, I can certainly help you there  . By default using the Bitcoin application on a Mac does not create a bitcoin.conf file. You create your own. When you first start up your Bitcoin application (assuming of course the standard Bitcoin Core software downloaded from bitcoin.org), it creates a directory here: ~/Library/Application Support/Bitcoin
It is in that directory that you want to create the bitcoin.conf file. |
|
|
|
I fully get what you're stating. I can't imagine running a process like a coin daemon without at least some rudimentary monitoring. I guess what I'm getting at is that the answer shouldn't just be "restart it when it acts up" and that's the end of it. Yes, that might be necessary, but it would be far more valuable to figure out why it was acting up in the first place so that the underlying problem can be addressed. It's kind of like just constantly replacing oil in your car when you notice it's low, instead of looking into it to find out your seals are shot or the oil pan is leaking like a sieve . |
|
|
|
|
I have no idea how you twisted that into me spilling 100 gallons of water, or proving your point in any way. I successfully carried 100 gallons of water to the village. I did it all in one day, and that was 2 days ago. You also successfully carried 100 gallons of water; however, you carried 25 gallons a day over 4 days. The village now has 200 gallons of water.
Your suggestion is that because my water arrived 2 days ago, my water is somehow worth less than your water.
|
|
|
|
Sounds like something Obama would want to do. Lolol.
LOL... actually I think you have it backwards... wanting someone else to carry you water now, while you are in "retirement". Let's use your example... I carried 100 gallons of water to the village two days ago. You carried 100 gallons of water (25 gallons a day for 4 days). Why is your water worth more than my water? |
|
|
|
|
Take a look at how PPLNS works. By definition it discourages pool hopping. That's why pool operators tend to use it over PROP.
What you are suggesting is that part time miners be punished.
|
|
|
|
I hate to be "that guy" but you're a newbie account. You're going to have a VERY hard time convincing anybody to trust you. I, too, was burned by Nexious - I was the guy that found the block on his pool and exposed the scammer. As a result, I just opened up my own pool. You're welcome to throw your hash (and your friends' hash) my way. www.bravo-mining.com |
|
|
|
Have your website make a call back to your bitcoin daemon to get a new address. If you want to keep track of your customers (i.e. they've logged in and you know their user name) you can make a call like this: $bitcoin->getnewaddress($username);
|
|
|
|
|
I think it would be pretty freaking amazing if somebody just happened to fire up good old minerd on his work laptop to show mining to somebody at work and they hit a block. Chances of it happening? Infinitesimally small. Look on the guy's face if it happened? Priceless!
|
|
|
|
Just my humble opinion, but the 5N payment method is what has interested me to mine on Kanos pool, as no one else offers such a service as far as I know of. If you want something else for payment scheme, there are many other pools that are maybe more to your taste, but for me with my old Ant S2 miners this has been a valuable service. And I am in it for the long run, not changing pools anymore, just letting them run here, you get the most benefit when you reach the 5N potential. I maybe incorrect on these things, if so, Kano will likely let me hear it  But still I think no one else is offering this kind of great payout scheme and pool, and am very glad for the service he provides and with very low fees for the miners.. Edit: and not to mention all the wisdom Kano dispenses concerning the finer points of bitcoin/mining.. Also thanks to CK as well.. -Thankful miner. You might want to take a look at PPLNS pools in general. They all offer exactly that service . Sure, the N value may be different, but the process is the same. Kano runs a great pool. He's actively involved here on the forums. He might know a thing or two about the pool's code (and the mining software most of us use)  |
|
|
|
I would ask you back why my shares are worth less than your shares. Let's say I rent 1PH/s for a day. For the sake of argument, let's say I get 1 billion shares. That's all I can afford for the week. You, on the other hand rent 200 TH/s a day for 5 days. You get the same 1 billion shares. However, because you mined longer to get exactly the same number of shares, you think you should be paid out more than me?
Humm... Guess I am not understanding your question. Don't see how one is worth more then the other. BUT, yes, if your one billion shares never produced anything, you still have a chance to earn 70% average of it if others continue to mine for you, but in actuality, you are no longer mining, so why do you think you are entitled to be paid at possibly 100% plus yet if others got lucky for you? Why would I not be entitled to earn full value for the shares I submitted? So what if I'm no longer mining? I mined for a period of time and contributed to the pool's efforts towards solving a block. What you're suggesting is that just because my billion shares happen to be older than your billion shares, that mine are somehow worth less. |
|
|
|
|
Will do. I've been trying to avoid writing a "restart coin daemon" script. Yes, I know restarting it helps, and is something a number of people do... but it feels like we're treating the symptoms, rather than trying to find a cure. It also seems counterproductive for a pool to be constantly restarting the coin daemon as that would flush the mempool and render worker shares invalid on the restart... one of those shares might have solved a block.
|
|
|
|
|
I would ask you back why my shares are worth less than your shares. Let's say I rent 1PH/s for a day. For the sake of argument, let's say I get 1 billion shares. That's all I can afford for the week. You, on the other hand rent 200 TH/s a day for 5 days. You get the same 1 billion shares. However, because you mined longer to get exactly the same number of shares, you think you should be paid out more than me?
|
|
|
|
Rav3n's fork has support for a boatload of alt coins. Adding more hash to p2pool is a double-edged sword. Yes, it means more blocks. However, it also means higher share difficulty and higher variance for miners - especially noticeable the lower hash rate you have as a miner. Many pages of this thread have been dedicated to that very discussion |
|
|
|
Hi psycodad, I appreciate the response. I have not set the RPC threads previously, just relying upon the default value. I will give your suggestion a try to see if it helps mitigate the issues. Thanks |
|
|
|
Hey everyone, I asked this in the Technical Support forums as well, but thought I'd try my luck here, too. Since a lot of alt coin pools run on the NOMP/MPOS combination, perhaps some of you pool operators have run into a similar issue, and have a solution. Below is the text from my post: All, Very recently I have run into an issue with my bitcoin daemon. I am wondering if it might have to do with the pool software I'm running on top of it, and will likely ask this same question if I can find a forum thread for the pool . Here's what I notice: 1) I start up the bitcoin daemon process and all is happy. 2) After about 24 hours, the process becomes completely unresponsive. Typing: Or any other command just hangs without returning. 3) This causes all kinds of havoc on my pool. Website runs exceptionally slow. I get bombarded with mail from the cron jobs saying they're already running. Things like that. When I look at my debug.log, all I see is it trying to create new blocks: 2015-12-03 12:26:06 CreateNewBlock(): total size 998979
2015-12-03 12:26:12 CreateNewBlock(): total size 998945
2015-12-03 12:26:18 CreateNewBlock(): total size 998993
2015-12-03 12:26:24 CreateNewBlock(): total size 998883
2015-12-03 12:26:30 CreateNewBlock(): total size 998978
2015-12-03 12:26:36 CreateNewBlock(): total size 998837
2015-12-03 12:26:42 CreateNewBlock(): total size 998842
2015-12-03 12:26:48 CreateNewBlock(): total size 998971
2015-12-03 12:26:54 CreateNewBlock(): total size 998913
2015-12-03 12:26:58 keypool reserve 3
2015-12-03 12:26:58 keypool return 3
2015-12-03 12:27:00 CreateNewBlock(): total size 998914
The fact that it's trying to create a new block every 6 seconds seems a bit odd, but looking at the log shows that is pretty consistently happening, even when things are running smoothly. My only recourse is to kill the process and restart it. Doing so makes everything run smoothly once again. Once restarted, I can see typically "normal" things in the log: 015-12-03 13:00:45 CreateNewBlock(): total size 696619
2015-12-03 13:00:48 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-12-03 13:00:48 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2015-12-03 13:00:52 CreateNewBlock(): total size 701939
2015-12-03 13:00:53 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2015-12-03 13:00:56 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2015-12-03 13:00:58 CreateNewBlock(): total size 707323
2015-12-03 13:00:59 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2015-12-03 13:01:03 CreateNewBlock(): total size 719860
By the way, I'm running 0.11.2 compiled and built from source on Ubuntu 15.10. Pool is running MPOS/NOMP. Processes are running on a 4 core box with 8G RAM. Looking at CPU usage, bitcoind is about 150% or more when it is unresponsive. Typically it ranges anywhere from 30% to 80%. I'm wondering if having a max block size of 1M is causing problems. If you look at the two log snippets I included above, when it was completely unresponsive, all it was doing was trying to create new blocks of max size (or very close to it). When things are running smoothly, the blocks its trying to create are considerably smaller. Thanks in advance for any suggestions. |
|
|
|
All, Very recently I have run into an issue with my bitcoin daemon. I am wondering if it might have to do with the pool software I'm running on top of it, and will likely ask this same question if I can find a forum thread for the pool . Here's what I notice: 1) I start up the bitcoin daemon process and all is happy. 2) After about 24 hours, the process becomes completely unresponsive. Typing: Or any other command just hangs without returning. 3) This causes all kinds of havoc on my pool. Website runs exceptionally slow. I get bombarded with mail from the cron jobs saying they're already running. Things like that. When I look at my debug.log, all I see is it trying to create new blocks: 2015-12-03 12:26:06 CreateNewBlock(): total size 998979
2015-12-03 12:26:12 CreateNewBlock(): total size 998945
2015-12-03 12:26:18 CreateNewBlock(): total size 998993
2015-12-03 12:26:24 CreateNewBlock(): total size 998883
2015-12-03 12:26:30 CreateNewBlock(): total size 998978
2015-12-03 12:26:36 CreateNewBlock(): total size 998837
2015-12-03 12:26:42 CreateNewBlock(): total size 998842
2015-12-03 12:26:48 CreateNewBlock(): total size 998971
2015-12-03 12:26:54 CreateNewBlock(): total size 998913
2015-12-03 12:26:58 keypool reserve 3
2015-12-03 12:26:58 keypool return 3
2015-12-03 12:27:00 CreateNewBlock(): total size 998914
The fact that it's trying to create a new block every 6 seconds seems a bit odd, but looking at the log shows that is pretty consistently happening, even when things are running smoothly. My only recourse is to kill the process and restart it. Doing so makes everything run smoothly once again. Once restarted, I can see typically "normal" things in the log: 015-12-03 13:00:45 CreateNewBlock(): total size 696619
2015-12-03 13:00:48 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-12-03 13:00:48 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2015-12-03 13:00:52 CreateNewBlock(): total size 701939
2015-12-03 13:00:53 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2015-12-03 13:00:56 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2015-12-03 13:00:58 CreateNewBlock(): total size 707323
2015-12-03 13:00:59 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter
2015-12-03 13:01:03 CreateNewBlock(): total size 719860
By the way, I'm running 0.11.2 compiled and built from source on Ubuntu 15.10. Pool is running MPOS/NOMP. Processes are running on a 4 core box with 8G RAM. Looking at CPU usage, bitcoind is about 150% or more when it is unresponsive. Typically it ranges anywhere from 30% to 80%. I'm wondering if having a max block size of 1M is causing problems. If you look at the two log snippets I included above, when it was completely unresponsive, all it was doing was trying to create new blocks of max size (or very close to it). When things are running smoothly, the blocks its trying to create are considerably smaller. Thanks in advance for any suggestions. |
|
|
|
|
Show Posts
