Requirements To Be Contacted

A set of attributes that a requestor must have in order to be able to contact a requestee. Each set of RTBC are associated with an attribute of the requestee.

They are to aid entrepreneurship. Assume Alice has skills in marketing, but she doesn't want to be contacted by people who are not ready for her to work effectively with. She can set requirements-to-be-contacted, so that Bob, if he wants to reach out, will need to have a business plan, and $600 available to spend, for example.

The attributes that Alice lists can, but not must (they should), have a requirement that they be signed by someone Alice trusts to verify such a thing. For a monetary requirement, that would require Bob, the requestor, to have an attribute which referred to a UTXO, and a reference to a signature of some document, such that Alice can use the public key of that UTXO to verify the signature, and be sure that Bob controls that UTXO.

The person Alice is listing to sign off on a requirement, lets call them Dave, has an opportunity to make some money, depending on the nature of what he is cosigning on. And such requirements are the essence of an idea about standardizing work, defining things necessary to be done before a specialist you find through this app can jump in and be effective.

See fee-to-be-contacted.