Small Grant: Landrush

Introduction

Project Name: Landrush

Name of the organization or individual submitting the proposal: Landrush Ltd

Team Background

The Landrush technical team brings a combined 17 years of hands-on engineering and product development experience directly relevant to building scalable mobile marketplace applications and decentralized infrastructure integrations.

All members are publicly listed on the Landrush GitHub organization and maintain active professional profiles.

Core Team

Lead Full-Stack Developer — Arinze Obasi

LinkedIn: https://www.linkedin.com/in/arinze-obasi-161618233/

Full stack Developer — Unsteady Teddy

GitHub: Raphaelj1 (Raphael James) · GitHub

Backend Developer — Ubongabasi Jerome

LinkedIn: https://linkedin.com/in/ubongabasi-jerome

Engineering Intern — Godspower Ufot

LinkedIn: https://www.linkedin.com/in/godspower-ufot-1b0967363

Product Designer — Aniebiet Peter

LinkedIn: https://www.linkedin.com/in/ani

ebiet-peter-5ba80323a

Describe your project.

Landing page: https://www.landrushafrica.com/

Landrush is a land-discovery mobile application for Android and iOS. The platform connects verified landowners, agents, surveyors, agricultural stakeholders, and land seekers across three marketplace categories: leasing, buying, and distress sales.

The application is designed around the Sia Quickstart model, putting the user first: all land imagery, ownership documentation, verification attestations, and user-generated media are encrypted on the user’s device before any data ever leaves the phone. The mobile application then uses the Sia SDK to upload these encrypted blobs directly to the Sia network, with indexd operating as the full renter layer responsible for storage contract management, host negotiation, redundancy, and retrieval. A minimal Go backend coordinates only authentication, lightweight non-sensitive metadata for discovery and inspection scheduling, and verification attestations. It never stores encryption keys, never handles plaintext land media, and cannot access user documents.

Landrush does not broker transactions or process payments. Instead, it provides a transparent infrastructure for land discovery, document integrity verification, inspection scheduling, and trust signaling through a multi-layer verification system.

Users discover land through:

  • Native mobile map visualization

  • Geospatial search and filtering

  • Inspection scheduling workflows

  • Verification badges and trust tiers

By combining client-side encryption, direct SDK-to-network uploads, and a minimal zero-knowledge backend, Landrush reduces fraud risks, improves transparency, and advances genuine user-owned data within African property markets.

How Does the Project Serve the Foundation’s Mission of User-Owned Data?

Landrush directly advances the mission of the Sia Foundation by applying decentralized storage to a high-impact real-world problem: land access, trust, and fraud in African property markets.

Today, land records and property listing media are commonly stored on centralized servers controlled by governments, agencies, or proprietary platforms. This creates several vulnerabilities:

  • Data manipulation

  • Single points of failure

  • Vendor lock-in

  • Censorship risks

  • Poor transparency

  • Unauthorized modification of records

Landrush addresses these issues by ensuring that sensitive data never touches a centralized server in plaintext. Using the Sia SDK, all photographs, videos, and ownership documents are encrypted client-side with AES-256-GCM using keys derived from the user’s own passphrase via PBKDF2. Only the ciphertext is uploaded to the Sia network, with indexd acting as the full renter layer that manages storage contracts, host negotiation, and redundancy. The Landrush backend is deliberately minimal and zero-knowledge: it coordinates authentication, general discovery metadata, and inspection appointments, but it never possesses decryption keys, never stores plaintext media, and cannot read ownership documents even if compelled. No centralized party not Landrush Ltd, not a cloud provider, not a government request can unilaterally view, alter, or delete a user’s land records.

This is user-owned data in practice. An everyday farmer, agent, or buyer can list land, share proof of ownership, and schedule inspections while retaining sole cryptographic control of their files. By building with the official Sia SDK and indexd following the Quickstart model, Landrush expands the Sia ecosystem into property technology and emerging markets.

Importantly, Landrush distinguishes between:

  • Document integrity (ensuring files are immutable and untampered) and

  • Document authenticity (ensuring uploaded claims are independently verified)

To address authenticity, Landrush introduces a multi-layer verification framework rather than relying solely on storage permanence.

Fraud Reduction & Verification Framework

Land fraud remains widespread across several African property markets due to fragmented record-keeping, falsified documents, and limited transparency.

Landrush mitigates this through a layered trust model consisting of:

  1. Document Integrity Verification
    All uploaded documents are:
  • Encrypted client-side with AES-256-GCM before upload

  • SHA-256 hashed for integrity verification.

    • Stored on the Sia network via the Sia SDK, with indexd operating as the full renter layer managing contract distribution, host negotiation, and redundancy
      This ensures uploaded records cannot be silently altered after submission.
    1. Authority-Based Validation
      Where available, uploaded document hashes may be cross-checked against recognized authorities such as:
    • State land registries

    • Survey plans

    • Certificates of Occupancy

    • Governor’s Consent records
      The platform initially supports manual verification workflows and will expand into registry integrations where APIs or partnerships become available.

    1. Human Verification Layer
      Landrush incorporates verified third-party validators such as:
    • Licensed surveyors

    • Verified agents

    • Legal documentation professionals
      Users may selectively grant these validators access to encrypted documents through secure Sia object sharing. Validators may:

    • Confirm land existence

    • Validate coordinates

    • Inspect uploaded documentation

    • Submit signed cryptographic attestations
      The Landrush team never accesses plaintext documents.

    1. Geospatial Verification
      The platform supports:
    • GPS-tagged image capture

    • Timestamped inspections

    • Coordinate-linked listings

    • Native map visualization
      This creates an additional layer connecting ownership claims to physical land locations.

    1. Transparent Verification Tiers
      Listings display clear trust labels computed from cryptographic proofs and validator attestations, such as:
    • Unverified

    • Document Verified

    • Inspection Verified

    • Fully Verified
      This ensures users understand the level of verification associated with each listing rather than assuming guarantees.

    Note: All ownership documents are encrypted client-side before upload. The Landrush team cannot view plaintext documents. Verification is performed through cryptographic integrity checks (SHA-256 hashes), geospatial proofs, and optional third-party validator attestations. Users may grant time-bound access to verified surveyors or legal professionals via secure Sia object sharing; these validators submit cryptographic attestations without the Landrush team ever accessing the underlying document.

    Are you a resident of any jurisdiction on that list? NO

    Will your payment bank account be located in any jurisdiction on that list? NO

    Grant Specifics

    Amount of money requested and justification with a reasonable breakdown of expenses:

    Total Requested: $10,000 USD (Small Grant — 3-Month MVP)
    Budget includes:

    • Mobile Development

    • Backend Development

    • Sia SDK Integration

    • Security Auditing & Testing

    • App Store Preparation & Deployment

    • Documentation & Open-Source Release

    Grant payments will be received monthly via ACH/wire in USD.

    What is the high-level architecture overview for the grant? What security best practices are you following?

    Architecture Overview

    Client: Cross-platform mobile application for Android and iOS built with React Native, leveraging native mobile map SDKs for geospatial discovery. The app features native camera integration for direct capture of land imagery and video, with on-device compression and client-side encryption before any data is transmitted.

    API Backend: Minimal Go REST API handling authentication, inspection scheduling, and coordination of non-sensitive listing metadata. The backend does not orchestrate storage operations; all encrypted uploads and downloads are performed directly by the mobile client via the Sia SDK.

    Decentralized Storage Layer: All land imagery, video, and ownership documentation is encrypted client-side on the user’s device using AES-256-GCM before upload. The mobile application uses the Sia SDK to upload encrypted blobs directly to the Sia network, with indexd operating as the full renter layer responsible for storage contract management, host negotiation, redundancy, and retrieval. The backend never handles plaintext media, never stores encryption keys, and cannot access user documents. Only lightweight, non-sensitive metadata (listing titles, general location, availability status) touches the PostgreSQL database. If any S3-compatible bridge becomes necessary for auxiliary services, we will use s3d as recommended.

    Database: PostgreSQL for lightweight metadata indexing and relational data (users, listings, inspection appointments). No sensitive land media or ownership documents are stored here.

    Verification: SHA-256 hashing of encrypted documents; hashes cross-referenced with Sia content identifiers to detect tampering. Verification tiers are derived from cryptographic proofs and third-party validator attestations, not centralized review.

    Communication: Direct contact details are revealed only after a confirmed inspection booking, mediated through the backend authorization layer.

    Security Best Practices

    Credential Management: All server-side secrets managed via environment variables; never committed to version control. Mobile application secrets use native secure storage (iOS Keychain / Android Keystore). JWT tokens are stored securely on-device and never in plain text. Encryption keys are derived from user passphrases via PBKDF2 and stored in hardware-backed secure storage; there is no server-side key escrow.

    Input Validation: Strict sanitization and validation on all API inputs to prevent injection attacks. On-device file validation enforces type whitelisting and size limits before encryption and upload.

    Secure Communication: TLS 1.3 enforced for all mobile-to-API traffic with certificate pinning to prevent man-in-the-middle attacks. All Sia network traffic is natively encrypted via the Sia protocol.

    Access Control: JWT-based authentication and role-based authorization for listing management. Biometric authentication (Face ID / fingerprint) is supported where hardware permits.

    Dependency Management: Regular vulnerability audits and pinned dependency versions for both mobile and backend codebases.

    Data Privacy: Document encryption is performed client-side before any Sia upload; users control their own encryption keys. EXIF metadata is stripped from images on-device before encryption to protect user privacy. The Landrush team cannot access plaintext documents.

    Mobile Resilience: On-device image compression and offline-first listing caching to accommodate African connectivity constraints. Background upload queues ensure large media files reach Sia even on unstable networks.

    What are the goals of this small grant? (MAY-JULY)

    Goals: Deliver a fully functional, open-source MVP demonstrating a real-world Sia SDK use case: a decentralized land discovery mobile application for Android and iOS with user-owned storage for documents and media, plus a working inspection scheduling system.

    Timeline (3 Months):

    Month 1 — Milestone 1: Sia Storage Foundation & Backend

    • Sia SDK integration (client-side encryption, upload, download, content addressing).

    • REST API scaffolding, PostgreSQL metadata schema, auth system.

    • Document hashing and verification pipeline.

    Month 2 — Milestone 2: Mobile App Development & Discovery

    • Cross-platform mobile client with native map-based discovery and search/filter.

    • Native camera integration for direct photo/video capture, on-device compression, and client-side encryption.

    • Listing creation flow for landowners/agents.

    • Inspection booking system and contact-reveal logic.

    Month 3 — Milestone 3: Polish, Security, App Store Prep & Open-Source Release

    • End-to-end testing on Android and iOS devices, security review, dependency audit.

    • App Store and Play Store submission preparation.

    • README, build instructions, and MIT-licensed public release.

    • Monthly progress report submission.

    • Monthly progress reports will be submitted at the conclusion of each monthly milestone (Milestone 1, Milestone 2, and Milestone 3).

    Who is the target user for your project?

    Who is the target user for your project?

    While our long-term vision is pan-African, our initial deployment and go-to-market strategy for the MVP focus strictly on Nigeria, where we plan to establish a strong presence and properly test the market before expanding. Our long-term goal is to gradually scale into other West African countries and eventually other parts of Africa as adoption grows.

    Target users within Nigeria include:

    • Nigerian landowners seeking to lease or sell property

    • Real estate agents and verified property professionals

    • Agricultural businesses and farmers seeking lease agreements

    • Property investors and individual buyers looking for transparent, user-controlled land discovery via mobile devices.

    What are your plans for this project following the grant?

    Post-grant, Landrush will scale to additional African markets, introduce community-driven verification incentives, and explore premium listing tiers. We will optimize the mobile experience based on user feedback, add offline-first capabilities for rural areas with intermittent connectivity, and contribute feedback, SDK bug reports, and potential SDK improvements back to the Sia ecosystem to strengthen developer tooling for emerging-market mobile applications.

    Potential risks that will affect the outcome of the project:

    Regulatory variance: Land digitization laws differ across African jurisdictions; we will prioritize markets with clearer property rights frameworks first.

    Connectivity & adoption: Rural users may have limited bandwidth and older Android devices; we will build aggressively on-device compression, offline caching, and support Android API level 24+.

    App store compliance: Google Play and Apple App Store review processes can introduce delays; we will begin submission prep in Month 2 and adhere strictly to platform content guidelines.

    Document standardization: Ownership documents vary by region; we will start with a flexible document schema and expand iteratively.

    User key responsibility: Because encryption keys are client-side and there is no server-side escrow, users who lose their passphrase cannot recover their documents. We will implement optional biometric key wrapping and clear UX warnings about this responsibility.

  • Personal Data Protection & Privacy Policy

    A full Privacy Policy will be available and active when we launch. Since the platform is built on a zero-knowledge framework, privacy and user data protection are part of the core design from the start.

    We are committed to complying with data protection laws in different regions, including Nigeria’s Nigeria Data Protection Regulation (NDPR).

    Development Information

    Will all of your project’s code be open-source?

    Yes. 100% of the project code will be released under the MIT License.

    Leave a link where code will be accessible for review.
    https://github.com/Landrush-ltd

    Do you agree to submit monthly progress reports?

    Yes. I agree to submit monthly progress reports.

    Contact

    Email: [email protected]

  • Note on Landing Page

    Right now, the landing page at https://www.landrushafrica.com/ mainly serves as our pre-launch waitlist site. The icons are currently placeholders while we prepare for the MVP launch. At this stage, our main focus is building a waitlist of interested real estate agents, landowners, and property seekers across Nigeria ahead of the official release.

Hello, welcome :).

First, renterd is no longer allowed in grants. see Grants Program: New Funding Guidelines and Requirements.

Second indexd despite the name isn’t a search engine or key value store in how you may think :P. It is a full renter itself. You need to redesign your idea around Quickstart - Sia Developer Docs since this puts the user first and prevents any centralized party from seeing the data unless a Sia object is shared.

I would recommend you review how Sia’s latest software works and create a design for your pitch based on that.

Lastly, if you need s3, you should be following GitHub - SiaFoundation/s3d: A lightweight, S3-compatible Renter for the Sia network · GitHub.

Thanks.

Please keep in mind that using AI for generating responses to the community questions, especially the way you are, doesn’t add confidence in your ability to deliver good solutions.

1 Like

That’s fair @mike76

I don’t think using a tool to improve communication takes away from our ability to build.

Hi @Mayorken - welcome to the Sia community! Thank you for your proposal and your prompt responses to the community feedback.

A few items:

  • Can you provide proof of previous work for all members of your team?
  • Can you be more specific about who your target users are? You mention ‘African’ generally and then in your post-grant plans indicate you would want to “scale to additional African markets.” What are your initial markets?
  • Since your verification system will be handling legal/property documents, what personal data protection measures will you consider taking if required? Will you have a privacy policy in place?
  • Note: monthly progress reports are required for each milestone (not just Milestone 3) :slight_smile:
  • Are the icons on the landing page provided meant to lead to active links or is this a mockup for now?
1 Like

Hi @mecsbecs

Here’s the GitHub profiles for the team

Secondly

While our long-term vision is pan-African, our initial deployment and go-to-market strategy for the MVP focus strictly on Nigeria, where we plan to establish a strong presence and properly test the market before expanding. Our long-term goal is to gradually scale into other West African countries and eventually other parts of Africa as adoption grows.

Thirdly

Yes, a full Privacy Policy will be available and active when we launch. Since the platform is built on a zero-knowledge framework, privacy and user data protection are part of the core design from the start. We’re also committed to complying with data protection laws in different regions, including Nigeria’s NDPR, covering areas like user rights, lawful data handling, and proper breach response procedures.

Fourthly

Thank you for the clarification. We completely understand and explicitly agree to submit detailed progress reports at the conclusion of each monthly milestone (Milestone 1, Milestone 2, and Milestone 3), rather than just at the end of the grant cycle.

Lastly

Right now, the landing page mainly serves as our pre-launch waitlist site.

The icons are currently just one would say placeholders while we prepare for the MVP launch. At this stage, our main focus is building a waitlist of interested real estate agents, landowners, and property seekers across Nigeria ahead of the official release.

Thank you for addressing my questions and please include the above details in your original proposal for ease of reference.

We’ve reached capacity for next week’s Grants Committee meeting, so this proposal will be slotted for review during the next meeting on June 9th.

Thank you for your patience.

1 Like

Thank you so much @mecsbecs

Thanks for your proposal to The Sia Foundation Grants Program.

After review, the Committee has decided to reject your proposal citing the following reasons:

  • The Committee has doubts Sia is the best fit for this project.

  • Additionally, the Committee has doubts regarding the proposer’s technical understanding of Sia, for example, cross-referencing sha256 hashes with Sia as mentioned in the proposal, was not something the Committee was able to understand.

We’ll be moving this to the Rejected section of the Forum.

Thanks again for your proposal, and you’re always welcome to submit new requests if you feel you can address the Committee’s concerns. Please bear in mind if you do resubmit, that we will require proof of experience building on Sia, which is a new requirement as of this week. Details can be found on the Grants webpage and reflected in the revised Small Grant proposal template.

1 Like