Project facts

1. Operator and project

Project: Voiddeeds. Operator: VOIDS team. Official website: https://voiddeeds.xyz. Current product stage: testnet.

The VOIDS team is responsible for the website processing and operation described here. A project name, domain or deployment is not a regulatory status or certification. Publication of these documents makes no approval claim.

2. Treasury and privileged roles

The current deployment manifest identifies collection, deployer and treasury. The treasury receives mint proceeds, the 10% protocol toll share and rejected recipient allocations; royalties are declared separately. The testnet attestor and price publisher are trusted roles.

In this release the treasury and testnet attestor are the same configured address shown below. Each TestnetPriceOracle exposes its publisher on its network. The constructor fixes those role addresses; website configuration or terms acceptance cannot rotate them. Check the on-chain role getters as well as the release manifest when evaluating trust.

Treasury receipts include mint proceeds, the protocol toll portion and rejected recipient allocations. Those receipts are not a segregated pool held for NFT holders. The contract does not create a later claim for a recipient whose native payment was rejected. Royalty declarations are separate and depend on marketplace payment.

The operator maintains the website, its database and the trusted testnet services. Holders control their canonical space configuration with their wallets. Builders control their own applications and publication keys. None of these roles gives the operator a user's private key or a general power to spend assets from that wallet.

3. Current release facts

The collection caps supply at 1,111 Deeds, charges 0.001 test ETH per public mint and tracks one public mint per wallet without a reserved allocation. Its default toll is USD 0.01 and owner configuration accepts USD 0 to USD 2. The cap covers the Deed toll only. The configured deployment spans six test networks; only Sepolia is the canonical NFT network.

The collection metadata uses a shared image. The holder artwork licence is personal and commercial but non-exclusive and excludes project marks. Token ownership is not ownership of application code, the operator's business, real property or copyright. An activated remote owner snapshot can differ from current canonical ownership until refreshed.

4. How to assess evidence

Compare the canonical collection and each network address under Contracts with /api/release and the relevant explorer. Read treasury, attestor and publisher getters where applicable. A familiar contract name or ticker is insufficient. Match test results and source verification to those exact addresses and to the release being assessed.

Use transaction receipts and the relevant event types to distinguish a submitted request, a reverted execution, an actual recipient payment and a redirected amount. Website totals and cached snapshots are presentation data, not guaranteed balances or forecasts. Separate test activity from evidence of independent adoption or revenue.

Document publication and a content hash do not prove legal identity, assets under management, regulatory compliance or third-party acceptance. Historical signed receipts refer only to their original document release. Current website actions do not require an acknowledgment.

5. Conflicts, dependencies and limitations

The operator benefits from treasury payments and also maintains the testnet attestation and price services. This concentration of roles is a trust dependency. NFT holders benefit only from toll allocations that actually execute successfully under the effective network state; there is no minimum usage commitment or entitlement to app revenue.

Independent applications, RPCs, wallets, hosting and database services introduce separate operational and privacy dependencies. The documents make no claim of an independent security audit or guaranteed availability. Security boundaries, artwork rights and data handling are described in the Security, Licences, Deed conditions and Privacy documents.

Deployment references for this release

Collection

0x8f0b8eacacad43bd8b86b2305a20bb4a7007faba

Treasury

0x224385Bd4dBe4c5cb0ab469fe06ACdA734541A94