---
# System prepended metadata

title: 'MetaNugs Confidentiality, IP Ownership Assignment, and Non-Compete'

---

# MetaNugs Confidentiality, IP Ownership Assignment, and Non-Compete

Hey team, Mackenzie writing this document on behalf of myself and Isaac.
The request for the Confidentiality and IP Ownership documents were surprising, we typically don't use documents like that for work engagements, but I understand the desire for documents like that and hope this document can work to fulfill that desire and help you feel comfortable and safe working with us.

## Confidentiality

### Confidentiality in Web3 / NFTs

Confidentiality is one of the standard business features that has not and likely will not translate to the new economy of Web3.

The core underlying technology, blockchain-based immutable decentralized public legders, make most information that would be protected by a confidentiality agreement necessarily open. 

This includes payment amounts as the decentralized public ledger records the transfer of assets, as well as timelines because the "work started" and "work completed" pay-outs are on chain. These transactions can be private, like your birth name doesn't have to be associated with the transaction, but the details need to be verifiable by any network user - this verifiability enables the common consensus that 'proves' the transaction happened.

Furthermore, with respect to NFTs, these tokens are also necessarily independently verifiable. All network users must be able to determine which image is associated with which index of the NFT Smart Contract, and we should assume all network users includes everyone. 

These two features make it difficult to scope confidentiality. One could imagine a cone-of-silence around a dev team leading up to a project's release date, but the nature of working with a DAO introduces further issues to implementing a confidentiality agreement.

Namely, RaidGuild is structured in a decentralized format - Isaac, or myself, are very capable of completing the scope of work, but we could go missing or fail in our duties and make RaidGuild as a brand responsible for the missed work. To prevent issues like that, RaidGuild has an internal policy that all project files are made available to the Guild as a whole so that, in the event that Isaac or myself fail to complete our duties, another member could pick up and complete the project. 

The strength of our organization is this labour interoperability, but in cases like confidentiality it introduces enforcement issues.

## IP Ownership Assignment

Again, there's a struggle with enforceability. Isaac and myself can promise to not leak art or code before anything had been announced, but we're not capable of enforcing a blanket cone of silence across the guild. 

IP also isn't generally enforceable in crypto - as the source code for smart contracts is independently verifiable by all network users, it's also instantly forkable. The images attached to the NFTs can be downloaded by any requester from IPFS without restriction - so that users may independently verify that the image attached to the NFT is what everyone agrees it to be.

