## implementation of a draft of an EIP for rental NFTs with rights management


<br>

* please refer to [this link](eip-9999.md) for the proposal, which follows the guidelines from the [ethereum foundation](https://github.com/ethereum/EIPs).
* a reference implementation (in [foundry](https://book.getfoundry.sh/)) can be found [here](eip-9999-test/).
* finally, you can check that the EIP is well-formatted by running EF's EIP validator locally:

<br>

```shell
> cargo install eipv
> eipv

draft: 1, review: 0, last_call: 0, final: 0, stagnant: 0, withdrawn: 0, living: 0
valid: 1, invalid: 0
```

<br>

----

### references


* [EF's list of ERCs](https://eips.ethereum.org/erc)
* [EIP-5218, NFT rights management](https://eips.ethereum.org/EIPS/eip-5218)
* [ERC-4907, Rental NFT, an extension of EIP-721](https://eips.ethereum.org/EIPS/eip-4907)
* [the token-bound license, by james grimmelmann](https://eips.ethereum.org/assets/eip-5218/ic3license/ic3license.pdf)
* [how do EIP numbers get assigned?](https://ethereum-magicians.org/t/how-do-eip-numbers-get-assigned/9079/4)
* [difference between ERC and EIP](https://ethereum.stackexchange.com/questions/44847/difference-and-relationship-if-any-between-erc-and-eip)
* [running the EIP validator locally](https://github.com/ethereum/EIPs/tree/master?tab=readme-ov-file)