Bitcoin Forum
December 11, 2016, 04:08:35 AM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 [636] 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2035483 times)
yslyung
Legendary
*
Offline Offline

Activity: 1064


Mine Mine Mine


View Profile
June 06, 2015, 02:28:06 PM
 #12701

Yep, double checked all passwords & ports - although there's no need to forward the rpc ports as they are only used locally on 127.0.0.1 for merge mining. None of my rpc ports are forwarded on any other wallets & they work fine - it's only the UNO wallet that seems to be having issues. I'm compiling the QT wallet now.....

EDIT: QT compiled & running, I'll keep an eye on it for payments. In the meantime, if anyone else using the daemon hasn't received any payments - please post here, thanks.

thx for headsup again ... i'm on windows as i'm a linux noob .... so far so good for me ... 1 block per hour sometimes more ...



keep us updated
1481429315
Hero Member
*
Offline Offline

Posts: 1481429315

View Profile Personal Message (Offline)

Ignore
1481429315
Reply with quote  #2

1481429315
Report to moderator
1481429315
Hero Member
*
Offline Offline

Posts: 1481429315

View Profile Personal Message (Offline)

Ignore
1481429315
Reply with quote  #2

1481429315
Report to moderator
1481429315
Hero Member
*
Offline Offline

Posts: 1481429315

View Profile Personal Message (Offline)

Ignore
1481429315
Reply with quote  #2

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

Activity: 1064


Mine Mine Mine


View Profile
June 06, 2015, 02:30:28 PM
 #12702

btw windpath ... how do i add this to my node ?



thx ...

and also i can't seem to add or show node efficiency ...

feel a block is coming soon  Cool
windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
June 06, 2015, 03:02:35 PM
 #12703

btw windpath ... how do i add this to my node ?



thx ...

and also i can't seem to add or show node efficiency ...

feel a block is coming soon  Cool

I poll bitcoin core and p2pool nodes, store it in a DB, and calculate it....

yslyung
Legendary
*
Offline Offline

Activity: 1064


Mine Mine Mine


View Profile
June 06, 2015, 03:11:48 PM
 #12704

btw windpath ... how do i add this to my node ?



thx ...

and also i can't seem to add or show node efficiency ...

feel a block is coming soon  Cool

I poll bitcoin core and p2pool nodes, store it in a DB, and calculate it....


any guide ? want to add that to my node if possible.

and wut did i said few mins earlier a block ? yeah !!!

BITCOIN BLOCK FOUND by 1GEvGnXQbALcjvw6Ed4Xek6f3wyCgXQRfb! https://blockchain.info/block/000000000000000007eff6dfc2ed5478164b2627917b96d494f800175b53abcc
windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
June 06, 2015, 03:21:11 PM
 #12705


any guide ? want to add that to my node if possible.

and wut did i said few mins earlier a block ? yeah !!!

BITCOIN BLOCK FOUND by 1GEvGnXQbALcjvw6Ed4Xek6f3wyCgXQRfb! https://blockchain.info/block/000000000000000007eff6dfc2ed5478164b2627917b96d494f800175b53abcc

Unfortunately not, I'll spend some time this afternoon and describe the setup, it's not overly complex...

yslyung
Legendary
*
Offline Offline

Activity: 1064


Mine Mine Mine


View Profile
June 06, 2015, 03:39:53 PM
 #12706


any guide ? want to add that to my node if possible.

and wut did i said few mins earlier a block ? yeah !!!

BITCOIN BLOCK FOUND by 1GEvGnXQbALcjvw6Ed4Xek6f3wyCgXQRfb! https://blockchain.info/block/000000000000000007eff6dfc2ed5478164b2627917b96d494f800175b53abcc

Unfortunately not, I'll spend some time this afternoon and describe the setup, it's not overly complex...

thx very much, looking forward to it !
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266



View Profile
June 06, 2015, 05:42:22 PM
 #12707

Yep, double checked all passwords & ports - although there's no need to forward the rpc ports as they are only used locally on 127.0.0.1 for merge mining. None of my rpc ports are forwarded on any other wallets & they work fine - it's only the UNO wallet that seems to be having issues. I'm compiling the QT wallet now.....

EDIT: QT compiled & running, I'll keep an eye on it for payments. In the meantime, if anyone else using the daemon hasn't received any payments - please post here, thanks.

Update: Well, I just received my first payment using the QT wallet, so now I know for sure there's no problem with my settings. I'm gonna switch back to using the daemon to see if the payments stop again.....
windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
June 06, 2015, 07:51:00 PM
 #12708

This will be a high level explanation of how my node works, it's not an exhaustive tutorial...

So here goes...

I built this over a year ago (when p2pool.info died) in a bit if a rush, and there are certainly things I would change today to make it more efficient....

It runs an an AWS LAMP server, and pulls data from both bitcoind and p2pool. Everything is gathered and stored locally on the server, there are no external API's.

The first thing you will need to do (in addition to the existing p2pool setup) is add
Code:
txindex=1
to your bitcoin.conf, restart it, and force a re-scan. This will force a lengthy re-index, and makes the data of all transactions available from the bitcoin API. (note: if you do this on an operating node be prepared for some extended downtime during the re-index).

Next I set up the DB (MySQL), again it was quick and dirty, and this DB is specifically focused on p2pool:

Code:
-- Host: localhost:3306
-- Generation Time: Jun 06, 2015 at 11:56 AM
-- Server version: 5.5.36
-- PHP Version: 5.4.28

SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
SET time_zone = "+00:00";

--
-- Database: `p2pool`
--

-- --------------------------------------------------------

--
-- Table structure for table `block_payout`
--

CREATE TABLE IF NOT EXISTS `block_payout` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `block_id` int(11) NOT NULL,
  `address` varchar(34) NOT NULL,
  `ammount` decimal(10,8) NOT NULL,
  PRIMARY KEY (`id`),
  KEY `address` (`address`),
  KEY `block_id` (`block_id`)
) ENGINE=InnoDB  DEFAULT CHARSET=utf8 AUTO_INCREMENT=587605 ;

-- --------------------------------------------------------

--
-- Table structure for table `found_blocks`
--

CREATE TABLE IF NOT EXISTS `found_blocks` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `share` varchar(15) NOT NULL,
  `time` datetime NOT NULL,
  `hash` varchar(64) NOT NULL,
  `height` int(8) DEFAULT NULL,
  `orphan` tinyint(1) NOT NULL DEFAULT '0',
  `luck` decimal(8,2) DEFAULT NULL,
  PRIMARY KEY (`id`),
  UNIQUE KEY `height` (`height`)
) ENGINE=InnoDB  DEFAULT CHARSET=utf8 AUTO_INCREMENT=2555 ;

-- --------------------------------------------------------

--
-- Table structure for table `found_shares`
--

CREATE TABLE IF NOT EXISTS `found_shares` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `address` varchar(34) NOT NULL,
  `share` varchar(15) NOT NULL,
  `time` datetime NOT NULL,
  `doa` tinyint(1) NOT NULL DEFAULT '0',
  PRIMARY KEY (`id`)
) ENGINE=InnoDB  DEFAULT CHARSET=utf8 AUTO_INCREMENT=17889 ;

-- --------------------------------------------------------

--
-- Table structure for table `pool_stats`
--

CREATE TABLE IF NOT EXISTS `pool_stats` (
  `id` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `global_rate` varchar(72) NOT NULL,
  `global_nonstale_rate` varchar(20) NOT NULL,
  `diff` varchar(20) NOT NULL,
  `miners` int(7) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

So some quick explanation of the DB structure:

3 things not to overlook: charset = UTF8,  SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO", and SET time_zone = "+00:00".

The first 2 are self explanatory, the timezone must be set to UTC as that is what bitcoin uses globally in the block chain, was going to add a way for miners to set their local timezone in the views, but never got around to it.

Table block_payout contains the payout data by public address for every block P2Pool has found, it facilitates displaying total as well as per block payouts for miners (example). Originally I wrote a script to go over all the historical blocks and let it run, now it pulls them as we find blocks.

Table found_blocks has every block P2Pool has found, the p2pool share that found it, whether it was orphaned, and its luck. Again, added historical ones from a few sources provided by someone probably 100 pages back in this thread, new ones are added as they are found.

Table found_shares is specific to my node (I hated loosing all the shares on a re-start), so if you have ever found a share mining on my node, it's in there (example on miner shares tab).

Table pool_stats stores the bitcoin difficulty from bitcoind and pool hashrate from p2pool every minute, this is how luck is calculated - and why I could not calculate luck for historical blocks when I built it (no one had historical pool hashrate data).

The rest of the back end is basically 2 cron files, 1 that polls p2pool's log file and another that polls bitcoind. Both run once a minute, pull new data, check for orphans, calculate luck for new blocks, and store it in the DB.

The cron also renames the p2pool log file and saves it as a date stamped archive every 10MB, this greatly reduces memory usage when reading the log into memory.

Originally was adding blocks by searching the log for "GOT BLOCK", however this missed any stale shares that happened to find a block (and there are quite a few), so now I monitor a p2pool miner payout address for generation transactions as well (look out for donations!).

The front end is an ugly (code wise) mashup of p2pool's JS front ends and PHP running on the server. I used Bootstrap, a lot of cut and paste hacking, and some PHP to query the DB, calculate everything for the view, and display it.

In a nut shell, that's it.

All of this was done pretty openly in this thread with a lot of help from the community, a lot of the code logic is buried in this thread if you want to take a look at it.

If you give it a try and have any specific questions I'd be happy to try and help out.


yslyung
Legendary
*
Offline Offline

Activity: 1064


Mine Mine Mine


View Profile
June 06, 2015, 08:46:42 PM
 #12709

This will be a high level explanation of how my node works, it's not an exhaustive tutorial...

So here goes...

I built this over a year ago (when p2pool.info died) in a bit if a rush, and there are certainly things I would change today to make it more efficient....

It runs an an AWS LAMP server, and pulls data from both bitcoind and p2pool. Everything is gathered and stored locally on the server, there are no external API's.

The first thing you will need to do (in addition to the existing p2pool setup) is add
Code:
txindex=1
to your bitcoin.conf, restart it, and force a re-scan. This will force a lengthy re-index, and makes the data of all transactions available from the bitcoin API. (note: if you do this on an operating node be prepared for some extended downtime during the re-index).

Next I set up the DB (MySQL), again it was quick and dirty, and this DB is specifically focused on p2pool:

Code:
-- Host: localhost:3306
-- Generation Time: Jun 06, 2015 at 11:56 AM
-- Server version: 5.5.36
-- PHP Version: 5.4.28

SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
SET time_zone = "+00:00";

--
-- Database: `p2pool`
--

-- --------------------------------------------------------

--
-- Table structure for table `block_payout`
--

CREATE TABLE IF NOT EXISTS `block_payout` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `block_id` int(11) NOT NULL,
  `address` varchar(34) NOT NULL,
  `ammount` decimal(10,8) NOT NULL,
  PRIMARY KEY (`id`),
  KEY `address` (`address`),
  KEY `block_id` (`block_id`)
) ENGINE=InnoDB  DEFAULT CHARSET=utf8 AUTO_INCREMENT=587605 ;

-- --------------------------------------------------------

--
-- Table structure for table `found_blocks`
--

CREATE TABLE IF NOT EXISTS `found_blocks` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `share` varchar(15) NOT NULL,
  `time` datetime NOT NULL,
  `hash` varchar(64) NOT NULL,
  `height` int(8) DEFAULT NULL,
  `orphan` tinyint(1) NOT NULL DEFAULT '0',
  `luck` decimal(8,2) DEFAULT NULL,
  PRIMARY KEY (`id`),
  UNIQUE KEY `height` (`height`)
) ENGINE=InnoDB  DEFAULT CHARSET=utf8 AUTO_INCREMENT=2555 ;

-- --------------------------------------------------------

--
-- Table structure for table `found_shares`
--

CREATE TABLE IF NOT EXISTS `found_shares` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `address` varchar(34) NOT NULL,
  `share` varchar(15) NOT NULL,
  `time` datetime NOT NULL,
  `doa` tinyint(1) NOT NULL DEFAULT '0',
  PRIMARY KEY (`id`)
) ENGINE=InnoDB  DEFAULT CHARSET=utf8 AUTO_INCREMENT=17889 ;

-- --------------------------------------------------------

--
-- Table structure for table `pool_stats`
--

CREATE TABLE IF NOT EXISTS `pool_stats` (
  `id` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `global_rate` varchar(72) NOT NULL,
  `global_nonstale_rate` varchar(20) NOT NULL,
  `diff` varchar(20) NOT NULL,
  `miners` int(7) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

So some quick explanation of the DB structure:

3 things not to overlook: charset = UTF8,  SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO", and SET time_zone = "+00:00".

The first 2 are self explanatory, the timezone must be set to UTC as that is what bitcoin uses globally in the block chain, was going to add a way for miners to set their local timezone in the views, but never got around to it.

Table block_payout contains the payout data by public address for every block P2Pool has found, it facilitates displaying total as well as per block payouts for miners (example). Originally I wrote a script to go over all the historical blocks and let it run, now it pulls them as we find blocks.

Table found_blocks has every block P2Pool has found, the p2pool share that found it, whether it was orphaned, and its luck. Again, added historical ones from a few sources provided by someone probably 100 pages back in this thread, new ones are added as they are found.

Table found_shares is specific to my node (I hated loosing all the shares on a re-start), so if you have ever found a share mining on my node, it's in there (example on miner shares tab).

Table pool_stats stores the bitcoin difficulty from bitcoind and pool hashrate from p2pool every minute, this is how luck is calculated - and why I could not calculate luck for historical blocks when I built it (no one had historical pool hashrate data).

The rest of the back end is basically 2 cron files, 1 that polls p2pool's log file and another that polls bitcoind. Both run once a minute, pull new data, check for orphans, calculate luck for new blocks, and store it in the DB.

The cron also renames the p2pool log file and saves it as a date stamped archive every 10MB, this greatly reduces memory usage when reading the log into memory.

Originally was adding blocks by searching the log for "GOT BLOCK", however this missed any stale shares that happened to find a block (and there are quite a few), so now I monitor a p2pool miner payout address for generation transactions as well (look out for donations!).

The front end is an ugly (code wise) mashup of p2pool's JS front ends and PHP running on the server. I used Bootstrap, a lot of cut and paste hacking, and some PHP to query the DB, calculate everything for the view, and display it.

In a nut shell, that's it.

All of this was done pretty openly in this thread with a lot of help from the community, a lot of the code logic is buried in this thread if you want to take a look at it.

If you give it a try and have any specific questions I'd be happy to try and help out.



prolly too long to reply here. u got pm & hopefully we can work from there.

whereistheblock ? i've bumped pool hashrate up earlier, i think it went over 3+ ph.

any other coins worth to merge ?
Geremia
Sr. Member
****
Offline Offline

Activity: 445


View Profile WWW
June 06, 2015, 09:48:02 PM
 #12710

Code:
-- Host: localhost:3306
-- Generation Time: Jun 06, 2015 at 11:56 AM
-- Server version: 5.5.36
-- PHP Version: 5.4.28

SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
SET time_zone = "+00:00";

--
-- Database: `p2pool`
--

-- --------------------------------------------------------

--
-- Table structure for table `block_payout`
--

CREATE TABLE IF NOT EXISTS `block_payout` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `block_id` int(11) NOT NULL,
  `address` varchar(34) NOT NULL,
  `ammount` decimal(10,8) NOT NULL,
  PRIMARY KEY (`id`),
  KEY `address` (`address`),
  KEY `block_id` (`block_id`)
) ENGINE=InnoDB  DEFAULT CHARSET=utf8 AUTO_INCREMENT=587605 ;

-- --------------------------------------------------------

--
-- Table structure for table `found_blocks`
--

CREATE TABLE IF NOT EXISTS `found_blocks` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `share` varchar(15) NOT NULL,
  `time` datetime NOT NULL,
  `hash` varchar(64) NOT NULL,
  `height` int(8) DEFAULT NULL,
  `orphan` tinyint(1) NOT NULL DEFAULT '0',
  `luck` decimal(8,2) DEFAULT NULL,
  PRIMARY KEY (`id`),
  UNIQUE KEY `height` (`height`)
) ENGINE=InnoDB  DEFAULT CHARSET=utf8 AUTO_INCREMENT=2555 ;

-- --------------------------------------------------------

--
-- Table structure for table `found_shares`
--

CREATE TABLE IF NOT EXISTS `found_shares` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `address` varchar(34) NOT NULL,
  `share` varchar(15) NOT NULL,
  `time` datetime NOT NULL,
  `doa` tinyint(1) NOT NULL DEFAULT '0',
  PRIMARY KEY (`id`)
) ENGINE=InnoDB  DEFAULT CHARSET=utf8 AUTO_INCREMENT=17889 ;

-- --------------------------------------------------------

--
-- Table structure for table `pool_stats`
--

CREATE TABLE IF NOT EXISTS `pool_stats` (
  `id` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `global_rate` varchar(72) NOT NULL,
  `global_nonstale_rate` varchar(20) NOT NULL,
  `diff` varchar(20) NOT NULL,
  `miners` int(7) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
Do you have all this and supporting code up on GitHub or somewhere else? If not you should put it all up.

BTC tip jar | my BTC wiki, BTC StackExchange, Twister posts, & Keybase pages | Tox ID: 65C3E8810738AD9D175234808FCB317A1103632903436203D45411AE97C03F547D390A76B3CF
Join Coinbase. | The best, free book on Bitcoin: Mastering Bitcoin
Nos cum prole pia benedicat Virgo Maria.
kano
Legendary
*
Online Online

Activity: 1932


Linux since 1997 RedHat 4


View Profile
June 07, 2015, 12:30:36 AM
 #12711

...
Table pool_stats stores the bitcoin difficulty from bitcoind and pool hashrate from p2pool every minute, this is how luck is calculated - and why I could not calculate luck for historical blocks when I built it (no one had historical pool hashrate data).
...
How do you calculate luck?

Pool: https://kano.is BTC: 1KanoiBupPiZfkwqB7rfLXAzPnoTshAVmb
CKPool and CGMiner developer, IRC FreeNode #ckpool and #cgminer kanoi
Help keep Bitcoin secure by mining on pools with Stratum, the best protocol to mine Bitcoins with ASIC hardware
windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
June 07, 2015, 04:22:39 AM
 #12712

...
Table pool_stats stores the bitcoin difficulty from bitcoind and pool hashrate from p2pool every minute, this is how luck is calculated - and why I could not calculate luck for historical blocks when I built it (no one had historical pool hashrate data).
...
How do you calculate luck?

Basically after a lot of discussion, we ended up with pretty close to what is described here:

https://bitcointalk.org/index.php?topic=18313.msg7373650#msg7373650

I dug around to find it, the discussion started when p2pool.info went offline almost a year ago (The post is from June 18, 2014).

Edit: I know our stats look crazy high right now, in fact just found another block at 222.82%, but we are on a nice streak.... Take a look at the times between the last 10 blocks we have found, all except 1 much better then expected. We have paid our dues with the bad times recently, looks like it's turned around Wink


yslyung
Legendary
*
Offline Offline

Activity: 1064


Mine Mine Mine


View Profile
June 07, 2015, 05:31:04 AM
 #12713

...
Table pool_stats stores the bitcoin difficulty from bitcoind and pool hashrate from p2pool every minute, this is how luck is calculated - and why I could not calculate luck for historical blocks when I built it (no one had historical pool hashrate data).
...
How do you calculate luck?

thats wut i wanna add to my node .... & been trying to figure that out.

math looks right to me windpath ....

now a how to for a noob .. thx Wink
kano
Legendary
*
Online Online

Activity: 1932


Linux since 1997 RedHat 4


View Profile
June 07, 2015, 08:20:53 AM
 #12714

...
Table pool_stats stores the bitcoin difficulty from bitcoind and pool hashrate from p2pool every minute, this is how luck is calculated - and why I could not calculate luck for historical blocks when I built it (no one had historical pool hashrate data).
...
How do you calculate luck?

Basically after a lot of discussion, we ended up with pretty close to what is described here:

https://bitcointalk.org/index.php?topic=18313.msg7373650#msg7373650

I dug around to find it, the discussion started when p2pool.info went offline almost a year ago (The post is from June 18, 2014).

Edit: I know our stats look crazy high right now, in fact just found another block at 222.82%, but we are on a nice streak.... Take a look at the times between the last 10 blocks we have found, all except 1 much better then expected. We have paid our dues with the bad times recently, looks like it's turned around Wink

Well, those calculations are based on other calculations that have their own accuracy issues.

The correct and direct definition of luck (where >100% is good luck and less than 100% is bad luck) is simply DifficultyExpected/DifficultySubmitted

Those are two number that you should have - the other numbers you use are calculated from them.
The pool hash rate (as you may well have seen) is, like any pool, only an estimate, and not very accurate either.

My real question, though, is do you count blocks that are not part of the share chain?
If you do, then you must also include the hashes used to find those blocks.
Adding a block into your luck figure without including the hashes expended to find that block is, obviously, incorrect.

Pool: https://kano.is BTC: 1KanoiBupPiZfkwqB7rfLXAzPnoTshAVmb
CKPool and CGMiner developer, IRC FreeNode #ckpool and #cgminer kanoi
Help keep Bitcoin secure by mining on pools with Stratum, the best protocol to mine Bitcoins with ASIC hardware
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266



View Profile
June 07, 2015, 10:22:48 AM
 #12715

Hi all, just a heads up.

I'm using Xubuntu 14.04 64bit & have found that when using the Unobtanium daemon for merge mining I'm not receiving any payments, but if I use the QT wallet - payments are received in the normal way. I've recompiled the daemon a few times with no errors & I get no errors in my p2pool logs either - the payments just don't appear in my wallet, yet as soon as I use the QT wallet, payments resume as normal.

I will report the issue on the Unobtanium thread, but I recommend that anyone using the Unobtanium daemon on NIX to check that they are receiving their merge mined payments & if not, to switch to the QT wallet instead. Unfortunately it seems that previous lost payments are just that - lost.

I'm not sure if this issue is the same for other OS's, but I'd check anyway, just to be sure.
Meuh6879
Legendary
*
Offline Offline

Activity: 1092



View Profile
June 07, 2015, 11:25:11 AM
 #12716



this is not a p2pool direct network payment.

this screen is a pool (perhaps with a NODE connected to a P2Pool).
this POOL pay regulary.




on REAL P2Pool, you are pay when block is found only ... 1 block find with P2Pool = 1 transaction.
history of BLOCK FOUND By P2Pool is here : http://minefast.coincadence.com/p2pool-stats.php

on 6/6/15 ... only 2 blocks are found (02h17 and 15h07).

French ... but not so much   ---===---   P2P ... it's people at the end   ---===---   P2Pool (10,9 GH/s).
Comment miner des bitcoins ? Un tutoriel est là : https://bitcointalk.org/index.php?topic=1114415.0
Bitcoin change everything ... an explain of this fact : https://www.youtube.com/watch?v=joITmEr4SjY
yslyung
Legendary
*
Offline Offline

Activity: 1064


Mine Mine Mine


View Profile
June 07, 2015, 11:33:19 AM
 #12717



this is not a p2pool direct network payment.

this screen is a pool (perhaps with a NODE connected to a P2Pool).
this POOL pay regulary.




on REAL P2Pool, you are pay when block is found only ... 1 block find with P2Pool = 1 transaction.
history of BLOCK FOUND By P2Pool is here : http://minefast.coincadence.com/p2pool-stats.php

on 6/6/15 ... only 2 blocks are found (02h17 and 15h07).

Huh what are you trying to say ?

we're talking about merged mining uno with p2pool Huh

lost here...maybe you wanna elaborate ?

qt works but not daemon
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266



View Profile
June 07, 2015, 11:45:37 AM
 #12718

qt works but not daemon

Exactly. At least on my distro & local node.
chalkboard17
Sr. Member
****
Offline Offline

Activity: 271


View Profile
June 07, 2015, 12:38:37 PM
 #12719

I have searched everywhere but haven't found an answer to this. Appreciate if someone could help me.
I have been trying to mine on p2pool, but I get much lower hashrate than usual. I normally get 1380gh/s on eligius and ghash. On p2pool I always get ~1230gh/s.
I already tried mining on my node and other people's nodes and result is still the same.
I am using antminer s5 interface and pointing miner to the ip.

I cannot use my IP to mine, don't know why. I use its network IP and seems to work fine (at lower hashrate). Is that ok?

Can someone take any fees or possibly steal hashrate from me if I use p2pool?

Can I merge mine on all merged mining possible coins? At the same time? On windows?
Thanks

p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266



View Profile
June 07, 2015, 01:08:42 PM
 #12720

I am using antminer s5 interface and pointing miner to the ip.

Use kano's cgminer replacement - bitmain's cgminer is borked for p2pool:

SSH into your S5 as root then copy/paste:

Code:
cd /tmp
wget http://ck.kolivas.org/apps/cgminer/antminer/s5/4.9.0-150105/cgminer
chmod +x cgminer
mv /usr/bin/cgminer /usr/bin/cgminer.bak
cp cgminer /usr/bin
/etc/init.d/cgminer.sh restart

Then press enter.

I cannot use my IP to mine, don't know why. I use its network IP and seems to work fine (at lower hashrate). Is that ok?

You should be able to use your LAN IP - is your node on your network or on your PC?

Can someone take any fees or possibly steal hashrate from me if I use p2pool?

You can see if a node is charging you a fee by adding "/fee" at the end of the node address. It's impossible for anyone to steal your hash if you use your own node.

Can I merge mine on all merged mining possible coins? At the same time? On windows?

Yes.
Pages: « 1 ... 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 [636] 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 ... 744 »
  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!