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.

Sign up for GitHub

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

Jump to bottom

Problem: no local date entry for vesting time #59

Closed
tomtau opened this issue Sep 15, 2020 · 0 comments · Fixed by #96
Closed

Problem: no local date entry for vesting time #59

tomtau opened this issue Sep 15, 2020 · 0 comments · Fixed by #96
Assignees
@devashishdxt @leejw51crypto

Comments

@tomtau
Copy link
Contributor

tomtau commented Sep 15, 2020

https://github.com/crypto-com/chain-main/blob/master/doc/vesting.md
similarly to #29
it may be more human-friendly if one could optionally enter the start/end date in ISO-8601 (instead of unix time), i.e. "YYYY-MM-DD"
devashishdxt added a commit that referenced this issue Sep 21, 2020
@devashishdxt
Problem: No human-friendly date entry for vesting time
59c86ff 
Solution: Parse date string using RFC-3339. Fixes #59.
devashishdxt added a commit that referenced this issue Sep 21, 2020
@devashishdxt
Problem: No human-friendly date entry for vesting time
f9824ba 
Solution: Parse date string using RFC-3339. Fixes #59.
@devashishdxt devashishdxt mentioned this issue Sep 21, 2020
Merged
devashishdxt added a commit that referenced this issue Sep 21, 2020
@devashishdxt
Problem: No human-friendly date entry for vesting time
9a54065 
Solution: Parse date string using RFC-3339. Fixes #59.
devashishdxt added a commit that referenced this issue Sep 21, 2020
@devashishdxt
Problem: No human-friendly date entry for vesting time
3b3f1f1 
Solution: Parse date string using RFC-3339. Fixes #59.
devashishdxt added a commit that referenced this issue Sep 21, 2020
@devashishdxt
Problem: No human-friendly date entry for vesting time
7268fea 
Solution: Parse date string using RFC-3339. Fixes #59.
devashishdxt added a commit that referenced this issue Sep 21, 2020
@devashishdxt
Problem: No human-friendly date entry for vesting time
8cefc6d 
Solution: Parse date string using RFC-3339. Fixes #59.
tomtau pushed a commit that referenced this issue Sep 21, 2020
@devashishdxt
Problem: No human-friendly date entry for vesting time (#96)
c7060cd 
Solution: Parse date string using RFC-3339. Fixes #59.
damoncro pushed a commit to damoncro/chain-main that referenced this issue Oct 25, 2021
@yihuang
Problem: gravity bridge hooks and native token wrapping not connected (…
66d9e40 
…crypto-org-chain#59)

Closes crypto-org-chain#58

add denom-by-contract query cmd

test send back to ethereum

fix bidirectional e2e test

fix proto-lint

changelog

make proto-gen

Update x/cronos/client/cli/query.go

Co-authored-by: Thomas Nguy <81727899+thomas-nguy@users.noreply.github.com>

Update x/cronos/client/cli/query.go

Co-authored-by: Thomas Nguy <81727899+thomas-nguy@users.noreply.github.com>

Update x/cronos/keeper/grpc_query.go

Co-authored-by: Thomas Nguy <81727899+thomas-nguy@users.noreply.github.com>

fix contract not found error

Update integration_tests/utils.py

fix integration test

update contract
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@devashishdxt devashishdxt

@leejw51crypto leejw51crypto

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Problem: No human-friendly date entry for vesting time crypto-org-chain/chain-main
3 participants
@tomtau @devashishdxt @leejw51crypto