forked from etotheipi/BitcoinArmory
-
Notifications
You must be signed in to change notification settings - Fork 172
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
Remove more torrent code #29
Closed
Closed
Conversation
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
some extra block scanner code
Says mempool replaceable instead of RBF to be less vague and more similar to what Bitcoin Core says.
More fixes.
Indicates whether transactions are Opt In RBF
dedicated ZC db
disable BlockDataMap gc
verbose in init()
Follows up to what was started in #4
Option makes script only compile C++ code and copy it and the Python code to Armory.app. Changes are now near-instantaneous instead of taking 5-10 min. waiting for a rebuild of all the background components. Script may need a bit of tweaking to remove unnecessary, intermediate files (e.g., pyc files) so that tar.gz files don't include cruft.
Fixes signed message verification by removing stuff related to ATI signed messages.
Fixes the verification of ClearSign signed messages by remove an extraneous line that is added where the comment used to be.
In certain instances, if certain calls are given a font not found on the system, Armory attempts to revert to the system font. The call for the system font is incorrect. Patch fixes this problem.
increment testing version
Have you tested this at all? |
goatpig
pushed a commit
that referenced
this pull request
Nov 10, 2017
64037f8 Update JavaScript tests (Pieter Wuille) Pull request description: Tree-SHA512: ae9b8f1539d51eac45ea7df8a46d08de1c4764db259c6cf1492984da0723e2f996508e75efbaf2b3da5213b6e018b467b0810ff15b5b86e16856e24aaf83beea
goatpig
pushed a commit
that referenced
this pull request
Nov 10, 2017
af2da22 Add new tests for invalid Bech32 strings (Clark Moody) Pull request description: Similar updates in the vein of #27, #29, #30, #31, #32 Adds invalid Bech32 string test cases. Please note: Rust strings are UTF-8, so that the character literal `0xff` [turns into](https://codepoints.net/U+00FF) `0xc3bf` when accessed with the `bytes` function. Tree-SHA512: 73f85762fc22059acb9c4b382068997fb0341354f1de26ecb2d75ba3c57aee80609fd2839967541c9a9f96ccdc04137140174396f5acfe62a6511fd9f18e703e
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.