Closed johnp1954 closed 6 years ago
The actual root cause here is likely the polling mechanism that starts when you aliasnew
. There is an async process for writing the alias public data may be the root cause here. If that polling mechanism gets tripped up by user actions (within BM or by closing/opening BM) the offchain data won't be written to the mongo DB, but the read side of the BM:DT experience is asynchronous to this so it will encounter an error when reading from the offchain DB.
When you create an Alias and change the expiring date to a date far into the future the cost can be extremely high. Can you show the estimated cost of an Alias when the date is changed, or an acceptance dialog stating the rough cost when pressing OK