Non‑Disclosure & Security Agreement (NDSA)

Project: Silver Vein – Quantum‑Blockchain

Party Details

Disclosing Party

Receiving Party

On‑Chain Proofs

Compute a SHA‑256 hash in‑browser for timestamping or anchoring (e.g., OpenTimestamps, IPFS metadata).

Tip: After saving a PDF, you can hash the exact PDF bytes in your OS shell too (e.g., sha256sum file.pdf) and compare with this hash of the rendered text for a second integrity anchor.

1) Purpose

The Receiving Party may access Confidential Information to perform virtual assistant, bookkeeping, technical, research, and administrative services for the Silver Vein quantum‑blockchain initiative (the “Project”).

2) Definitions

“Confidential Information” includes, without limitation:

  • Quantum/crypto tech & R&D: algorithms, circuits, gate schedules, post‑quantum schemes, QKD/QDS concepts, consensus research, node topologies, protocol specs, test vectors, attack models, and performance data.
  • Keys & security artifacts: seed phrases, private keys, HSM configs, signing policies, derivation paths, multisig policies, KMS roles, and any credentials.
  • Business/financial: ledgers, wallet histories, token issuance plans, partner lists, pricing, investor communications, and forecasts.
  • Code & data: repositories, models, datasets, logs, dashboards, schemas, and documentation.
  • NDA metadata: document hashes, notarization proofs, and chain IDs.

Trade secrets remain trade secrets indefinitely.

3) Obligations

  • Use Confidential Information solely for the Purpose.
  • Do not disclose to third parties without written consent.
  • Apply reasonable, industry‑standard safeguards (device encryption, strong passwords, MFA).
  • Report any suspected breach within 24 hours (details, scope, mitigation steps).
  • Maintain access on a least‑privilege, need‑to‑know basis.

4) Quantum‑Blockchain Security (Key Handling)

  • No storing private keys or seed phrases in plaintext, screenshots, email, or shared docs.
  • Keys may be used only within approved secure signers/HSMs/hardware wallets; no local exports.
  • No pushing secrets to git/cloud; no clipboard managers; no screen recordings of secrets.
  • Logs/shared files must redact secrets.
  • On request, produce an access ledger (who/what/when) for sensitive resources.

5) Exclusions

Information is not confidential if it: (i) is public through no fault of Receiving Party; (ii) was rightfully known without duty; (iii) is independently developed; or (iv) must be disclosed by law (with prompt notice and cooperation to seek protective orders).

6) Public‑Chain Proofs (Notarization)

The Disclosing Party may publish hashes or on‑chain proofs of documents (including this NDSA) without revealing content, solely for timestamping/audit. The Receiving Party consents to such publication of hashes/proofs only.

7) Work Product & IP

Unless otherwise agreed in writing, all Work Product created for the Project is work‑made‑for‑hire or, where that concept doesn’t apply, is assigned to the Disclosing Party. The Receiving Party retains no rights except a limited internal license to perform the work during the engagement. Open‑source releases or publications require prior written approval.

8) Non‑Circumvention & Non‑Solicit

For 12 months after the last access to Confidential Information, the Receiving Party will not (a) circumvent the Disclosing Party to approach named investors/partners regarding substantially similar services/products; or (b) solicit Disclosing Party employees/contractors for competing engagements (general public recruiting is acceptable).

9) Return/Destruction

Upon request or termination, the Receiving Party will return or securely destroy all Confidential Information (including backups, caches, logs, and thumbnails). A brief destruction certificate may be requested.

10) Injunctive Relief

Unauthorized use or disclosure may cause irreparable harm; the Disclosing Party may seek injunctive relief in addition to other remedies.

11) Compliance

The Receiving Party will comply with applicable export controls and sanctions, and with privacy laws for any personal data processed.

12) Term & Survival

This NDSA lasts through the engagement and for five (5) years thereafter; trade‑secret obligations survive indefinitely.

13) Governing Law & Venue

This Agreement is governed by the laws of Saskatchewan, Canada, with venue in suitable courts located in Saskatchewan, without regard to conflict‑of‑laws rules.

14) Entire Agreement; Amendments

This document is the entire agreement on confidentiality and security. Amendments must be in a signed writing; e‑signatures are permitted.

Signatures

Sign with your mouse or finger. Your strokes are embedded as SVG paths for portability in the saved PDF.