-
Notifications
You must be signed in to change notification settings - Fork 24
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
Replace Insight with Bitcoin Core in BlockchainWriter #408
Merged
Merged
Changes from 16 commits
Commits
Show all changes
22 commits
Select commit
Hold shift + click to select a range
764ad6c
delete useless tests
lautarodragan 4bb4ac7
more bitcoin-core typings
lautarodragan b8c1c01
docker-compose bitcoin-regtest
lautarodragan 416e841
UnspentOutput interface
lautarodragan a6c50c3
basic but actually working thing
lautarodragan ed25213
npm uninstall bitcore-lib
lautarodragan 07451fc
npm uninstall @types/bitcore-lib
lautarodragan d81974d
lint
lautarodragan 6d4c7f9
estimate fee wip
lautarodragan cdbe35a
revert ramda.d.ts
lautarodragan e47b399
improve bitcoin-core.d.ts
lautarodragan d9a4884
default bitcoin rpc config to regtest
lautarodragan 9a71119
use fundrawtransaction + small refactor
lautarodragan e7656b2
Merge branch 'master' into bitcoin-core-writer
lautarodragan 35c5926
rename poet-bitcoind to bitcoin-testnet in docker-compose, fix ports
lautarodragan cece185
Merge branch 'master' into bitcoin-core-writer
lautarodragan b4619ae
Merge branch 'master' into bitcoin-core-writer
lautarodragan e90d89a
split docker-compose.testnet
lautarodragan 9ff3b1e
add TODO
lautarodragan a1ce206
add unit tests for Bitcoin.getData
lautarodragan 8c231fa
mini fix to docker-compose.yml
lautarodragan 0927e0c
Merge branch 'master' into bitcoin-core-writer
lautarodragan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see the need to stand up a testnet docker instance anymore now that we are using regtest. If that is correct, can we either comment this out or remove it? Otherwise when I run
docker up --build
I am starting up a testnet instance and syncing with the testnet blockchain, thus using up bandwidth and storage for no real reason.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point @geoffturk. I can't think of a situation that I would still want a testnet docker instance locally.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, now that I thought about it more, I think we do want a mainnet/testnet instance actually for people to run the node on their machines. Maybe we just need a simpler way of expressing which instance we run instead of running all of them, but that can be tackled in a future PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's correct, I'll split it apart in different docker-compose files. We still want to test stuff in testnet if possible, but
docker up
shouldn't cause you to download the whole testnet.