The Storage Replicator Node and the verifier are the same node with different roles. It stores the owner's data for payment and verifies other replicators. The Storage Replicator Node can become the verifier when another Storage Replicator Node or the owner sends the start Drive verification transaction.
- The Storage Replicator Node searches and joins an active Drive contract. When the Storage Replicator Node wants to join the Drive, it makes the deposit equal to the Drive size.
- The Storage Replicator Node stores the Storage Director Node's files. When new data should be stored, the Storage Director Node's node sends actual data to the Storage Replicator Node nodes, and they keep that file until the Drive contract expiration or it is deleted.
- The Storage Replicator Node confirms that files are stored. The verifier continually checks that the Storage Replicator Node stores the correct and undamaged files. For it, the verifier uses the Challenge. The Storage Replicator Node, 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 Storage Replicator Node'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 Storage Replicator Node is to make a profit, it is interested in verifications.