Joshua

Here is the [EIP-4907](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-4907.md) to enable renting NFTs. This can be a reference for basic NFTs then we can extend the logic

This is to update the listing if it exists. We could change this to a `try_mutate` instead on the `ListedNfts` to prevent the temporary removal from storage.

Agreed we can submit this as a simple refactor.

This can also start the discussion on `Logic` for properties.

That could be beneficial to reduce storage. I was thinking about how to utilize `#[pallet::hooks]` and clean stale listings every certain number of Blocks. I did something similar with being...

I believe we want to reduce the amount of reads and writes to storage and managing this for 3 separate storage could get complicated to manage. This would also create...

Do we prevent this scenario when sending/minting NFTs to NFTs? If we are able to get a `Budget` from `lookup_root_owner`, could we prevent this scenario from happening? 

The `Weights` are now a struct with a `u64` field named `ref_time`. I think some of the build errors can be fixed by using the `Weights::from_ref_time(u64)`. Here is the file...

> Need to remove the commented out code. I'll run this in my environment. Do the integration tests pass, as well? > > Another thought is on downstream implementations. These...

We can check the `Budget` trait defined here. This will allow for the caller to create a `Budget` for a call and define a `Value` for the number of calls...