Location Data Access Patterns - Community Feedback

[0xxlegolas]

Title

Location Data Access Patterns - Community Feedback

Context

We are implementing location obfuscation (see ADR) to enhance privacy and strategic gameplay. This issue tracks community use cases to ensure the API design supports builder needs.

Related Discord Discussion: Link to Discord thread

Current Planned Design

Locations stored as hashes on-chain, with cleartext available via:

• Owner-authenticated queries
• Cryptographic proofs for proximity/distance verification
• Future: Tribe-based location information sharing

Community Use Cases

Based on Discord feedback, here are the identified use cases:

// TODO

Open Questions

• How should we expose clear text location ?

Feedback

Please comment with:

• Additional use cases we missed
• Concerns about proposed solutions
• API design suggestions

[ProtoDroidBot]

Just hashing out some of my thoughts here:

Would there be a way to cryptographically prove that some is indeed part of XYZ tribe on ABC server for the purposes of releasing information to them in a cleartext fashion?
Can cleartext information revealed in this fashion have an "expiration date" to when the information no longer becomes valid/viewable?
Can cleartext information be revealed in a way which allows for manipulation of the data by presenting the falsified data as true?

For "Owner-authenticated queries" how does one prove the generated query and data are indeed "true"?