Bitcoin Forum
December 09, 2016, 05:59:00 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 ... 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 [396] 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2033097 times)
Tegija
Member
**
Offline Offline

Activity: 98

Just Fun!


View Profile
March 03, 2014, 07:39:53 PM
 #7901

if I ran my miner over night will I see the results are back on track?

depending of miner hash rate you will see full results first in 3 days. if block is already longer "in work" you will not get/reach in first block full payout. P2pool is hop-proof pool.
in some alcoin p2pools you can see results earlier depending of block frequency of this coin and several other factors.

Enjoy your life!
1481263140
Hero Member
*
Offline Offline

Posts: 1481263140

View Profile Personal Message (Offline)

Ignore
1481263140
Reply with quote  #2

1481263140
Report to moderator
1481263140
Hero Member
*
Offline Offline

Posts: 1481263140

View Profile Personal Message (Offline)

Ignore
1481263140
Reply with quote  #2

1481263140
Report to moderator
1481263140
Hero Member
*
Offline Offline

Posts: 1481263140

View Profile Personal Message (Offline)

Ignore
1481263140
Reply with quote  #2

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

Posts: 1481263140

View Profile Personal Message (Offline)

Ignore
1481263140
Reply with quote  #2

1481263140
Report to moderator
1481263140
Hero Member
*
Offline Offline

Posts: 1481263140

View Profile Personal Message (Offline)

Ignore
1481263140
Reply with quote  #2

1481263140
Report to moderator
smooth
Legendary
*
Offline Offline

Activity: 1246



View Profile
March 04, 2014, 02:05:43 AM
 #7902

Anybody have any ideas how to increase the hash rate? We are sinking to a smaller and smaller percentage of the network, and round times are growing. We're having 4 day rounds now, a few more difficulty jumps and it may be weeks or longer.

Something must be done.


forrestv
Hero Member
*****
Offline Offline

Activity: 510


View Profile
March 04, 2014, 05:10:16 AM
 #7903

Anybody have any ideas how to increase the hash rate? We are sinking to a smaller and smaller percentage of the network, and round times are growing. We're having 4 day rounds now, a few more difficulty jumps and it may be weeks or longer.

Something must be done.

I'm working on a revamp of P2Pool that will give us a few key features that will help:

  • Running a "lite" P2Pool instance - one without a full Bitcoin node - will be possible without losing any of the promises P2Pool makes about its contribution to Bitcoin network health
  • P2Pool will have a non-linear sharechain so that we can have shares more often than 30 seconds, allowing small miners to use P2Pool

Both of these make P2Pool easier to use; the eventual goal is being able to run P2Pool on the same hardware miners use, such as a Raspberry Pi, though that would likely require a laborious rewrite in C++ or another compiled language.

My current progress on this: I have a piece of software talking to bitcoind and augmenting blocks with UTXO merkle branches, feeding that to another piece of lightweight software that can trustlessly verify the blockchain, while holding O(1) state. I have a good idea about how the non-linear sharechain will work, but implementing that hasn't started yet.

1J1zegkNSbwX4smvTdoHSanUfwvXFeuV23
smooth
Legendary
*
Offline Offline

Activity: 1246



View Profile
March 04, 2014, 05:13:32 AM
 #7904

Both of these make P2Pool easier to use; the eventual goal is being able to run P2Pool on the same hardware miners use, such as a Raspberry Pi, though that would likely require a laborious rewrite in C++ or another compiled language.

Pypy works fine with the current p2pool code, have you tried that? Not quite sure about a RPi, but it should help on a lot of small hosts.

Re: The rest.

Looking forward to it. Good stuff.

oldbushie
Member
**
Offline Offline

Activity: 94


View Profile
March 04, 2014, 06:46:08 AM
 #7905

Those would definitely entice a lot more people to give it a try. Good luck!! I have a dream that one day we will reach 500 TH/s.

smooth
Legendary
*
Offline Offline

Activity: 1246



View Profile
March 04, 2014, 07:14:44 AM
 #7906

Those would definitely entice a lot more people to give it a try. Good luck!! I have a dream that one day we will reach 500 TH/s.

Too low. In six months 500 TH might well be just one block a week. This is do or die time for p2pool. If adoption doesn't pick up soon, we are facing a death spiral and the need for a full relaunch (which might be okay)



smoothrunnings
Hero Member
*****
Offline Offline

Activity: 546


View Profile
March 04, 2014, 11:45:19 AM
 #7907

Is there anyway to disable the wallet function in P2Pool and have it instead forward the percentage of shares the note is to receive to a different wallet?

I have hit a stumbling block; over a week a go I initiated a transfer of over 1/2 a bitcoin and Bitcoin-QT told me I need to account for 0.0004 of the fee, so I did that and ever since the transfer has been in limbo, it looks like bitcoin-qt gave me the wrong fee to account for it if I understand the blockchain correctly.

https://blockchain.info/tx-index/7bbbc7b5fac8c2973e9c62a17cead946b9cf1832aac47479799ce566fafabcc1

Also I need to figure out if can fix this issue or have I lost those coins? Sad

Thanks,

jedimstr
Hero Member
*****
Offline Offline

Activity: 784



View Profile
March 04, 2014, 11:48:04 AM
 #7908

Is there anyway to disable the wallet function in P2Pool and have it instead forward the percentage of shares the note is to receive to a different wallet?

I have hit a stumbling block; over a week a go I initiated a transfer of over 1/2 a bitcoin and Bitcoin-QT told me I need to account for 0.0004 of the fee, so I did that and ever since the transfer has been in limbo, it looks like bitcoin-qt gave me the wrong fee to account for it if I understand the blockchain correctly.

https://blockchain.info/tx-index/7bbbc7b5fac8c2973e9c62a17cead946b9cf1832aac47479799ce566fafabcc1

Also I need to figure out if can fix this issue or have I lost those coins? Sad

Thanks,



-a bitcoinAddress

smoothrunnings
Hero Member
*****
Offline Offline

Activity: 546


View Profile
March 04, 2014, 11:55:43 AM
 #7909

Is there anyway to disable the wallet function in P2Pool and have it instead forward the percentage of shares the note is to receive to a different wallet?

I have hit a stumbling block; over a week a go I initiated a transfer of over 1/2 a bitcoin and Bitcoin-QT told me I need to account for 0.0004 of the fee, so I did that and ever since the transfer has been in limbo, it looks like bitcoin-qt gave me the wrong fee to account for it if I understand the blockchain correctly.

https://blockchain.info/tx-index/7bbbc7b5fac8c2973e9c62a17cead946b9cf1832aac47479799ce566fafabcc1

Also I need to figure out if can fix this issue or have I lost those coins? Sad

Thanks,



-a bitcoinAddress

do I need to add anything to the bitcoin.conf?

roy7
Sr. Member
****
Offline Offline

Activity: 434


View Profile
March 04, 2014, 02:04:43 PM
 #7910

-a bitcoinAddress
do I need to add anything to the bitcoin.conf?

Not to change the node fee payment address. -a sets that address, as jedimstr said above.

RoyalMiningCo: Pools retired. Was fun!
freebit13
Sr. Member
****
Offline Offline

Activity: 420

I got Satoshi's avatar!


View Profile
March 04, 2014, 02:05:28 PM
 #7911

Both of these make P2Pool easier to use; the eventual goal is being able to run P2Pool on the same hardware miners use, such as a Raspberry Pi, though that would likely require a laborious rewrite in C++ or another compiled language.
I think this will be a major win for p2pool, at the moment not everyone can run their own node 24hrs and it's not the same running on someone else's node, I would p2pool if I could run it on my miner.

Who knows, in the future miners could come with p2pool pre-installed, just plug in and go... that would be a win for p2pool and for Bitcoin.

Looking forward to it... thanks for all the hard work forrestv!

Decentralize EVERYTHING!
roy7
Sr. Member
****
Offline Offline

Activity: 434


View Profile
March 04, 2014, 02:22:49 PM
 #7912

I have a good idea about how the non-linear sharechain will work, but implementing that hasn't started yet.

I think that sounds awesome. The thing is the disk space for the share chain isn't that big of a deal, it uses no space really compared to the bitcoind blockchain itself. And older shares once expired don't need to be saved forever. If the sharechain can work more similar to a normal PPLNS share database at centralized pools, that'd be a big win for smaller miners. (Some way to accumulate tiny shares without paying them until they exceed the dust level might be useful, but prone to abuse if someone tries to flood the sharechain with changing addresses just to bloat it.)

One option is that all stales still get passed around like valid blocks, and payments are based on all valid + stale blocks. It isn't like bitcoin where we actually need a single chain with a record of transactions. We're only using the chain's POW so we don't have to trust clients on how much work they are reporting.

Another thought on the dust issue for small miners with tiny shares is when they are served work, that work include the prior shares value that was too low to pay. That is, a normal miner finds shares A B and C. When calculating payouts, that miner is going to be paid A+B+C until those shares start to expire off the chain. A small miner finds share A that is below dust level. They don't appear in the Payouts list. However, when serving work to miner A, they are served a share to work on that includes the diff value from share A. When share B is accepted, share A is invalidated and share B has the value of A + B's new work. If B is > DUST, it goes into Payouts list. If not, then when small miner finds C, C will include B and B is invalidated.

The thought for doing DUST this way is the tiny miner can keep building a balance without storing every tiny share on the chain, and their dust won't expire off the chain before it can grow above the payment threshold since the share's age resets on each new share found. If the miner is so small they can't find even a tiny share consistently within the PPLNS window, they they probably need to mine something else. Wink This might be more appropriate for a pay-once PPLNS structure though and not the traditional PPLNS window p2pool uses now.

(BTW, I've never looked, but p2pool needs to store the block (share chain?) difficulty when work is served so that can be logged on the share chain with the share, and payments based on the diff of work done vs diff of the block, not just the diff of the work done. Otherwise people get unfair rewards around diff changes and the pool is hoppable.)

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

Activity: 546


View Profile
March 04, 2014, 02:30:56 PM
 #7913

-a bitcoinAddress
do I need to add anything to the bitcoin.conf?

Not to change the node fee payment address. -a sets that address, as jedimstr said above.

So I don't need the disablewallet=1 in bitcoin.conf correct, only need to add the -a {address} to my P2Pool startup string?

 
jedimstr
Hero Member
*****
Offline Offline

Activity: 784



View Profile
March 04, 2014, 03:24:34 PM
 #7914

-a bitcoinAddress
do I need to add anything to the bitcoin.conf?

Not to change the node fee payment address. -a sets that address, as jedimstr said above.

So I don't need the disablewallet=1 in bitcoin.conf correct, only need to add the -a {address} to my P2Pool startup string?

 

No, you don't "need" it... but I use disablewallet=1 anyway since I only use bitcoin-qt (or bitcoin core since that's what we're calling it these days) for it's blockchain RPC and not as a wallet.

Note: disablewallet=1 only works on bitcoind/bitcoinqt OMG10 and 0.9.0 rc2 at the moment (that I know of).

smoothrunnings
Hero Member
*****
Offline Offline

Activity: 546


View Profile
March 04, 2014, 03:30:09 PM
 #7915

-a bitcoinAddress
do I need to add anything to the bitcoin.conf?

Not to change the node fee payment address. -a sets that address, as jedimstr said above.

So I don't need the disablewallet=1 in bitcoin.conf correct, only need to add the -a {address} to my P2Pool startup string?

 

No, you don't "need" it... but I use disablewallet=1 anyway since I only use bitcoin-qt (or bitcoin core since that's what we're calling it these days) for it's blockchain RPC and not as a wallet.

Note: disablewallet=1 only works on bitcoind/bitcoinqt OMG10 and 0.9.0 rc2 at the moment (that I know of).

Not sure what OMG10 is? I use bitcoin-qt 0.8.6 on my P2Pool.
cr1776
Legendary
*
Offline Offline

Activity: 1372


View Profile
March 04, 2014, 03:53:41 PM
 #7916

I have a good idea about how the non-linear sharechain will work, but implementing that hasn't started yet.

I think that sounds awesome. The thing is the disk space for the share chain isn't that big of a deal, it uses no space really compared to the bitcoind blockchain itself. And older shares once expired don't need to be saved forever. If the sharechain can work more similar to a normal PPLNS share database at centralized pools, that'd be a big win for smaller miners. (Some way to accumulate tiny shares without paying them until they exceed the dust level might be useful, but prone to abuse if someone tries to flood the sharechain with changing addresses just to bloat it.)

One option is that all stales still get passed around like valid blocks, and payments are based on all valid + stale blocks. It isn't like bitcoin where we actually need a single chain with a record of transactions. We're only using the chain's POW so we don't have to trust clients on how much work they are reporting.

Another thought on the dust issue for small miners with tiny shares is when they are served work, that work include the prior shares value that was too low to pay. That is, a normal miner finds shares A B and C. When calculating payouts, that miner is going to be paid A+B+C until those shares start to expire off the chain. A small miner finds share A that is below dust level. They don't appear in the Payouts list. However, when serving work to miner A, they are served a share to work on that includes the diff value from share A. When share B is accepted, share A is invalidated and share B has the value of A + B's new work. If B is > DUST, it goes into Payouts list. If not, then when small miner finds C, C will include B and B is invalidated.

The thought for doing DUST this way is the tiny miner can keep building a balance without storing every tiny share on the chain, and their dust won't expire off the chain before it can grow above the payment threshold since the share's age resets on each new share found. If the miner is so small they can't find even a tiny share consistently within the PPLNS window, they they probably need to mine something else. Wink This might be more appropriate for a pay-once PPLNS structure though and not the traditional PPLNS window p2pool uses now.

(BTW, I've never looked, but p2pool needs to store the block (share chain?) difficulty when work is served so that can be logged on the share chain with the share, and payments based on the diff of work done vs diff of the block, not just the diff of the work done. Otherwise people get unfair rewards around diff changes and the pool is hoppable.)

There are good ideas in here, particularly about the dust transactions for smaller miners.  Perhaps increasing the window too would be helpful with that change in order to accommodate smaller miners in the future.
jedimstr
Hero Member
*****
Offline Offline

Activity: 784



View Profile
March 04, 2014, 04:14:11 PM
 #7917

-a bitcoinAddress
do I need to add anything to the bitcoin.conf?

Not to change the node fee payment address. -a sets that address, as jedimstr said above.

So I don't need the disablewallet=1 in bitcoin.conf correct, only need to add the -a {address} to my P2Pool startup string?

 

No, you don't "need" it... but I use disablewallet=1 anyway since I only use bitcoin-qt (or bitcoin core since that's what we're calling it these days) for it's blockchain RPC and not as a wallet.

Note: disablewallet=1 only works on bitcoind/bitcoinqt OMG10 and 0.9.0 rc2 at the moment (that I know of).

Not sure what OMG10 is? I use bitcoin-qt 0.8.6 on my P2Pool.

Bitcoin OMG10 is the last updated version from the test build of Bitcoin-qt client from the Litecoin Devs (contributing back into the main bitcoin core development).  Check it out here: https://bitcointalk.org/index.php?topic=320695

It had a lot of the features that made it into 0.9.0 release candidates and 0.8.6 before they were released.

I don't think -disablewallet is available in the regular 0.8.6 release of bitcoind/bitcoin-qt.

Tegija
Member
**
Offline Offline

Activity: 98

Just Fun!


View Profile
March 04, 2014, 04:47:25 PM
 #7918

Is there anyway to disable the wallet function in P2Pool and have it instead forward the percentage of shares the note is to receive to a different wallet?

I have hit a stumbling block; over a week a go I initiated a transfer of over 1/2 a bitcoin and Bitcoin-QT told me I need to account for 0.0004 of the fee, so I did that and ever since the transfer has been in limbo, it looks like bitcoin-qt gave me the wrong fee to account for it if I understand the blockchain correctly.

https://blockchain.info/tx-index/7bbbc7b5fac8c2973e9c62a17cead946b9cf1832aac47479799ce566fafabcc1

Also I need to figure out if can fix this issue or have I lost those coins? Sad

Thanks,



i had long ago same problem and the solution is really -a. i do not really remember anymore how it really worked but it is possible to get back this coins. i am sure that here are many people who can help you to find solution.

main thing why i am writing about is that your problem has same background as my long ago: bitcoin-QT told you that you have to pay fee 0.0004BTC (it often happens virgin coins) but you paid only 0.00004, so 10 times less. try to be more careful next time to avoid that it happens again. i needed 3 weeks until i had my coins back...

Enjoy your life!
smooth
Legendary
*
Offline Offline

Activity: 1246



View Profile
March 04, 2014, 08:15:04 PM
 #7919

Is there anyway to disable the wallet function in P2Pool and have it instead forward the percentage of shares the note is to receive to a different wallet?

I have hit a stumbling block; over a week a go I initiated a transfer of over 1/2 a bitcoin and Bitcoin-QT told me I need to account for 0.0004 of the fee, so I did that and ever since the transfer has been in limbo, it looks like bitcoin-qt gave me the wrong fee to account for it if I understand the blockchain correctly.

https://blockchain.info/tx-index/7bbbc7b5fac8c2973e9c62a17cead946b9cf1832aac47479799ce566fafabcc1

Also I need to figure out if can fix this issue or have I lost those coins? Sad

Thanks,

Use the addnode listed here and keep your client open and connected so it will retransmit.

https://en.bitcoin.it/wiki/Free_transaction_relay_policy

If you can get it relayed, someone will probably mine it.

The issue with the transaction is the change output is small so it fails the 0.01 output rule. That is dumb and this rule is being removed but most nodes enforce it now.



qbsterr
Newbie
*
Offline Offline

Activity: 1


View Profile
March 04, 2014, 09:11:21 PM
 #7920


Hey,

I did start p2pool but im not sure is this setup correct.

My stats:

P2Pool BTC

Graphs

Version: 13.4-16-g5ee3172-dirty

Pool rate: 105TH/s (14% DOA+orphan) Share difficulty: 453000

Node uptime: 9.0 hours Peers: 7 out, 0 in

Local rate: 3.88GH/s (7.3% DOA) Expected time to share: 5.8 days

Shares: 0 total (0 orphaned, 0 dead) Efficiency: ? ? ?

Payout if a block were found NOW: 0 BTC to 1APv5LQpmEHuVitA7dJMEkVoamxYEPmw7c. Expected after mining for 24 hours: 0.000931 BTC per block.

Current block value: 25.13156442 BTC Expected time to block: 1.8 days


Im worry about Shares, Efficiency and Peers 0 in Sad

Is this normall ?

And how long i have to wait for any result ( avarage ) ?

Any advice ?

Pages: « 1 ... 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 [396] 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 ... 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!