From 00d40f5be9c373c75c3ff93b80cbbc38f0d21aff Mon Sep 17 00:00:00 2001
From: kleos <36254493+amlitio@users.noreply.github.com>
Date: Wed, 11 Dec 2024 17:08:27 -0500
Subject: [PATCH] Create project_name-milestone_number.md

---
 deliveries/project_name-milestone_number.md | 73 +++++++++++++++++++++
 1 file changed, 73 insertions(+)
 create mode 100644 deliveries/project_name-milestone_number.md

diff --git a/deliveries/project_name-milestone_number.md b/deliveries/project_name-milestone_number.md
new file mode 100644
index 0000000..554c792
--- /dev/null
+++ b/deliveries/project_name-milestone_number.md
@@ -0,0 +1,73 @@
+# JAM Milestone Delivery 
+
+> Don't remove any of the mandatory parts presented in bold letters or as headlines! Lines starting with >, such as this one, can be removed.
+
+
+## Company/Team details
+
+>Please provide all the required information below.
+
+- Company/Team's name:
+- Company/Team's GitHub:
+- Programming language and language set: 
+- Link/s to previous delivery/ies: 
+
+
+## Documentation checklist
+
+>Please check the boxes to confirm that you have provided all the required documentation, providing direct links whenever possible. **DO NOT** include links to confidential or private documents.
+
+>Chose the relevant option(s) (e.g. Option A | Option B | etc.) and delete the rest.
+
+We declare that:
+
+- [ ] we have completed **the Web3 Foundation KYC/KYB process**.
+- [ ] we used **a clear and permissive open-source license**.
+- [ ] we submitted **a clear Git history and public, credibly timestamped commits** | **code developed in private, with commit hashes placed, in a timely fashion, on a major public blockchain**.
+- [ ] we used third party libraries for: **cryptographic primitives** (e.g. erasure-coding, Bandersnatch, Ed25519) | **codecs** (e.g. SCALE) | **networking** (e.g. QUIC).
+- [ ] we provided **Gas, trie/DB, signature-verification, and availability (EC/DB) performance tests** to be run on standard hardware.
+- [ ] we viewed the following **JAM implementation code** before | during our implementation.
+- [ ] we have not | have had private conversations with **other | the following implementers**.
+- [ ] we have not | have had **concerns about collusion**.
+- [ ] we agree to a recorded interview by the *Polkadot Technical Fellowship* on any matter arising from this milestone submission.
+- [ ] we understand that this milestone submission will need to be ratified with an on-chain remark by the *Polkadot Technical Fellowship* before it can be merged.
+
+
+
+## Context
+
+>Please present your rationale for the completion of this milestone by connecting the deliverables and describing their purpose.
+
+
+## Deliverables
+
+>Please check the relevant box to indicate which milestone you are delivering.
+
+- [ ] 1. IMPORTER: State-transitioning conformance tests pass and can import blocks.
+- [ ] 2. AUTHOR: Fully conformant and can produce blocks (including networking, off-chain).
+- [ ] 3. HALF-SPEED: Conformance and Kusama-level performance (including PVM implementation).
+- [ ] 4. FULL-SPEED: Conformance and Polkadot-level performance (including PVM implementation).
+- [ ] 5. SECURE: Fully audited.
+
+
+>Please provide a list of all deliverables for the milestone and include links to the actual deliverables.
+
+>Ideally all links inside the table below should include a commit hash, which will be used for testing. If you don't provide a commit hash, we will work off the default branch of your repository. Thus, if you plan on continuing work after delivery, we suggest you create a separate branch for either the delivery or your continuing work.
+
+>If there is anything particular about any of the deliverables we or a future reader should know, use the respective Notes column.
+
+| Number	| Deliverable	| Link	 | Notes |
+|---------|-------------|--------|-------|
+|1.	      |...	        | ...	   |...    |
+|2.	      |...	        | ...	   |...    |
+|3.	      |...	        | ...	   |...    |
+|4.	      |...	        | ...	   |...    |
+|5.	      |...	        | ...	   |...    |
+
+
+## Additional Information
+
+>Provide any relevant comments on the milestone submission that you would like to share with us.
+
+
+