It's a little confusing right now since Futures provide an onCompletion() method of their own to add completion callbacks, so you can wind up with instance->onCompletion().onCompletion([]{ /*[...]*/ });

This also lets me sidestep a name collision with the existing TransactionCoordinator::onCompletion() method.