refer to EIP-7997

Author: bbjubjub2494

ERCS/erc-8270.md

@@ -22,7 +22,7 @@ In order to avoid fragmentation, there should be one standard wrapper contract.
 
 ## Specification
 
-The Vyper source code for the wrapper is included in the ERC repository, along with a Python script generating deployment parameters. It can be deployed trustlessly using a well-known deterministic deployment proxy. The system has two smart contracts: a minimal withdrawal receiver contract which is deployed using a proxy for each NFT, and the main contract which implements the [ERC-721](./eip-721.md) interface as well as the metadata and enumeration extensions.
+The Vyper source code for the wrapper is included in the ERC repository, along with a Python script generating deployment parameters. It can be deployed trustlessly to a predictable address using [EIP-7997](./eip-7997.md). The system has two smart contracts: a minimal withdrawal receiver contract which is deployed using a proxy for each NFT, and the main contract which implements the [ERC-721](./eip-721.md) interface as well as the metadata and enumeration extensions.
 
 The main contract allows anyone to mint a token associated with a specific validator public key. A proxy contract is immediately deployed to a unique withdrawal address. Holding the token confers full control over the withdrawal address and thus, once the validator is deployed, of its stake. More specifically, the main contract offers the following bespoke methods for the token holder to call:
 - `pullNativeBalance(tokenId, destination)` move the ether in the withdrawal address to the destination via a call.