Closed JSHan94 closed 2 months ago
The changes in the vip_vesting.move
module add a new struct, UserVestingResponse
, which includes fields for tracking user vesting details. Additionally, two new public functions, get_user_vestings
and get_user_vestings_finalized
, are introduced to retrieve user vesting information based on specified stages. These updates enhance the functionality related to user vesting information retrieval.
Files | Change Summary |
---|---|
precompile/modules/initia_stdlib/sources/vip/vesting.move |
Introduced UserVestingResponse struct with various fields and added two public functions for retrieving user vesting information based on specified stages. |
sequenceDiagram
participant User
participant Contract
participant VestingStore
User ->> Contract: get_user_vestings(account_addr, bridge_id, stages)
activate Contract
Contract ->> VestingStore: acquire VestingStore
VestingStore -->> Contract: vesting_data
Contract -->> User: vector<UserVestingResponse>
deactivate Contract
User ->> Contract: get_user_vestings_finalized(account_addr, bridge_id, stages)
activate Contract
Contract ->> VestingStore: acquire VestingStore
VestingStore -->> Contract: finalized_vesting_data
Contract -->> User: vector<UserVestingResponse>
deactivate Contract
In the land of code, a struct did arise,
With fields so rich, it was no surprise.
Vesting info now so clear and wise,
Two functions added to retrieve the prize.
Hopping through stages, with data in hand,
Our vesting journey, perfectly planned.
🎉🐇
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Summary by CodeRabbit