You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
List every OS the wallet runs on. These map to the platforms field on the wallet record.
Windows
macOS
Linux
iOS
Android
Hardware
User type
New
Experienced
Criteria ratings and evidence
The wallet record carries a single check block that applies to every platform. Use the rating rubric in docs/wallet-submissions.md, and include evidence for each rating. Use platformOverrides.<os>.check only when one platform genuinely differs (rare).
Criterion
Proposed rating
Evidence
control
good
User controls the private keys
validation
not_applicable
Hardware device only
transparency
good
Open source with reproducible builds
fees
acceptable
User can choose from preset fees
If any platform overrides one of these criteria, list it here:
Features
The wallet record carries a single features array that applies to every platform. Use platformOverrides.<os>.features only when one platform genuinely differs.
2FA: Yes (FaceId and password code in app)
Hardware wallet support: Yes
Multisig: No
If any platform overrides the feature list, list it here:
Acquisition actions
List every way a user can install or open the wallet. Each acquisition path is one entry in the wallet's actions array.
An action without platforms applies to every platform the wallet supports.
Use platform scopes when install, web, or source links differ by OS.
App Store actions must be scoped platforms: ["ios"]. Google Play actions must be scoped platforms: ["android"]. Other actions can be scoped to any subset of platforms when the link genuinely differs per OS.
Thanks for the submission @Copy-of-A. Before we can merge this, a few wallet-record details need to be adjusted or clarified:
transparency should be changed from good to acceptable unless you can provide current public evidence that the shipped Android and iOS builds are reproducible from the published source.
We understand iOS reproducibility is less mature and harder to verify publicly than Android reproducibility. That said, if the wallet record claims transparency: "good" across Android/iOS, please provide public evidence that those shipped builds are reproducible.
WalletScrutiny currently lists Tangem Android as source-available rather than reproducibly verified, and does not treat the iPhone app as reproducibly verifiable under its iOS methodology: https://walletscrutiny.com/mobile/com.tangem.wallet/
Because Tangem is a hardware device used through Android/iOS companion apps, validation: "not_applicable" should not be set at the wallet level. That would make Android/iOS show validation as N/A too.
We recognise our submission guidance could make this mixed hardware + companion-app case clearer, and we’ll improve that process for future hardware wallet submissions. For this PR, please set the wallet-level validation to the mobile-app behaviour, then use a hardware override for the card/device:
If Tangem does not let Kaspa users choose their own node/RPC, the wallet-level validation should be caution. If Tangem does let Kaspa users choose their own node/RPC, please provide evidence and acceptable may fit.
Please replace the Google redirect URL with the direct Play Store link.
Please fill in the blank “Wallet name” and “Official wallet page” sections in the PR body.
Since the record is claiming source availability, please add scoped view_source actions for the public Android and iOS app repositories, for example:
This file contains hidden or 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
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.
Wallet Submission
Wallet name
Official wallet page
Wallet icon
public/hodl/wallets/tangem-wallet/icon.pngChange type
Acceptance evidence
Provide official public links that help maintainers verify the wallet and decide whether it is mature enough to list.
Source repository, or reason source is not public: https://github.com/tangem/ (public)
Release page or app listing: https://github.com/tangem/tangem-app-ios/releases, https://github.com/tangem/tangem-app-ios/releases
Documentation or support page: https://tangem.com/en/help-center/introduction-to-tangem-wallet/, https://tangem.com/en/help-center/submit-request/
Evidence of community usage or maturity:
Active maintenance evidence: Actively maintained
Supported platforms
List every OS the wallet runs on. These map to the
platformsfield on the wallet record.User type
Criteria ratings and evidence
The wallet record carries a single
checkblock that applies to every platform. Use the rating rubric indocs/wallet-submissions.md, and include evidence for each rating. UseplatformOverrides.<os>.checkonly when one platform genuinely differs (rare).If any platform overrides one of these criteria, list it here:
Features
The wallet record carries a single
featuresarray that applies to every platform. UseplatformOverrides.<os>.featuresonly when one platform genuinely differs.2FA: Yes (FaceId and password code in app)
Hardware wallet support: Yes
Multisig: No
If any platform overrides the feature list, list it here:
Acquisition actions
List every way a user can install or open the wallet. Each acquisition path is one entry in the wallet's
actionsarray.platformsapplies to every platform the wallet supports.platforms: ["ios"]. Google Play actions must be scopedplatforms: ["android"]. Other actions can be scoped to any subset ofplatformswhen the link genuinely differs per OS.Confirmation
src/data/wallets.tsplatformslists every supported OSfeaturesandcheckdescribe the wallet's defaults; per-OS variation lives inplatformOverridesactionscovers every acquisition path; platform-specific links useplatformsnpm run wallets:check