-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow for new AUX POW. #51
Conversation
getauxblock is being depreciated and replaced by createauxblock and submitauxblock. This allows for specifying a payment address when asking for an auxblock instead of getting a wallet address so you don't have to run a wallet where p2pool has access. Most coins support both methods, some only support the old method (Terricoin is an example) and some only support the new method (Myriadcoin is an example). Use `--merged` for the old style and `--merged_addr` for the new style.
@jtoomim Since I don't have any hash power at the moment, I couldn't test that the submitting of aux work is working, but I think I should. If you have some testnet with aux, can you double check it? |
I've never messed around with the auxpow stuff, unfortunately. Testing this would be harder for me than for you. Perhaps you could rent some hashpower on nicehash? |
@rldleblanc and @jtoomim I've tested p2pool with this pull request on our own altcoin fork on testnet. And I just received blocks on the configured address! Thanks for the good work! The only thing which seems ugly is the % char between the address and the merged_addr url!. Makes some problems inside systemd for me. |
That's great news. What was the main coin and what was the aux coin(s)?
Sent from a mobile device, please excuse any typos.
…On Sat, Sep 26, 2020, 11:14 PM Nico Krause ***@***.***> wrote:
@rldleblanc <https://github.com/rldleblanc> and @jtoomim
<https://github.com/jtoomim> I've tested p2pool with this pull request on
our own altcoin fork on testnet. And I just received blocks on the
configured address! Thanks for the good work!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#51 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACW6TV2QUASBEPRE3VAKVR3SH3C4JANCNFSM4PY7EDHQ>
.
|
Thanks for testing it, @inspiraluna. I'm willing to merge this either now or after the % issue has been changed. Do you have a suggestion for what to do instead of the %? |
Well, I don't know if anything would speak against it; Now: Later: That would require testing the URL in a different way. I guess it would be not a problem. I am just not a python programmer yet otherwise I could do it by myself quickly. If somebody is faster then me with it, that would be it. |
@rldleblanc Main blockchain was Bitcoin 0.20. and Aux-Coin was Doichain (DOI) Doichain is a project which is aiming to record "Double Opt Ins" (DOIs) in order to track unforgeable email permissions on blockchain for preventing spam in email marketing businesses. |
I tried using a delimiter that would not interfere with anything that could be a path (I'm not aware of any coins using a path, but you never know). I have a shell script that launches p2pool with all the correct parameters and I call that from systemd. /home/rleblanc/start_p2pool.sh:
/etc/systemd/system/p2pool.service:
Probably a lot easier than managing systemd and having to reload on every change. |
@rldleblanc I ended up doing the same as you. Created another shell script which starts p2pool. But it seemed a bit of pain if you don't calculate with it, since it needs an additional research. What is the problem here with systemd etc? Which solutions are possible? Is it possible to escape the # in the string or not? Regarding to your worries, that other coins would use a path for constructing the rpc url, I am still thinking about this possibility but generally don't really see it as a scenario since more or less all (well, I don't have the full overview) forked from bitcoin and use this simple rpc url. But if you really think so and other coins would do so, why not embrace this thought and use this: http://ncuser:ncpass@127.0.0.1:port/?payout_addr=xyz In such a way such coins (if such coins should exist) could still work and we just append a parameter. |
I'm getting this error:
This is the createauxblock output of the bvault daemon:
So no target or _target Mining BTC and trying to merge mine BTCV |
getauxblock is being depreciated and replaced by createauxblock and
submitauxblock. This allows for specifying a payment address when asking
for an auxblock instead of getting a wallet address so you don't have to
run a wallet where p2pool has access. Most coins support both methods,
some only support the old method (Terricoin is an example) and some only
support the new method (Myriadcoin is an example). Use
--merged
forthe old style and
--merged_addr
for the new style.