Skip to main content
Research Preview — These examples illustrate intended patterns. The code is pseudocode for the ideas, not tested snippets, and may not match current SDK call signatures (the SDK uses object arguments — see the SDK reference). They also gate value on location, so remember: raw GPS is spoofable, and Astral verifies the computation, not that a user was truly somewhere. Use location proofs where the input needs to be trustworthy.

What You Can Build

One thing you can build with Astral is location-based smart contracts: by combining geospatial computation with EAS resolvers, you can gate an onchain action by real-world location. The examples below are the onchain slice of a broader capability — the same signed results work just as well offchain (agents, backends, compliance records).

The Pattern

1

User provides location

Creates a location record (or submits raw coordinates)
2

Astral computes

Performs spatial operation (distance, containment, etc.) in the TEE
3

Signed result

Returns a signed result with the computation output
4

Contract executes

Resolver verifies and triggers business logic

Local Currencies

Concept: Token pairs that can only be traded by people physically in a region. Create neighborhood economies where you must be present to participate. SF residents trade BAY tokens, NYC residents trade APPLE tokens.
Ideas:
  • Neighborhood currencies
  • Regional stablecoins
  • Tourism tokens (only tradeable in the city)
  • Event-specific tokens (festival currency)

Neighborhood DAOs

Concept: Governance tokens only mintable by residents of a specific area.
Ideas:
  • Community governance
  • Co-op management
  • Neighborhood resource allocation
  • Local mutual aid networks

Proof-of-Visit NFTs

Concept: Collectibles you can only mint by physically visiting a location.
Ideas:
  • Travel badges (collect cities/landmarks)
  • Conference attendance proofs
  • Scavenger hunts with onchain checkpoints
  • Historical site verification

Delivery Verification

Concept: Escrow that releases only when package arrives at the right location.
Ideas:
  • P2P delivery marketplaces
  • Supply chain verification
  • Last-mile logistics
  • Food delivery with location proof

Event Check-Ins

Concept: POAPs, rewards, or access that require physical presence.
Ideas:
  • Conference attendance tracking
  • Concert/festival badges
  • Meetup verification
  • Sports event proof-of-attendance

Proximity-Weighted Voting

Concept: Vote weight increases the closer you are to what’s being voted on.
Ideas:
  • Local infrastructure decisions
  • Park/facility usage votes
  • Noise ordinance voting
  • Development impact assessment

Location-Based Marketplaces

Concept: Buy/sell only from people in your area.
Ideas:
  • Hyperlocal classifieds
  • Farmers markets with verified vendors
  • Tool/equipment sharing
  • Local services marketplace

Location-Based Games

Concept: Onchain gameplay tied to real-world movement.
Ideas:
  • Territory control games
  • AR treasure hunts
  • Geocaching with tokens
  • Location-based battles

Environmental Monitoring

Concept: Carbon credits and conservation proofs tied to physical locations.
Ideas:
  • Reforestation verification
  • Wildlife habitat monitoring
  • Pollution reporting
  • Community garden tracking

The Building Blocks

All of these are built with just a few core operations: Combined with EAS resolvers, these primitives open up a broad design space for location-aware applications — onchain and off.

Get Started

Build your first location-based dApp