-
Notifications
You must be signed in to change notification settings - Fork 13
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
Tezos not delagating on Galleon #679
Comments
I have not been able to confirm. I haven’t received any rewards. Not sure what to do.
…Sent from my iPhone
On Jul 27, 2020, at 2:35 AM, Shaun Young ***@***.***> wrote:
@BostonPatriot Hello mate, have you been able to confirm if your tezzies have been delegated and if you're receiving your rewards ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I am experiencing the same thing, delegated on June 18th, shows Delegated to tz1xxxxxx... in the wallet, I see no rewards on the transactions page, the last transaction was Updated Delegate. Talked with another person who did this around the same time period and they are also not seeing any rewards?? |
Is that normal? Seems odd to set up the wallet, deposit coins, put in your delegate and then have to re-install the wallet. For both me and the other person, these were new installations with the latest version of the wallet. |
Not sure what the fundraiser PDF is, so I would assume I didn't participate |
Ok, so the Restore function is in the Web site and not within the wallet? |
The website asks for a 15 word seed phrase - when you signed up it gave you a 24 word seed phrase. It also doesn't ask for any sign in information, just a seed phrase to restore? |
I delegated my Tezos on Galleon and it actually says delgated underneath where my total tezos are in my wallet. I did this initially on April 24. They should have been delegating a week or two ago. How do i make sure i am recieving these tokens i should be baking.
thank you,
The text was updated successfully, but these errors were encountered: