Problem: can't reach consensus about the current state of Nostrocket and Subrockets
The Nostrocket Engine subscribes to all events that are in reply to the ignition event: 503941a9939a4337d9aef7b92323c353441cb5ebe79f13fed77aeac615116354.
It parses each event and validats it against the Nostrocket Protocol, and builds its internal state.