Bitcoin Forum
April 22, 2018, 05:32:31 PM *
News: Latest stable version of Bitcoin Core: 0.16.0  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 [6]  All
  Print  
Author Topic: Bitparking PPCoin Pool [closed]  (Read 22706 times)
roy7
Sr. Member
****
Offline Offline

Activity: 434
Merit: 250


View Profile
April 06, 2013, 01:28:10 PM
 #101

protip: open a second instance of cgminer for BTC.. run BTC at intensity 3 and PPC at intensity 11... when PPC is up you'll only get a few mhash devoted to BTC.. but when ppc is down you'lll get 85% hash rate on BTC

Great idea, thank you. Smiley What I ended up doing was starting up a local ppcoin server and putting into cgminer as a second pool in load balance mode. So in theory I'll solo mine if coinotron is down. In theory...

Speaking of which, can I have pools for multiple SHA-256 coins in cgminer at the same time? I'm guessing the longpool/stratum notifications would mess that up. Like say, if I added a PPC and a TRC pool, if it'd individually work on the work units assigned without any weird issues.

RoyalMiningCo: Pools retired. Was fun!
1524418351
Hero Member
*
Offline Offline

Posts: 1524418351

View Profile Personal Message (Offline)

Ignore
1524418351
Reply with quote  #2

1524418351
Report to moderator
1524418351
Hero Member
*
Offline Offline

Posts: 1524418351

View Profile Personal Message (Offline)

Ignore
1524418351
Reply with quote  #2

1524418351
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
roy7
Sr. Member
****
Offline Offline

Activity: 434
Merit: 250


View Profile
April 06, 2013, 01:45:22 PM
 #102

doublec, did you roll your own front end/back end or were you using existing packages? May I ask which one(s)?

Thanks.

Edit: If you enjoy running the pool and doing the front end part of things, you might consider this payment system:

http://eligius.st/wiki/index.php/Capped_PPS_with_Recent_Backpay

Zero out of pocket/risk to you.

RoyalMiningCo: Pools retired. Was fun!
doublec
Legendary
*
Offline Offline

Activity: 1078
Merit: 1000


View Profile
April 06, 2013, 11:25:18 PM
 #103

doublec, did you roll your own front end/back end or were you using existing packages? May I ask which one(s)?
It is my own front end and back end. The back end is written in the ATS programming language and the front end in the Ur/Web programming language. Thanks for the payment point I'll take a look.
roy7
Sr. Member
****
Offline Offline

Activity: 434
Merit: 250


View Profile
April 07, 2013, 01:44:47 AM
 #104

Man, so many new languages I've never even heard of, lol. I'm obsolete. Everything I ever did was in C, C++, PHP, or Perl. Touch of Java. Never learned any Python.

I like how your system doesn't use a password, just links to a hash you can't change. The Eligius guys take it a step further and your payment hash is your username, no pw or accounts.

RoyalMiningCo: Pools retired. Was fun!
doublec
Legendary
*
Offline Offline

Activity: 1078
Merit: 1000


View Profile
April 07, 2013, 01:51:52 AM
 #105

I like how your system doesn't use a password, just links to a hash you can't change. The Eligius guys take it a step further and your payment hash is your username, no pw or accounts.
I'm a bit of a programming language nut. The pool was originally written because I wanted to try out the language runtimes and see how well they worked.

I used to do what Eligius does too, back when 'mmpool' wasn't merge mining but was a namecoin pool. When I switched to merge mining I had to somehow associate multiple addresses with a user. When I did the ppcoin pool I used the same pool code after I'd done the user modification thinking that sometime in the future I'd enable merge mining with ppcoin as the primary chain but I couldn't get that working.
Pages: « 1 2 3 4 5 [6]  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!