-
Notifications
You must be signed in to change notification settings - Fork 13
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
[Bounty Job] - Upgrade Chips-Core to latest Bitcoin-Core upstream code #10
Comments
Hi @satindergrewal, |
Completed @ https://github.com/barrystyle/chips |
Thanks @barrystyle! I'll ask some developer from Chips to go through you upgrade changes. Will be getting back to you on it soon. |
Thanks for the so far work @barrystyle. Bounty amounts paid details:
There are still other things which needs to be done on this upgrade:
daemon=1
txindex=1
rpcuser=user$(openssl rand -base64 12)
rpcpassword=password$(openssl rand -base64 12)
rpcbind=127.0.0.1
rpcallowip=127.0.0.1"
prune=0
|
I am looking into adding the seeds for clearnet, tor, and i2p. Two questions:
|
@who-biz Theyve already been hardcoded into the base (https://github.com/satindergrewal/bitcoin/blob/barry/src/chainparamsseeds.h). |
@barrystyle you've included seeds for all of: clearnet, tor, and i2p? |
This should probably be closed, issue no longer relevant with current direction. |
Chips-Core code is forked from some Bitcoin-Core 0.16 (if I remember correctly). And as of this old version, Chips only does support Tor Onion v2 addresses to setup Chips node over tor.
Tor service version 2 addresses are being deprecated already. Here's relevant link: https://blog.torproject.org/v2-deprecation-timeline
It is important to have a decentralised and private network of Chips network nodes for Pangea Poker, and we need to have support for latest Tor Onion v3 addresses in Chips-Core software. Bitcoin recently removed Onion v2 support from their latest code base, since it's been suggest to move the Tor services support to Onion v3 long ago by Tor project.
Since we have the need, the opportunity, and the right time to upgrade Chips to latest upstream Bitcoin-Core code, we should take this opportunity and do efforts to do so.
So, I offer a bounty to anyone or any team who upgrades Chips-Core to latest upstream code base of Bitcoin-Core.
Bounty:
TOTAL BOUNTY ON OFFER: 4000 KMD
But, you have to make sure that there'll be backwards compatibility APIs which kept in latest upgrades as well. Have a word with the core developers to know which ones are most important to keep for backward compatibility. One example I know is to keep
getinfo
API in latest upgrade.The text was updated successfully, but these errors were encountered: