← Back to pinkape

Transparency & donation policy

Version 0.2 · Pre-launch draft

1. What this policy covers

pinkape is an independent community meme project. It is not a charity, does not solicit donations from the public, and does not hold funds on anyone’s behalf. This document describes how the project handles revenue it controls, how it selects recipients, and how every act of giving is documented.

Purchasing or trading the token is a speculative transaction. It is not a donation, it is not tax-deductible, and no part of a purchase is described here as a gift made by the purchaser.

2. Language rules the project holds itself to

• “Intends to donate” is used for anything not yet transferred.
• “Donated” is used only after a completed transfer with published evidence.
• Token purchases, fees, taxes and treasury movements are never described as charitable donations.
• No medical outcome, tax deductibility, return, price floor or donation total is ever promised.
• No organization’s name, logo, testimonial or endorsement is used without written permission.

3. Defined revenue source

Only one explicitly named source enters the giving process. Nothing else — no market-making profit, no unrelated treasury movement, no third-party wallet — is presented as a donation source.

• Revenue source: [TO BE CONFIRMED]
• Project-controlled collection wallet(s): [TO BE CONFIRMED]
• Explicit exclusions: [TO BE CONFIRMED]

A percentage is not proof. pinkape will not state that any share of anything is donated unless every term in that sentence is defined here, the wallets are public, the exclusions are listed, and the statement is operationally true at the moment it is made.

4. Gross versus net calculation

The donated amount is calculated as follows: [TO BE CONFIRMED — state whether the figure is gross or net of the costs below, and give the formula.]

Costs deducted before transfer

• Network fees: [TO BE CONFIRMED]
• Swap or conversion costs, including slippage: [TO BE CONFIRMED]
• Off-ramp, banking or payment-processor fees: [TO BE CONFIRMED]
• Any other deduction: [TO BE CONFIRMED]

Every deduction applied to a transfer is reported in that transfer’s ledger entry, in the notes field. Undisclosed deductions are not permitted.

5. Valuation

The value recorded for a transfer is its value at the moment the transfer is signed, taken from a single named price source linked in the ledger entry. Later price movement never changes a published record.

6. The five steps

Every act of giving follows the same order, and the public ledger shows which step it has reached.

1. Announce

   Publish the intended recipient, amount or calculation method, source wallet, timeline and conditions before making a transfer. The record enters the ledger as proposed.

2. Verify

   Confirm the recipient’s official receiving method through its own published channels. A wallet address posted by a third party, in a reply, or in a group chat is never treated as legitimate.

   When the community is asked to give directly, the project links only to donation pages or receiving instructions controlled and publicly confirmed by the selected breast cancer research organization.

3. Transfer

   Send from the disclosed project wallet and publish the transaction hash. The record becomes pending, then confirmed once the network or payment record confirms it.

4. Receipt

   Publish the recipient’s official receipt or acknowledgement. Only then does the record become receipt published. A record is never marked complete before the evidence exists.

5. Reconcile

   Explain network fees, conversion differences, failed transfers, refunds, and any variance between the announced and the received amount.

7. What every ledger entry must show

• Status — proposed, pending, confirmed, or receipt published.
• Amount — exact asset and amount transferred.
• Sender — a public, project-controlled wallet.
• Recipient — exact legal name, and a destination confirmed by the recipient organization.
• Transaction — a clickable block-explorer link.
• Receipt — the original receipt or acknowledgement.
• Dates — UTC transfer date and UTC receipt date.
• Notes — fees, conversion, and any material discrepancy.

Summary figures on the site count only records at confirmed or receipt published. Proposed and pending entries are visible but never counted as completed giving.

8. Custody and authorized signers

• Custody model: [TO BE CONFIRMED — e.g. multisig, threshold, single signer]
• Authorized signers: [TO BE CONFIRMED]
• Process for changing signers: [TO BE CONFIRMED]

Project wallets are disclosed so anyone can inspect their history independently of this site.

9. Recipient selection

A recipient is eligible only if it is a legitimate breast cancer research or care organization, identified by its exact legal name, and only if it has confirmed, through its own channels, that it accepts the method of payment being used.

• Selection process: [TO BE CONFIRMED]
• Current recipient(s): [TO BE CONFIRMED]

Linking to an organization, or giving to it, creates no partnership, sponsorship or endorsement. pinkape will not place any organization’s logo beside its own, or describe it as a partner, without written authorization from that organization.

10. If a recipient declines crypto-related funds

Some organizations do not accept cryptocurrency, or decline funds connected to token projects. If that happens, pinkape will:

• publish the fact that the funds were declined, with the date;
• hold the funds in the disclosed wallet without spending them on anything else;
• select an alternative eligible recipient under section 9 and publish that decision; and
• record the completed transfer to the alternative recipient in the ledger.

11. Corrections and failed transfers

Ledger entries are never silently edited or deleted. If a transfer fails, is reversed, or a record is found to be wrong:

• the original entry stays visible;
• a dated correction note is attached explaining what changed and why;
• summary figures are recalculated from corrected records; and
• if the correction reduces a previously reported total, that is stated plainly.

12. Contact

Questions about this policy can be sent to the contact address published at launch.