How ishagaikwad07/decentralized-real-estate works
Project type and purpose
• This is a single-contract Solidity project for managing the sale of a property on Ethereum.
• Purpose: allow a property owner to assign an agent, let a buyer purchase the property for exactly 11 ETH, automatically split payments (2 ETH to agent, 9 ETH to owner), and enable anyone to verify ownership.
File structure
• Only README.md is present, implying a single smart‐contract source file (not shown).
• No “frontend” or “backend” folders—interaction is done via an Ethereum wallet or IDE (e.g. Remix + MetaMask).
• No test suite or deployment scripts beyond typical Solidity instructions.
README for architecture clues
• Key functions:
• constructor (sets deployer as owner)
• assignAgent(address)
• buyHouse() payable
• getOwner() view
• Dependencies: Solidity ^0.8.0, Ethereum network, wallet (MetaMask).
Main components
• Property Owner (EOA deploying contract)
• Agent (EOA assigned by owner)
• Buyer (EOA calling buyHouse)
• Any Observer (calling getOwner)
• Nodes / Consensus
• Smart Contract bytecode & storage
• State variables: owner, agent, houseSold flag
• Functions: constructor, assignAgent, buyHouse, getOwner
Relationships and interactions
• Owner →[deploy]→ Smart Contract (constructor sets owner)
• Owner →[assignAgent(addr)]→ Smart Contract (writes agent)
• Buyer →[buyHouse() + 11 ETH]→ Smart Contract
• Contract →[2 ETH]→ Agent
• Contract →[9 ETH]→ Owner
• Contract updates owner := Buyer, houseSold := true
• Observer →[getOwner()]→ Smart Contract →[owner address]→ Observer
Architectural patterns & design principles
• Role-based access control (only owner can assign agent, agent cannot call buyHouse)
• On-chain automation of funds distribution
• Immutable transaction log (Ethereum ledger)
• Minimal external dependencies (no off-chain services)