The replicator and the verifier are the same node with different roles. It stores the owner's data for payment and verifies other replicators. The replicator can become the verifier when another replicator or the owner sends the start Drive verification transaction.
- The replicator searches and joins an active Drive contract. When the replicator wants to join the Drive, it makes the deposit equal to the Drive size.
- The replicator stores the owner's files. When new data should be stored, the owner's node sends actual data to the replicator nodes, and they keep that file until the Drive contract expiration or it is deleted.
- The replicator confirms that files are stored. The verifier continually checks that the replicator stores the correct and undamaged files. For it, the verifier uses the Challenge. The replicator, in this case, should generate tags using the algorithm and actual file data.
The verifier is checking that data is untouched and safe. It uses the Challenge to control replicators against corruption and loss of the owner's data. The verifier begins verification when the Drive verification transaction starts. According to the verification algorithm, a verifier that failed verification loses its deposit. That deposit will be divided between replicators. Since the main goal of any replicator is to make a profit, it is interested in verifications.