CertiK reviewed Valinity (Valinity Application) on 28 Oct 2022: 16 findings, 0 critical; 13 marked fixed, 3 open.
Report hosted on skynet.certik.com.
Trustblock does not review code.
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 4 |
| Low | 3 | 0 | 9 |
During testing the testers found many bucket configuration issues with the `My Freedom Coin` project. The following problems exist. - Bucket Access Logging Disabled - Bucket Allowing Clear Text (HTTP) Communication - Bucket without Default Encryption Enabled - Bucket without MFA Delete - Bucket without Versioning
A hardware MFA device generates a six-digit numeric code based upon a time-synchronized one-time password algorithm. The user must type a valid code from the device when prompted during the sign-in process. Each MFA device assigned to a user must be unique; a user cannot type a code from another user's device to be authenticated.
The mnemonics and password for wallets as well as other sensitive information are still available in memory even after the user logs out of the application. This allows for an attacker with physical access to the user's system to access the memory and steal the session token. The clear text-sensitive information and PII in the memory should be reset after it is used or after the user logs out of the application.
The report names a repository or files. Open the report to see its scope.
1,044 projects reviewed · 1,375 reports · latest May 2025
See CertiK’s auditsSomething wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us