Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Complete README #33

Merged
merged 20 commits into from
Aug 2, 2022
Merged

chore: Complete README #33

merged 20 commits into from
Aug 2, 2022

Conversation

fzavalia
Copy link
Collaborator

No description provided.

@fzavalia fzavalia marked this pull request as ready for review August 1, 2022 12:26
Copy link

@nicosantangelo nicosantangelo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome

README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
fzavalia and others added 13 commits August 1, 2022 20:07
Co-authored-by: Nicolas Santangelo <santangelonicolas@gmail.com>
Co-authored-by: Nicolas Santangelo <santangelonicolas@gmail.com>
Co-authored-by: Nicolas Santangelo <santangelonicolas@gmail.com>
Co-authored-by: Nicolas Santangelo <santangelonicolas@gmail.com>
Co-authored-by: Nicolas Santangelo <santangelonicolas@gmail.com>
Co-authored-by: Nicolas Santangelo <santangelonicolas@gmail.com>
Co-authored-by: Nicolas Santangelo <santangelonicolas@gmail.com>
Co-authored-by: Nicolas Santangelo <santangelonicolas@gmail.com>
Co-authored-by: Nicolas Santangelo <santangelonicolas@gmail.com>
Co-authored-by: Nicolas Santangelo <santangelonicolas@gmail.com>
Co-authored-by: Nicolas Santangelo <santangelonicolas@gmail.com>
Co-authored-by: Nicolas Santangelo <santangelonicolas@gmail.com>
Copy link

@nicosantangelo nicosantangelo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@fzavalia fzavalia merged commit 9f92af7 into main Aug 2, 2022
@fzavalia fzavalia deleted the chore/complete-readme branch August 2, 2022 18:09
- rentalDays: The amount of days I want to rent this LAND. It has to be in range between the min and max days of the index I choose or else it fails.
- fingerprint: In the case of an Estate, this indicates the fingerprint it should have when renting it to me. This prevents the owner to front run me and remove LAND from it before renting it.

If everything is correct, MANA equivalent to the pricePerDay index I've selected, times the rentalDays I provided will be transfered from my address to the lessor (and a fee to the DAO) and the provided operator will start being able to deploy scenes to that LAND.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fee to the FeeCollector, the DAO is an agent that may change.


There are various ways of signing these conditions. One of them can be achieved by using ethers as seen in the [./test/utlils/rentals.ts](https://github.com/decentraland/rentals-contract/blob/main/test/utils/rentals.ts#L81) utility file.

Once both the signature and the listings conditions are ready, I, or whichever off-chain system handling this, can store them to make them
Copy link
Contributor

@nachomazzara nachomazzara Aug 3, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the offer conditions?


- offer: [Offer](#offer-struct) containing the conditions and the signature of the offer.

2 - Sending the LAND to the Rentals cotract via LAND's `safeTransferFrom` function
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cotract typo. => Contract


## Extending a rental

BEFORE a rental is over, a new listing or offer for the LAND can be accepted as long as the lessor and tenant in said offer/listing are the same.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we explain how to do that by using the target parameter in the Listing struct?


The asset nonce is always bumped for both the lessor and the tenant once a rent is initialized to prevent any other listings or offers with the current nonce to be usable. This is a safety meassure to ensure that the least amount of usable signatures are available off-chain in the case of a signature storage breach.

In the case of the signer nonce, imagine that I signed a lot of listings or offers with the current nonce but for some reason I don't trust the way they are stored, I could just call the asset nonce bump to invalidate them all at once.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the case of the contract nonce? Should we need to add it too?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants