IOST address problem

XXXJAYXXX
Archived posts: 11
Joined: Feb 01, 2019

IOST address problem

by XXXJAYXXX · · Post #24230

I keep getting a notification telling me to update my IOST address to a mainnet address.. I have tried several times with different formats and different wallets... the system will not accept a mainnet address for IOST. This is also causing the issue of not being able to update/modify ALL payout address's.. as the IOST error causes all other info to not be saved. Please fix this.. would be nice to get that IOST payout after months of it being locked on the site...
Chris Sokolowski avatar
Chris Sokolowski
Site Admin
Archived posts: 945
Joined: Aug 27, 2014

Re: IOST address problem

by Chris Sokolowski · · Post #24234

I apologize for the frustration. The website was still validating IOST addresses as if it were an Ethereum token, which is why you couldn't enter one of the new chain addresses. I have fixed this and you now should be able to enter the new address. Please let me know whether it works now.
XXXJAYXXX
Archived posts: 11
Joined: Feb 01, 2019

Re: IOST address problem

by XXXJAYXXX · · Post #24237

Hi Chris, The format for the address has updated and now shows "Address" and "Destination tag"... however.. it will still not accept the IOST address format.. I have tried 2 different address's including the bissiost main wallet for voting.. and a huobi wallet as well (Huobi wallet is recommended on the IOST website).. Both of these addresses should work.. but both give me the same error.
Steve Sokolowski avatar
Steve Sokolowski
Archived posts: 4559
Joined: Aug 27, 2014

Re: IOST address problem

by Steve Sokolowski · · Post #24244

XXXJAYXXX wrote:Hi Chris, The format for the address has updated and now shows "Address" and "Destination tag"... however.. it will still not accept the IOST address format.. I have tried 2 different address's including the bissiost main wallet for voting.. and a huobi wallet as well (Huobi wallet is recommended on the IOST website).. Both of these addresses should work.. but both give me the same error.
Please submit a support ticket about this issue. I think that this may be a bug in the system. Once you submit a ticket, the bug can be tracked and assigned to Vance for resolution as soon as possible. Thanks!