That's a participle ('-ed' word) you're using, and just as valid for a 'static' state name. (see http://puremvc.tv/#P003/T395
for more State Naming advice).
The key is to pick a worldview for conceiving your states from the outset and stick to it. Static States
If you think of a state as a 'room' you enter in then you have a static worldview and will use participles to name your states.Dynamic States
If you think of a state not as the room but as what you do in that room, then you have a dynamic worldview and will use gerunds (-ing words) to name your states.
A user is sitting at the login screen. Describe the state. LOGGED_OUT - Static
In the static worldview, your user is LOGGED_OUT until they fill the login form and click submit. That may take them to a CREDS_SUBMITTED state where the server checks your credentials. If that fails, then you transition back to LOGGED_OUT, and a good return would take you to LOGGED_IN.
Note also that the use of participles tends describe things that have happened in the past. Not what is happening now, which is a little less appropriate. You're LOGGED_IN, but now what. What are your options? The state name doesn't give you a clue about what's going on now in the user's world.LOGGING_IN - Dynamic
With a dynamic worldview you could say a user who is looking at a login screen is logging in. That is, they are looking at a form that collects their creds and they may be interacting with it at this moment. Clicking the submit button might take them to the AUTHENTICATING state where an animation plays while the server interaction happens. A bad return of service would transition us back to the LOGGING_IN state. A good return might take us to the SHOPPING state. Clicking the cart button would take us to CHECKING_OUT, and so forth.
So the use of gerunds for state names is much more focused on what the user or the system is doing right now.