The \"company\" verifies that a particular amount of data has been deposited in the contract. The wallet keys are self-contained wallets . One thing of note: if no data is sent previously by the publisher, the scanner will auction off the data and that publisher will be refunded as the scanner will not be able to publish his/her data. Essentially, a \"zero-day\" vulnerability will be exploited and this scanner will profit from it, even though the first scanner to exploit the zero-day vulnerability will remain anonymous. The reason for this is that the data was not deposited with the scanner but with a test-wallet owned by the scanner. This is a way of preserving anonymity and protecting the scanner.
After a successful security audit of the Web you'll be asked to validate that the correct data have been published to your Smart-Contract. This is a two-way key agreement protocol. The validator sends a 1-of-1 randomly-generated proof, via RLPx protocol. The author then responds with a valid msgID and proof that it knows the author along with a timestamp. The proof is signed using an ECC curve derived from the public key of the author and a randomly-generated curve point. The validator trusts the author and will send this signed proof to the author. The author after validating the proof will sign off using the author's private key.
The Safe3 network uses an incentive model where each wallet which has not yet scanned any website that a smart contract offers it a payout of 0.05% per website. The payout is made in the form of 5 MainNet Transactions and is paid out in Ethereum. 7211a4ac4a