Currently ION is configured so that, after a DID is published, subsequent DID publication is blocked until the first transaction is confirmed.
Unless there is a reason why multiple unconfirmed DID transactions should not be published in the same block (as far as we know, there isn't), this constraint should be dropped.
Ideally, the server should also attempt to batch operations by waiting (e.g. for 5 minutes) after receiving the first publish request, to catch requests from other users.
Currently ION is configured so that, after a DID is published, subsequent DID publication is blocked until the first transaction is confirmed.
Unless there is a reason why multiple unconfirmed DID transactions should not be published in the same block (as far as we know, there isn't), this constraint should be dropped.
Ideally, the server should also attempt to batch operations by waiting (e.g. for 5 minutes) after receiving the first publish request, to catch requests from other users.