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
{{ message }}
This repository has been archived by the owner on Feb 26, 2021. It is now read-only.
If you are not suggesting a feature, you must be able to check all of the following (place an x inside the brackets to check the box). If you cannot check all of the boxes, this issue should not be reported on GitHub as it is not a bug:
I confirm that this is an issue with the IOTA Wallet and not an exchange
I confirm that this is an issue with the wallet, not IRI
For pending transactions: I confirm that I have tried reattaching and promoting multiple times (check this box if your issue is not related to a pending transaction)
I confirm that this is not an issue related to stolen/lost funds
I confirm that this is not a zero balance issue related to a snapshot (last snapshots occurred on October 23 and January 28)
For private key warnings: I confirm that I am not at risk of reusing an address, or another user has verified that I am not (check this box if your issue is not related to a private key reuse)
I confirm that this issue is present on the latest version of the wallet
Description
[Description of the bug or feature]
Steps to Reproduce
[First Step]
[Second Step]
[and so on...]
Expected behavior: [What you expected to happen]
Actual behavior: [What actually happened]
Versions
[OS Version]
[Wallet Version]
The text was updated successfully, but these errors were encountered:
Was there an unaccounted for change in the shasum 256 for the following between 7/25 and 7/26?: iota-2.5.7.x86_64.rpm
yyyoo
changed the title
Was there an unaccounted for change in the shasum 256 for he following between 7/25 and 7/26?: iota-2.5.7.x86_64.rpm
Was there an unaccounted for change in the shasum 256 for the following between 7/25 and 7/26?: iota-2.5.7.x86_64.rpm
Jul 26, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Prerequisites
If you are not suggesting a feature, you must be able to check all of the following (place an x inside the brackets to check the box). If you cannot check all of the boxes, this issue should not be reported on GitHub as it is not a bug:
Description
[Description of the bug or feature]
Steps to Reproduce
Expected behavior: [What you expected to happen]
Actual behavior: [What actually happened]
Versions
[OS Version]
[Wallet Version]
The text was updated successfully, but these errors were encountered: