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] The staked New York Coin did not come into my wallet #160

Open
SeongyeolYun opened this issue Apr 15, 2023 · 1 comment
Open

Comments

@SeongyeolYun
Copy link

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

The transaction was rejected by itself, and in case of rejection, it should be able to come into the wallet or refund, but there is no such function itself, so all my coins are now gone.

Currently, New York Coin has been changed to V2,
The New York coin I initially sent is V1.
Knowing that you need to change V1 New York Coin to V2
I went into my wallet
After 3 days of being sent, it was in a rejected state.

If so, it seems normal that the coin should be sent back to the wallet itself after being rejected.
No further work has been done,
I can't even do that myself

I suffered a loss because the 1885 million New York Coins I purchased for the purpose of New York Coin staking are not returned to my wallet in the current rejected state.

this is fatal error...

In the part where this changes from V1 to V2,
It seems there is an error
I do not know
Even if I ask people around the country, they say that this is the first time I've seen this, so I'm asking.

https://explorer.hiro.so/txid/0x73cdb8feaf2d5102f2461513293bf93b52c3a9d734f3e26fb1a50a25923b044c?chain=mainnet

My wallet address is SP2HEG2K7FQ1DT3MTD4T50H5XRGZAHZ3Z0JPV5YJR

I'm Korean..

Help me.

@SeongyeolYun SeongyeolYun added the Enhancement New feature or request label Apr 15, 2023
@whoabuddy whoabuddy added Bug Something isn't working and removed Enhancement New feature or request labels Apr 24, 2023
@whoabuddy
Copy link

Hello @SeongyeolYun - we should be able to get everything all fixed up here, it looks like there is just some confusion about the protocol changes that happened about a year ago.
https://www.citycoins.co/post/protocol-upgrade-faq

The transaction was rejected by itself, and in case of rejection, it should be able to come into the wallet or refund, but there is no such function itself, so all my coins are now gone.

If you are talking about the transaction you linked earlier, it's from over a year ago and we can see it failed because of (err u1) which is user does not have enough funds.

This is because the transaction just before it succeeded with the same parameters, and locked 188,500 NYC in the v1 stacking contract from cycles 6 to 15.

If we use this tool to check V1 stacking data for your address, we can see you have not claimed for any of those cycles. Next step would be to use that same wallet, log in at minecitycoins.com, and search for NYC cycles 6 through 15 under claim. Each should show your portion of the cycle reward, if available, as well as let you claim the NYC back in cycle 15.

image

Once those V1 CityCoins are returned and all transactions are finalized, you can convert the NYC to V2 using the profile tab on minecitycoins.com. When you refresh it detects your balance and will automatically display a convert button to generate the transaction.

It looks like you've successfully converted 368 NYC one time, so the process will be similar once you claim your NYC back from the old contract.

Finally, you have the option to stack again from that same interface at minecitycoins.com, which will create a transaction for the latest contract (ccd007-citycoin-stacking).

@whoabuddy whoabuddy removed the Bug Something isn't working label Apr 24, 2023
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

No branches or pull requests

2 participants