Skip to content
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

movement branch #115

Open
wants to merge 345 commits into
base: main
Choose a base branch
from
Open

movement branch #115

wants to merge 345 commits into from

Conversation

0xmovses
Copy link
Collaborator

Description

Type of Change

  • New feature
  • Bug fix
  • Breaking change
  • Performance improvement
  • Refactoring
  • Dependency update
  • Documentation update
  • Tests

Which Components or Systems Does This Change Impact?

  • Validator Node
  • Full Node (API, Indexer, etc.)
  • Move/Aptos Virtual Machine
  • Aptos Framework
  • Aptos CLI/SDK
  • Developer Infrastructure
  • Other (specify)

How Has This Been Tested?

Key Areas to Review

Checklist

  • I have read and followed the CONTRIBUTING doc
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I identified and added all stakeholders and component owners affected by this change as reviewers
  • I tested both happy and unhappy path of the functionality
  • I have made corresponding changes to the documentation

mzabaluev and others added 30 commits June 6, 2024 11:20
Use ? for terser, idiomatic code that can be cribbed for production.
Draft a test for FinalityView, checking that the latest_state_checkpoint_view
extension method gets us the view into finalized state.
StateView support in the mock is needed to complete the test.
In FinalityView::set_finalized_block_height, remove the outdated
sanity check, add comments explaining why we can use the empty hash
and no signatures specifically for Movement.
For set_finalized_block_height, retrieve ledger info from the
corresponding epoch or use the latest.
Exercise the DbStateView instance returned from
latest_state_checkpoint_view. No testing yet if the state
matches expectations for the finalized version.
Access to account state is convenient to test with.
`FinalityView`, a `DbReader` wrapper to represent a finalized state
Pass LedgerInfoWithSignatures by reference like in other methods.
Do not try to set epoch and version on the LedgerInfo in a way that
does not work. Instead, it's expected to be correct for the latest
pre-revert version.
All necessary information can be obtained from
either the LedgerInfoWithSignatures, or the current
database state.
Update both progress values in the ledger metadata
schema in one batch.
…vert

Make `LedgerInfo` the source of truth on revert
Rewrite the computation for rewards rate to avoid
division by zero when the epoch duration exceeds one year.
…n-long-epochs

fix: prevent zero divide on long epoch duration
andygolay and others added 30 commits December 1, 2024 20:24
…th side. Move unit tests pass, still working on E2E Move tests
…for now to help reviewers make sense of everything
Native bridge: Modify param serialization to make bridge transfer IDs match on Move and Solidity sides in both L1 -> L2 and L2 -> L1 directions
…ovementlabsxyz/aptos-core into andygolay/remove-initiate-hex-complete
…e-hex-complete

Fix: remove hex conversion from initiator in complete bridge transfer, refactor to one module per file
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.

9 participants