When a double-opt-in gets confirmed before the first confirmation. name_doi throws an Error since the blockchain has this nameId already in the mempool. Executing another "name_doi" throws this error:
Also during the update process the send-dApp gets informed about the confirmation before name_doi got stored in the blockchain. (it should be the other way around /imports/modules/server/doichain/update.js
Thoughts to resolve this issue:
1) Don't throw an error from doichain node in this case
2) Catch this error and don't make so much noise about it.
When a double-opt-in gets confirmed before the first confirmation. name_doi throws an Error since the blockchain has this nameId already in the mempool. Executing another "name_doi" throws this error:
Also during the update process the send-dApp gets informed about the confirmation before name_doi got stored in the blockchain. (it should be the other way around /imports/modules/server/doichain/update.js
Thoughts to resolve this issue: 1) Don't throw an error from doichain node in this case 2) Catch this error and don't make so much noise about it.
At the moment I prefer this solution 2)