Fund Verification: Service Terms

Effective date: 2026-03-23 · Last updated: 2026-10-10

1. Service description

Chain Daddy provides a fund verification service ("Fund Verification") for deal offers. Fund Verification checks the on-chain balance of a buyer's wallet at a specific block and creates a signed attestation of the result.

1.1. Fund Verification is required for certain offers. A buyout, project acquisition or collab offer cannot be created, on any chain, without a passing verification.

1.2. On Solana registrations Fund Verification reads the offering wallet's USDC, at Circle's USDC mint for that cluster, and Solana offers are priced in USDC only.

1.3. Passing verifications also set how much an account may have standing in offers at once: the sum of its verified balances from the last hour, times a multiple set by its plan, as described in the deals documentation.

2. Nature of verification

2.1. Fund Verification is a point-in-time balance check, not a guarantee, escrow, or hold on funds.

2.2. A passing verification confirms that, at a specific block number, the wallet held a balance meeting or exceeding the required threshold. It does not guarantee that funds will remain available at deal completion.

2.3. Verification results are informational. They do not constitute financial advice, credit checks, or underwriting.

2.4. A verification is valid for one hour. An offer submitted more than an hour after the balance was read is refused, and the buyer must verify again.

3. Attestation

3.1. When verification passes, Chain Daddy signs a cryptographic attestation containing the verification details. This attestation is:

• Stored off-chain in Chain Daddy's database and returned to the buyer
• Signed with a dedicated attestation key using the standard Ethereum personal-sign (EIP-191) envelope, so anyone holding the attestation payload and its signature can recover the signer address and compare it against Chain Daddy's fund-attestation signer

3.2. The attestation signer key is dedicated to fund verification and is separate from Chain Daddy's administrative keys.

3.3. The attestation commits to the buyer's wallet, the currency, the balance read, the required amount and percentage, the block number (on Solana, the slot), the chain id, a hash binding it to the offer, and a timestamp. The wallet is committed as a 20-byte address for an EVM chain (attestation version 1) or a 32-byte public key for Solana (attestation version 2). It does not commit to a block hash, so it does not bind the chain fork the balance was read on.

4. Limitations

4.1. Not an escrow or guarantee. Fund Verification does not lock, reserve, or custody any funds. The buyer retains full control of their wallet at all times.

4.2. Point-in-time only. Balances can change between verification and deal completion. Re-verification on an accepted deal provides updated information but is also point-in-time.

4.3. RPC dependency. Verification relies on third-party blockchain RPC providers. Temporary RPC outages may prevent verification. This is not a service failure.

4.4. Enforced by the API, not by a smart contract. The requirement in §1.1 is applied when the offer is created. No smart contract reads, stores, or enforces a fund verification, and no chain is consulted about one; a verification governs whether an offer may be made, not whether a deal may settle.

4.5. How much must be verified. A verification must cover the whole offer (for a collab, the whole liquidity it commits), except for an account on a paid Partner or Enterprise plan, which must cover 80% of it. Trials must cover the whole offer. The threshold is not a guarantee against price movements.

4.6. Unavailability. If Chain Daddy's verification store is not configured at all, offers are admitted without a proof rather than refused, and the condition is logged. If the store is configured but a lookup fails, the offer is refused and the buyer is asked to try again: a read failure is not treated as a pass.

5. Liability

5.1. Chain Daddy is not liable for deals where a verified buyer subsequently lacks sufficient funds. Fund Verification is a tool for informed decision-making, not a financial guarantee.

5.2. Chain Daddy is not liable for temporary unavailability of Fund Verification due to RPC provider outages, price API outages, or infrastructure maintenance.

5.3. The facilitation fee Chain Daddy charges on a deal is not a measure of liability for Fund Verification service errors. Liability is governed by the general Terms of Service.

6. Data handling

6.1. Verification records (wallet address, balance, attestation hash) are stored in Chain Daddy's database and retained for the lifetime of the associated deal.

6.2. No attestation hash is published on any blockchain. Fund Verification is off-chain end to end: the attestation and its hash live only in Chain Daddy's database, and deal settlement never carries them. A third party verifies an attestation off-chain, by recovering the EIP-191 signer as described in §3.1.

7. Availability

7.1. Fund Verification is provided as available, with no commitment to any level of availability, and may be unavailable for maintenance or any other reason without notice.

7.2. Offers of the types named in §1.1 cannot be submitted without a passing verification. On a buyout or a project acquisition, the registration's holder is shown, before accepting, what percentage of the offer the buyer proved they held, or that no proof was recorded. It is not presented as a guarantee, because a balance read is not one.