🌎
Illust-Studio
  • 🔮 Welcome
  • Getting Started
    • 🧑‍🏫 Simple Tutorials
      • 🔥 AR -Studio Quickstart
      • 🫟 Place an AR artifact in the world
      • 🕵 Drop a "secret message" w/ an exclusive hyperlink to the world
      • 👹 Support your team through AR face paint
      • 🎶 Create an AR music visualizer
      • 🏴‍☠️ Launch a hologram for an event
  • Core Studio Features & Functions
    • 🎨 AR Studio Editor
      • 🚦 Getting Started (Studio Key Features)
      • 🖱️ General Data
      • ☀️ Lighting & Shadows
      • 💨 Animations
      • 🔊 Audio
      • 👉 Interactions
    • 🤳 Placements
      • 🌎 Geofencing (World Tracking)
      • 😎 Face Tracking
      • 🎯 Image Targets
  • Augmented Reality Viewer
    • 📸 Augmented Reality Viewer(s)
  • Links + Social
    • AR Studio Login
    • @illustspace
    • @illust.space
  • Resources
    • 🚪 Login, Account, and Subscriptions
    • Smart Contract Audits
      • Geospatial Registry Litepaper
        • Abstract
        • Cross-Chain Ownership
        • Hyperstructure & Geohashes
        • Scene Config & AssetIDs
        • Off-Chain Data Usage
        • Time
        • GSR Smart Contract ABI
    • Legal
      • Privacy Policy
      • Terms of Service
      • User Agreement
Powered by GitBook
On this page
  1. Resources
  2. Smart Contract Audits
  3. Geospatial Registry Litepaper

Time

Publishers may want to include a time component in a Placement - either a start date that the Placement should not be considered valid until, or an end date where the placement should no longer be considered valid.

They can do this by including a startTime or endTime parameter in the placement call, encoded in a TimeRange struct. This data will be placed on the blockchain, and placeOf queries will not include placements if the current block is not within the specified time range. Note that, as the GSR only supports a single placement per owner per asset (to facilitate easy lookups), it is not possible to use this to encode multiple future placements (as with a traveling show).

Each placement also records its placement time (from block.timestamp), and exposes this in events and in the GSR data, for time-based views of GSR data. Dapps can then show how a single piece moved over time.

PreviousOff-Chain Data UsageNextGSR Smart Contract ABI

Last updated 8 days ago