If Bob has a newly installed node and dApp he get's a "out-of-funds" error from the doichain node when executing his first name_doi.
In this stage he should have received already 0.01 DOI for this operation.
It is unclear if this 0.01 can already be spent without confirmation.
Also names/main.h NAME_LOCKED_AMOUNT=50 spends 0.02 DOI so far which is too much regarding to our specification of 0.01
update white paper about this issue.
Update: Transaction cannot be spend as long as there is no confirmation of the last transaction (new block) but the job collection will take care of this and update this transaction in the job queue as soon thats done. The transaction can already be put into the queue for "de-facto confirmed DOI" but might not yet be effectively written back to the blockchain. Alice dApp gets informed as soon as Bob was receiving the HTTP-GET request originating from the DOI request email .
If Bob has a newly installed node and dApp he get's a "out-of-funds" error from the doichain node when executing his first name_doi.
In this stage he should have received already 0.01 DOI for this operation.
It is unclear if this 0.01 can already be spent without confirmation. Also names/main.h NAME_LOCKED_AMOUNT=50 spends 0.02 DOI so far which is too much regarding to our specification of 0.01
update white paper about this issue.
Update: Transaction cannot be spend as long as there is no confirmation of the last transaction (new block) but the job collection will take care of this and update this transaction in the job queue as soon thats done. The transaction can already be put into the queue for "de-facto confirmed DOI" but might not yet be effectively written back to the blockchain. Alice dApp gets informed as soon as Bob was receiving the HTTP-GET request originating from the DOI request email .