NEP-452 (linkdrop): Change status to "final" + add it to README.md. (#…

…543)

Make the NEP-452 present in the NEPs list.
Change its status to "final".

README.md

@@ -30,6 +30,7 @@ Changes to the protocol specification and standards are called NEAR Enhancement
 | [0393](https://github.com/near/NEPs/blob/master/neps/nep-0393.md) | Sould Bound Token (SBT)                  | @robert-zaremba                              | Final      |
 | [0399](https://github.com/near/NEPs/blob/master/neps/nep-0399.md) | Flat Storage                             | @Longarithm @mzhangmzz                       | Final     |
 | [0448](https://github.com/near/NEPs/blob/master/neps/nep-0448.md) | Zero-balance Accounts                    | @bowenwang1996                               | Final      |
+| [0452](https://github.com/near/NEPs/blob/master/neps/nep-0452.md) | Linkdrop Standard                        | @benkurrek @miyachi                          | Final      |
 | [0455](https://github.com/near/NEPs/blob/master/neps/nep-0455.md) | Parameter Compute Costs                  | @akashin @jakmeier                           | Final      |
 | [0514](https://github.com/near/NEPs/blob/master/neps/nep-0514.md) | Fewer Block Producer Seats in `testnet`  | @nikurt                                      | Final      |
 

neps/nep-0452.md

@@ -3,7 +3,7 @@ NEP: 452
 Title: Linkdrop Standard
 Author: Ben Kurrek <[email protected]>, Ken Miyachi <[email protected]>
 DiscussionsTo: https://gov.near.org/t/official-linkdrop-standard/32463/1
-Status: Draft
+Status: Final
 Type: Standards Track
 Category: Contract
 Version: 1.0.0
@@ -194,7 +194,7 @@ Below are some references for linkdrop contracts.
 
    Another important security implication of linkdrop creation is to ensure that only one key is mapped to a set of assets at any given time. Externally, assets such as FTs, and NFTs belong to the overall linkdrop contract account rather than a specific access key. It is important to ensure that specific keys can only claim assets that they are mapped to.
 
-2. Linkdrop Key Management  
+2. Linkdrop Key Management
    Key management is a critical safety component of linkdrops. The linkdrop contract should implement a key management strategy for keys such that a reentrancy attack does not occur. For example, one strategy may be to "lock" or mark a key as "in transfer" such that it cannot be used again until the transfer is complete.
 
 3. Asset Refunds & Failed Claims