diff --git a/SNIPS/snip-16.md b/SNIPS/snip-16.md
index a6a95c5..0ec227a 100644
--- a/SNIPS/snip-16.md
+++ b/SNIPS/snip-16.md
@@ -3,8 +3,8 @@ snip: 16
 title: Deprecation of transaction versions 0,1,2
 description: This SNIP proposes to deprecate transaction versions 0,1,2 and stop support for them around the end of Q1 of 2025.
 author: Ilia Volokh <iliav@starkware.co>
-discussions-to: 
-status: Draft
+discussions-to: https://community.starknet.io/t/snip-16-deprecation-of-transaction-versions-0-1-2/114443
+status: Review
 type: Standards Track
 category: Core
 created: 2024-07-02
@@ -25,7 +25,7 @@ Transaction versions 0,1,2 only support fee payment in ETH. Moreover, they have
 
 ## Proposal
 
-We propose for the sequencer to stop support for transaction versions 0,1,2 in an upcoming version in preparation for integrating the mempool and fee market, which is expected to happen within 6-8 months.
+We propose for the sequencer to stop support for transaction versions 0,1,2 in an upcoming version in preparation for integrating the mempool and fee market, which is expected to happen within 6-8 months. Concretely, we propose for these transaction versions to be rejected at the gateways to the mempool.
 
 To facilitate continuation of fee payment in ETH, we propose to adopt paymasters. The decision between applicative paymasters such as the one by AVNU or protocol-level paymasters will be left to applications/wallets. (A detailed SNIP for a protocol-level paymaster is in the works.)
 
diff --git a/SNIPS/snip-paymaster b/SNIPS/snip-paymaster
new file mode 100644
index 0000000..966c758
--- /dev/null
+++ b/SNIPS/snip-paymaster
@@ -0,0 +1,38 @@
+---
+snip: 
+title: Protocol-level Paymaster
+description: This SNIP proposes a design for a protocol-level paymaster contract and semantics for the 'paymaster' field in v3 transactions.
+author: Ilia Volokh <iliav@starkware.co>
+discussions-to: 
+status: Draft
+type: Standards Track
+category: Core
+created: 2024-08-12
+---
+
+## Simple Summary
+
+
+## Motivation
+
+
+## Proposal
+
+
+## Rationale
+
+
+## Drawbacks
+
+
+## Alternatives
+
+
+## Backwards Compatibility
+
+
+## Security Considerations
+
+
+## Copyright
+