CosmWasm Anchored Spatial Data Registry
Last updated
Was this helpful?
Last updated
Was this helpful?
With (Junø/CosmWasm contract) and (HTTP REST Server) we address the feasibility of providing performant and scalable access to geospatial data in geojson format, leveraging MongoDB’s . When a data item is ingested into the database, a hash of the relevant data is generated and stored on a CosmWasm contract which implements a indexed datastore. Validation results are stored on both the database and the contract. Validators would each run a replica instance, with an independent compute instance performing the same hashing algorithm.
Fully written in , using and .
Role-based access to rest endpoints: admin role creates data items, validator role validates, and user role can query.
Polymorphic (polygon, point, line, etc.) geospatial data within a single index.
Validation compute currently occurs via a REST endpoint based on userid/role and is not yet tied to a validator’s specific replica instance.
Integration tests for both geodata-anchor and geodata-rest run against a local instance of via Docker; we have not yet deployed to a testnet.
Reverse anchor hash from contract to database.
Move most data onchain, queried directly via secondary indexes, with links to IPFS, Arweave or MongoDB Atlas for large objects.
Evolve hashing strategies via .
Larger datasets could leverage MongoDB features.
3D geospatial index design and implementation with cw-storage-plus secondary .
Mostly beyond the scope of this PoC, but with and the on Cosmos, many possibilities exist for .
Thank you to for funding this PoC and providing valuable technical direction.