Roadmap
Astral is infrastructure for verifiable location: signed answers to spatial questions, and evidence-based verification of location claims. (Smart contracts are one place those signed results can go, not the whole story.) This page tracks what’s done, what we’re working on, and what’s planned.Current Status
What’s Built
Technical Specification
Complete spec defining architecture, API design, SDK structure, and security model
SDK Foundation
Core SDK with location and compute namespaces defined
Schema Definitions
EAS schema designs for Location and Policy attestations
Documentation
This documentation site
In Progress
| Component | Status | Notes |
|---|---|---|
| Compute Service API | Running (staging) | Express/Fastify service |
| PostGIS Integration | Running (staging) | Docker container setup |
| SDK Compute Extension | Built | TypeScript client |
| EigenCompute (TEE) | Test deployments | Validated on real TEE hardware; continuous attested operation not yet funded |
| Example Contracts | In Development | Resolver templates |
Planned Features
Phase 1: v0
- Core operations:
distance,contains,within,intersects,area,length - PostGIS-powered computations
- EigenCompute TEE test deployments (continuous attested operation not yet funded)
- Delegated attestation signing
- SDK with compute namespace
- Basic rate limiting (IP-based)
Phase 2: Authentication
- Wallet-based request signing
- Per-wallet rate limiting
- Higher limits for authenticated users
Phase 3: Extended Operations
-
buffer- Create buffer zone around geometry -
centroid- Find center point -
union- Merge geometries -
intersection- Overlapping area -
disjoint- Geometries don’t touch
Phase 4: Location Proofs (Research in Progress)
We’re actively researching location proof mechanisms. See the Location Proof framework design.- Framework design and specification
- First working plugin (ProofMode — verification end to end)
- Experimental plugin interfaces defined (WitnessChain, gpsd, GeoClue, Wi-Fi/MLS, IP geolocation)
- Mature the experimental plugins; develop new ones with partners
- Multi-stamp verification
- Sensor fusion (accelerometer, barometer)
- Physical proof integration (NFC/QR)
Phase 5: Decentralization
- AVS consensus (multiple operators)
- Cryptoeconomic security
- ZK proof generation (optional)
- Decentralized signer rotation
What’s Missing (v0)
These are explicitly out of scope for v0:| Feature | Status | Notes |
|---|---|---|
| Full location proof verification | In progress | ProofMode verification works; other plugins’ verification logic is experimental; multi-stamp correlation and hardening are ongoing |
| Gas sponsorship | Deferred | Developers pay via delegated attestations |
| Reference data caching | Deferred | Start stateless, add if needed |
| Complex geometry limits | Deferred | Add based on usage patterns |
| Cross-chain operations | Not planned | Single chain per SDK instance |
| Unit conversion | Not planned | Metric only |
Research Questions
These are open questions being investigated:-
Nonce/Replay Protection
- Should Policy Attestations include explicit nonce?
- Current design relies on unique UIDs + timestamps
-
EigenCompute Networking
- Verify TEE allows outbound for EAS queries
- Understand latency characteristics
-
PostGIS in TEE
- Validate performance in TEE environment
- Benchmark spatial operations
-
Deterministic Geocompute
- Ensuring identical results across runs
- Floating point precision handling
- GEOS version pinning
Contributing
We’re building in public! Ways to contribute:- Feedback: Open issues with suggestions or questions
- Use cases: Share what you’d build with location-based contracts
- Code: Contributions welcome — see the GitHub org
Security
Threat model, known limitations, and responsible disclosure