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

dMSTR token not visible on EVM address in Lightwallet #4189

Open
chrsch opened this issue Aug 13, 2024 · 4 comments
Open

dMSTR token not visible on EVM address in Lightwallet #4189

chrsch opened this issue Aug 13, 2024 · 4 comments
Labels
kind/bug Something isn't working needs/area Needs area label(s) needs/priority Needs a priority label needs/triage Waiting for triage to be accepted

Comments

@chrsch
Copy link

chrsch commented Aug 13, 2024

What happened:

I did sent dMSTR token from Metamask wallet on EVM to EVM address of Lightwallet. This works fine for me all the time. But this time I sent the dMSTR two days ago, so after the MSTR token split happened.

What you expected to happen:

I expected the Lightwallet would pick up the Tokens and convert them to the new tokens according to the stock split.

How to reproduce it (as minimally and precisely as possible):

If you have dMSTR token obtained before the MSTR stock split on the EVM send them to the EVM address of your Lightwallet

Anything else we need to know?:

@chrsch chrsch added the kind/bug Something isn't working label Aug 13, 2024
@github-actions github-actions bot added the needs/triage Waiting for triage to be accepted label Aug 13, 2024
Copy link
Contributor

@chrsch: Thanks for opening an issue, it is currently awaiting triage.

The triage/accepted label can be added by foundation members by writing /triage accepted in a comment.

Details

I am a bot created to help the BirthdayResearch developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.

@github-actions github-actions bot added the needs/area Needs area label(s) label Aug 13, 2024
Copy link
Contributor

@chrsch: There are no 'area' labels on this issue. Adding an appropriate label will greatly expedite the process for us. You can add as many area as you see fit. If you are unsure what to do you can ignore this!

You can add area labels by leaving a /area comment.

Details

I am a bot created to help the BirthdayResearch developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.

@github-actions github-actions bot added the needs/priority Needs a priority label label Aug 13, 2024
Copy link
Contributor

@chrsch: Thanks for opening an issue, an appropriate priority will be added soon.

The priority labels can be added by foundation members by writing /priority [type] in a comment.

Details

I am a bot created to help the BirthdayResearch developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.

@chrsch
Copy link
Author

chrsch commented Aug 18, 2024

/area assets

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working needs/area Needs area label(s) needs/priority Needs a priority label needs/triage Waiting for triage to be accepted
Projects
None yet
Development

No branches or pull requests

1 participant