-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
ibax wallet adress change bug #2097
Comments
Hello, I have the same problem, did you solve it? |
what's your problem
I can not understand
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virüs
yok.www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
muhammetgokce ***@***.***>, 16 Mar 2023 Per, 14:06 tarihinde
şunu yazdı:
… Hello, I have the same problem, did you solve it?
—
Reply to this email directly, view it on GitHub
<#2097 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXKIOKGJIBXWTPPZ2DTNBF3W4LX4TANCNFSM6AAAAAATTDR2JY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sama problem for me |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
i need change ibax wallet adress. i wrote wrong adress before. i can't change wallet adress. Can you help me?
Receive notification email
yucelbaransel@gmail.com Modify
Address of the wallet that has been bound to receive IBXC
1800-1137-3846-3390-3961 i need change this wallet
my new wallet adress 0820-5816-7102-5938-6564
Reproduction
i need change ibax wallet adress. i wrote wrong adress before. Can you help me?
Receive notification email
yucelbaransel@gmail.com Modify
Address of the wallet that has been bound to receive IBXC
1800-1137-3846-3390-3961 i need change this wallet
my new wallet adress 0820-5816-7102-5938-6564
System Info
Logs
Validations
The text was updated successfully, but these errors were encountered: