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

feat(lockup): expose unlock + add events #557 #559

Merged
merged 5 commits into from
Jun 11, 2022

Conversation

testinginprod
Copy link
Collaborator

closes: #557

@testinginprod testinginprod requested a review from a team as a code owner June 9, 2022 16:26
@NibiruHeisenberg
Copy link
Contributor

Looking at Osmosis' implementation, they automatically withdraw tokens from the lockup module to the user's account automatically in the EndBlocker. Is there a reason why we don't do that?

@@ -19,6 +20,8 @@ service Msg {
rpc InitiateUnlock(MsgInitiateUnlock) returns (MsgInitiateUnlockResponse) {
option (google.api.http).post = "/nibiru/lockup/init_unlock";
}

rpc Unlock(MsgUnlock) returns (MsgUnlockResponse) {}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unlock to a user could also mean InitiateUnlock. Maybe we should rename it to something like Withdraw.

@Unique-Divine Unique-Divine changed the title [lockup]: expose unlock + add events feat(lockup): expose unlock + add events #557 Jun 10, 2022
@AgentSmithMatrix AgentSmithMatrix merged commit 722fe2b into master Jun 11, 2022
@AgentSmithMatrix AgentSmithMatrix deleted the mercilex/lockup-expose-unlock branch June 11, 2022 08:56
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.

feat(lockup): add events
4 participants