Why do I need to connect my wallet?
When you sign the signature request to connect your wallet, two things happen:
We can read your Ethereum address (
0x...). If you are a landowner, we can determine which parcels or estates you own.
- We can confirm that you control the wallet and therefore have the right and ability to rent out the LAND tokens you list (if you are a land owner) or that you are the one involved in a rental transaction (if you are a tenant).
How can I be sure this is safe?
As a web3 user, it is your responsibility to educate yourself about basic functionality of the web3 ecosystem so you can use these tools effectively and protect yourself from scammers and other bad actors.
First, it is necessary to understand the difference between a signature request and a transaction request
A signature request is used to cryptographically prove that the person signing a given request is the owner of the address they are signing with. This is a sophisticated form of consent which allows you to prove your identity without ever revealing it and it is a fundamental basis of web3.
A signature request using the
specification never exposes your private key or poses a privacy risk -
it is the web3 equivalent of showing your passport at the airport. It is
simply read-only verification of identity.
A transaction request is more complex - it handles sending ETH or tokens, creating or interacting with a smart contract, or other operations which can be obfuscated or impersonated by bad actors.
MetaMask makes it easy to differentiate between these two types of requests and also gives tools to look more deeply into transaction requests to ensure that you always know what you are signing.
A signature request in MetaMask
A transaction request in MetaMask
Signing Data: A Brief History
An overview of data signing and how it is implemented in MetaMask
Wallet Signature Request Messages
An excellent explanation of the "why" and "how" of signature requests
The basics of transactions from the MetaMask documentation