This repository has been archived by the owner on Jun 7, 2023. It is now read-only.
Mobile: Secret Handling (includes #1060) #1080
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
* Implement quorum for wereAddressesSpentFrom * Simply #findSyncedNodes implementation * Add quorum support for getBalances IRI endpoint * Minor updates - Add quorum support for getTrytes IRI endpoint - Minor clean up in quorum methods * Add quorum support for findTransactions IRI endpoint * Rename quorum methods for better readability * Integrate quorum methods with extended api * Remove findTransactions & getTrytes endpoints from quorum * Refactor quorum implementation and do minor fixes - Update JSDoc typos - Simplify quorum implementation (Remove duplications) - Add a timeout for network request to each node - Fix issues in findSyncedNodes implementation - Update error messages * Add coverage - Add coverage for #determineQuorumResult - Add coverage for #fallbackToSafeResult - Add coverage for #findSyncedNodes * Add empty payload checks in quorum methods * Wrap percentage calculation in parentheses for clarity Co-Authored-By: laumair <aquadestructor@icloud.com> * Use develop branch of iota.lib.js * Enforce quorum (by default) on supported methods * Fix tests failing because of quorum enforcement * Add code documentation and rename parameters & variables for clarity - Related discussion #631 (comment) * [Security] Bump cryptiles from 3.1.2 to 3.1.4 (#829) * [Security] Bump nokogiri from 1.8.4 to 1.9.1 in /src/mobile/android (#828) * Make sure accounts are always iterated in correct order (by account index) (#824) Object.keys(<object>) function does not always preseve the order, especially if the object key starts with a number. This causes an issue when Object.keys is used for iterating on account names. #715 adds account indexes to state to make sure the order of accounts is always intact. However, some components in desktop use Object.keys directly on accounts object, which leads to certain issues of incorrect references to accounts. This commit fixes this issue by replacing Object.keys implementation on accounts with getAccountNamesFromState selector that guarantees the accounts order. Fixes #811 Note that the issues Object.keys create are not always noticeable. Steps to reproduce these issues are: - Add account with name "M" - Add another account with name "0" - Notice account names order in sidebar (Instead of "0" being the second account, it becomes the first) - Generate receive address from account "M" (Instead of generating receive address for account "M", it generates receive address for account "0") * New Crowdin translations [ci skip] (#826) * New translations translation.json (Czech) * New translations translation.json (Czech) * New translations translation.json (Japanese) * New translations translation.json (Spanish) * Mobile: Update findSyncedNodes * Update quorum.js * Improve parameters and variable names * Include custom nodes in quorum nodes * Reduce node request timeout for getNodeInfo api calls (in quorum)
…dger/trinity-wallet into mobile-0.6.0-alpha-quorum
…dger/trinity-wallet into mobile-0.6.0-alpha-quorum
* Rebuild entangled android Commit used: iotaledger/entangled@84f7446 PR: iotaledger/entangled#810 * Add batched proof-of-work methods in EntangledAndroid native module * Integrate entangled batched proof-of-work methods * Fix failing tests
…trinity-wallet into feat/trits-entangled
cvarley100
changed the title
…s-and-secret-handling
…://github.com/iotaledger/trinity-wallet into feat/combine-trit-methods-and-secret-handling
…s-and-secret-handling
…nd-secret-handling
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Includes #1060
Type of change
How Has This Been Tested?
Checklist:
mobilethat include native code (including React Native modules): I have verified that both iOS and Android successfully build in bothDebugandReleasemodesshared: If applicable, I have verified that my changes are implemented correctly indesktopandmobile