Skip to content

Vaulta Rebrand and New Contract Support #35

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

Open
wants to merge 48 commits into
base: develop
Choose a base branch
from

Conversation

ericpassmore
Copy link

Summary

EOS has rebranded to Vaulta. This update changes the brand name and logos. App code changes were required. Tests have been added and re-organized to support old and new contract names.

Security Review

Small code changes may require security review

Checklist

  • App update process has been followed
  • Target branch is develop
  • Application version has been bumped

Dependency

Depends on App-Database Update LedgerHQ/ledger-app-database#353

Details

EOS is rebranding to Vaulta, with a new ticker symbol A.

  • Update logos to match new branding
  • Update to AppName to Vaulta branding name
  • Remove references to unsupported fairy wallet
  • Refactor tests to distinguish legacy eosio tests and core.vaulta tests
  • Add additional test cases for A token and core.vaulta contract
  • Added wumpas tests with bad transfer actions, and validated they came across as unknown actions
  • Update Golden Images for testing. Includes new subdirectory structure for Golden Images for better isolation of eosio and vaulta transactions.
  • Upgraded tests to ledgered.Devices
  • Updated pylint config to accept more branches due to added test cases
  • Updated readme
  • Removed nanos from .toml
  • Upgraded Action in tests to accept straight hex-encoded data when provided.

ericpassmore and others added 30 commits February 7, 2025 10:49
…pdate

- 2025 documentation update for testing ledger. 
- regenerated snapshots for minor off by one pixel difference in text
- regenerated snapshots for flex which have better display of pagination where max pages > 10
… unknown/suspect when they data is not sufficient
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant