Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 419. (Read 2591964 times)

Is there anyway to setup bitcoin-qt so it subtracts the correct fee from your send transfers without you having to do it manually like multibit does?

Thanks,

Yes it will eventually time out and you will get your coins back, unless it happens to get mined by someone who doesn't care about the fee.

Minor correction to your terminology though. It isn't in the "blockchain" just the memory pool (collection of unmined transactions that have been sent).

EDIT: You still need to remove the transaction from your wallet so you can resend, which seems most easily done by (temporarily) creating a new wallet and importing the private keys for all the inputs on the transaction. That sounds like a pain, but it is what it is.

the way to fix those is just to create a new wallet.dat (back up old one ofc), then import private key of the address that sent those coins that never arrived and reindex blockchain

Thanks. I am in the process of moving my P2Pool so I can use pywallet and leave my bitcoin-qt shutdown for a week or so, hopefully the it will be removed from the blockchain then so I can resend it with the correct amount, then move my P2Pool back.

correct fee for that is 0.0004, the fee on link provided is 0.00004

chances of getting into a block that is less than 10k (or 27k if it's priority)  in size is slim

now if ppl would just upgrade their doge pools to new version.

alas

For now, waiting weeks is unlikely (but possible). The average for the pool to find a block is only a day and a half, so very likely it will find one during the three days your share is active.  

My feeling on this has always been if its a hobby (and it damn well better be a hobby at 4 GH) then treat it as such, have fun with the small "raffle" and help the bitcoin and p2pool networks by running a node

This will get worse as difficulty continues to grow if the p2pool network doesn't keep up (and it doesn't look like it will), but still no reason not to treat it like a fun raffle if you are mining as a hobby.

for sure it does not have big sense to have own node for such small hash power. you should connect your power then at least to one node where are already some miners, so you will have little better chance to find a share. or try to find some more miner for your own node.

0 in peers is fine, you have 7 out so you are connected. You only get paid if you find shares for the share chain and


Is not pretty. It will take you on average 6 days to find a share. That share will be worth enough to cover 6 days of earnings, except the pool also needs to find a block while your share is active.

Some miners with 180GH of hash power don't like using p2pool because of the variance. Using it with 4GH... you can do it, but you might wait weeks at a time without a payment if you have bad luck.

Hey,

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

My stats:

<sup>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</sup>

Im worry about Shares, Efficiency and Peers 0 in

Is this normall ?

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

Any advice ?

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.

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...

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://bitcointalksearch.org/topic/bitcoin-omg-including-watch-only-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.

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.

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

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).

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

 

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. 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.)

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!

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