Wallet Address Change

Effective Date: This protocol is effective as of February 2026. Wallet change requests submitted prior to this date were processed under the previous regime and are not subject to these requirements if already completed.

---

Overview: Project plans can evolve, and Catalyst accounts for these changes through a formal Change Request process. To ensure approval, your CR must be well-argued with adequate supporting information.

⚖️ Grantee Responsibility Disclaimer

It is the sole responsibility of the Grantees to ensure that all internal governance approvals are in place before a request is submitted. Catalyst follows its established verification protocols but does not arbitrate internal team disputes.

Wallet Accuracy: The Grantee bears full responsibility for the accuracy of any provided wallet addresses. Catalyst is not liable for funds sent to an incorrect or inaccessible address provided by the grantee.

---

Public Core Requirements (Apply to All Grantees)

1. Submit Only Through Catalyst Helpdesk from an Authorized Email: The ticket must be created/submitted using an email address explicitly listed as authorized in your grantee profile.

   1. Include: Grant ID, project name, current wallet address (with blockchain/network, e.g., Cardano mainnet), proposed new wallet address, and reason for the change.

   2. Unlisted emails will result in automatic rejection.

   3. Every project ID must have its own unique CR request. The Catalyst program does not accept bulk wallet address changes.

2. Provide a Formal Approval Document: Submit a single PDF titled "Wallet Address Change Authorization – Grant [Grant ID]", dated, with explicit details of current/new addresses, blockchain/network, and reason. This document must be signed with authenticated signatures (details in step 3).

3. Authenticate Signatures for Credibility

   1. Required – choose one - Preferred or Alternative signature verification methods):

      1. Preferred: Verifiable digital signatures using one of the recommended tools (e.g., DocuSign, Adobe Sign, Inkless, OpenSign, DocuSeal, Documenso, Zoho Sign, etc.). All signers' emails must match existing KYC records on file with Catalyst for cross-referencing; unknown signatures without a verified profile are not acceptable. Attach the full authentication trail (e.g., audit logs, completion certificate with timestamps, IP/access records, and signer details matching known contacts) as a separate PDF. Partial proofs like just an envelope ID are insufficient.

      2. Alternative: Notarized signatures (via accredited in-person or remote online services).

      3. Note: Grantees are responsible for ensuring signatures are legally binding and compliant with requirements applicable to your jurisdiction).

   2. Supplementary: Public announcement of the exact statement on official project channels (provide links).

4. Expect Proactive Confirmation Outreach: After submission, the Catalyst team will directly contact you (and all team members, if applicable) via on-file channels (e.g., Zendesk follow-up or video call) to confirm the request. Respond promptly to avoid delays. Changes activate only after official Zendesk confirmation following this verification.

5. Demonstrate Access to the New Wallet: As part of the change request, you must prove access to the new wallet via a small test transaction. The Catalyst team will provide instructions and coordinate this step after initial authentication.

6. Completion of the Request: Once all steps are successfully completed, the wallet change is finalized and confirmed via Zendesk. Wallet addresses (past and present) are all public information by default.

---

Specific Requirements by Grantee Type

The signature and verification process is determined by your project’s legal and team structure. Failure to provide the correct signatures will result in the immediate rejection of your Change Request.

Path A: Single-Person or Sole-Proprietor

Use this if you are an individual contributor or the sole majority owner of the business.

• Signature Requirements: Only your signature is required.

• Authentication: The document must be signed via a recommended digital tool (providing a full audit trail) or be notarized. The signature must match existing Catalyst KYC records.

• ⚠️ Security Precaution (Cooldown Period): Once a Wallet Change request is received, your payment release cycle will be put temporarily on hold. By default, your project will skip at least one payment cycle (every two weeks) before disbursements are reinstated.

• Wallet Policy: Single-key wallets are acceptable.

• Communication: No additional CCs are required. The Catalyst team will reach out directly to you for final confirmation.

---

Path B: Project Partners (Co-Proposers) or Shared-Control Entities

Use this if your project has multiple stakeholders or if your business has no single majority shareholder.

• Signature Requirements:

  • For Multiple Co-Proposers: Signatures are required from all stakeholders. Specifically, the Ultimate Beneficial Owners (UBOs) representing the majority controlling interest across each co-proposing entity must sign.

  • For Organizations (No Co-proposers): If the company has no single majority shareholder, all UBOs representing the majority controlling interest must sign.

• Important Constraints:

  • Power of Attorney: A single individual acting under Power of Attorney is not sufficient; UBOs must sign directly.

  • KYC Compliance: All signatories must have an active KYC on record. If records are missing, the Catalyst team will perform additional KYC/KYB checks before processing the request.

• ⚠️ Security Precaution (Cooldown Period): Once a Wallet Change request is received, your payment release cycle will be put temporarily on hold. By default, your project will skip at least one payment cycle (every two weeks) before disbursements are reinstated.

• Wallet Policy: We strongly recommend using a multisig wallet to prevent unilateral control over project funds.

• Communication: You must CC all known co-proposers on the helpdesk ticket. The Catalyst team will contact all signers and stakeholders directly for individual confirmations.

---

Quick-Reference Comparison

Requirement	Path A: Single/Sole Owner	Path B: Teams/Co-Proposers
Primary Signers	Lead Grantee	Majority UBOs across all entities
Power of Attorney	N/A	Not Accepted (UBOs must sign)
Wallet Change Cooldown	Min. 2 weeks (1 payment cycle)	Min. 2 weeks (1 payment cycle)
Authentication	Must match KYC record	Must match KYC records
Email Protocol	Direct submission	CC all co-proposers