Skip to content

Conversation

@instagibbs
Copy link
Contributor

Cookie defaults looking in regtest directory currently.

@instagibbs instagibbs changed the title Default to elementsregtest, when syncing liquid, find cookie [0.17] Default to elementsregtest, when syncing liquid, find cookie Mar 21, 2019
@instagibbs instagibbs force-pushed the default_elementsregtest branch from 587f690 to 5c784ca Compare March 21, 2019 13:12
@instagibbs
Copy link
Contributor Author

changing default is causing havok with some unit tests, investigating

boost::filesystem::path path(gArgs.GetArg("-mainchainrpccookiefile", MAINCHAIN_COOKIEAUTH_FILE));
std::string cookie_file = MAINCHAIN_COOKIEAUTH_FILE;
// Bitcoin mainnet exception
if (gArgs.GetChainName() == "liquidv1") {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

generalizing this becomes a pain due to dependencies :/

@instagibbs instagibbs force-pushed the default_elementsregtest branch from 40f80ef to 5273ed5 Compare March 21, 2019 14:43
@instagibbs
Copy link
Contributor Author

rebased to catch mempool_packages.py fix

@stevenroose
Copy link
Contributor

stevenroose commented Mar 21, 2019

utACK 5273ed5

@stevenroose
Copy link
Contributor

This should also fix https://github.com/Blockstream/liquid/issues/26.

@instagibbs instagibbs merged commit 5273ed5 into ElementsProject:elements-0.17 Mar 21, 2019
instagibbs added a commit that referenced this pull request Mar 21, 2019
…ind cookie

5273ed5 Default to mainnet cookie for liquidv1 (Gregory Sanders)
8ea52ee Default to elementsregtest (Gregory Sanders)

Pull request description:

  Cookie defaults looking in `regtest` directory currently.

Tree-SHA512: df8e384f12c84e7adf86edcc2d4a96432187ce58b76f19ea347b911988f55177efebcd8f5a5986acfe19044535b27ad896ec3f75a273bae24826e33ba58f40e0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants