A key component of the EngineerDAO platform is enabling anonymous and psuedo-anonymous work. Although these arrangements will not fit every use case, we feel the option is critical to our value preposition. We do not enforce specific rules around working relationships. We offer the capability and tools to conduct business in a way that is compatible for both supplier and engineer.

<aside> 💡 It is entirely the responsibility of the contract participants to comply with any relevant laws in their jurisdictions, including but not limited to employment eligibility, taxes, and reporting.

</aside>

Types of Work 🧐

Let's dig into some common types of work. We will make these options available as contract properties, and may add new types in the future. If you have a different working relationship requirement, we recommend you list it in the contract description.

Strict Anonymous

The strict anonymous relationship demands that great care be taken at each interaction to preserve the anonymity of one or both parties. Each party will be identified by their ERC-20 wallet address and optionally a pseudonym. This relationship may be desirable when working on projects that draw negative public attention (ie. an election campaign website) or experimental DeFi projects that could face regulatory scrutiny in the future.

<aside> ❗ Illegal content or contract objectives will never be tolerated on the platform. We reject the assertion that anonymity is only useful for illegal activity.

</aside>

Although the specifics will be more nuanced, here are some anticipated considerations when working in this way:

• PII, device, and location data should be stripped from any files prior to transfer
• Identifying information should be stripped from the contract instructions and supporting materials.
  • ie. A Figma comp might contain a non-descript box in place of the company logo.
• Anonymous email should be used, if email communication is necessary (ie. ProtonMail)
• Encrypted chat may be used
• Ethereal demo environments may be created for a short window and destroyed after their use expires
• Post-contract communication may be limited to in-contact messaging on EngineerDAO
• Special purpose, short-lived wallets may be created for the primary purpose of interacting with the contract

Anonymous

Anonymous contracts notate the desire and requirement for both parties to remain anonymous. In this relationship, parties agree not to seek personally-identifying details. However, the standard for retaining anonymity is less stringent than "strict anonymous". For example, both parties may use the same Discord and Google Drive that they use for other projects.

Anonymous contracts generally convey the desire to minimize the human relationship element of a contract. Communication is limited to clarifying technical questions and discussion. Real names are not used. Suppliers will generally take care to strip identifying information from the contract description.

These types of contracts will require more up-front and post-contract work to "de-anonymize" and integrate the work. For example, a React UI built via an anonymous contract will likely need the logos replaced, company branding, and real content inserted.

Semi-Anonymous