Software, art & marks

Voiddeeds | 2026-10-19.2 | https://voiddeeds.xyz/licenses

Different permissions apply to software, NFT artwork and project identity.

Software licence

Project-authored source in this checkout is provided under the MIT licence described in LICENSE, subject to file-level notices and third-party terms. Preserve copyright and licence notices. OpenZeppelin and vendored components retain their own applicable licences. Source verification or a public ABI is not a security warranty.

The MIT licence permits use, copying, modification, distribution, sublicensing and sale of covered software when its copyright and permission notices are preserved. It supplies the software without the warranties described in the licence, subject to rights that applicable law does not permit to be waived. The repository LICENSE and NOTICE specify the scope.

A dependency name, verified contract or reused interface does not replace that component's own licence. Review source-file headers, package licences and attribution before redistribution. The operator grants only permissions it holds; this notice does not represent a transfer of rights from an outside contributor.

Artwork and brand

The software licence does not license artwork, trait source assets or VOIDS/Voiddeeds marks. The current holder’s personal and commercial use of the NFT artwork is governed by the Deed conditions.

NFT ownership and copyright ownership are distinct. Holders receive the express personal and commercial artwork permissions in the Deed conditions while lawfully holding the token. Those permissions do not include exclusive rights to a shared collection image, source trait files, other works or the VOIDS and Voiddeeds identities.

You may accurately identify a token or describe an integration, but must not present your product as an official project product or imply endorsement. No licence here authorizes registration of project marks, confusingly similar branding or resale of a trademark licence. Uses outside the express artwork grant are not licensed by these documents.

Independent content and documentation

Application names, code, links and assets belong to their respective owners. Directory publication does not transfer those rights to Deed holders or other builders. Rights in a builder's submission are limited by the permission in the builder terms.

You may save the published documents as evidence of the release you reviewed. Historical document bundles remain available to verify existing receipts. Publication does not grant permission to reuse project artwork or marks outside the express licence. A content hash confirms bytes, not title to intellectual property.