Ok, I have found the answer. From the syncrepl documentation it says this
The consumer also stores its replica state, which is the provider's contextCSN received as a synchronization cookie, in the contextCSN attribute of the suffix entry. The replica state maintained by a consumer server is used as the synchronization state indicator when it performs subsequent incremental synchronization with the provider server. It is also used as a provider-side synchronization state indicator when it functions as a secondary provider server in a cascading replication configuration. Since the consumer and provider state information are maintained in the same location within their respective databases, any consumer can be promoted to a provider (and vice versa) without any special actions.
So, by simply dropping the synchronization to the original provider, this node can become the new master provider. and this can be confirmed by comparing the contextCSN attributes on each DIT on each node to validate.