As discussed in this comment:
now that the faucet will be a network faucet, we should emit events for what notes were committed and consumed. For example, it would be great to be able to see the amount of time that passes between the time in which the operator submits the tx, then the note gets committed, and finally it gets picked up and consumed by the ntx builder. We should have this information as part of the SyncSummary that we get from doing Client::sync_state
Once #262 gets merged, the faucet will be a network account, which means a mint request takes two transactions to complete rather than one. It would be useful to have som way of measuring the latency of a mint request. We should emit tracing events tracking the lifecycle of a note so we can see how long each phase takes.
As discussed in this comment:
Once #262 gets merged, the faucet will be a network account, which means a mint request takes two transactions to complete rather than one. It would be useful to have som way of measuring the latency of a mint request. We should emit tracing events tracking the lifecycle of a note so we can see how long each phase takes.