Geolocation Probes the simple appraoch

[h4x3rotab]

Geolocation is required to offer worker QoS to developers. The very basic version of geolocation probes could be to upload a desensitization geolocation from worker to a analytics contract without leaking any IP data.

We leave the real-time network condition probes as the long term goal.

💰 RFP Code Bounty Attached

This issue has a RFP (request-for-proposal) bounty attached. RFP bounties are can have higher amount than mid-size bounties, and are usually only started by the contributor after negotiated with the Phala team. Refer to the list to find RFP bounties.

Milestones

• M1: Implement a basic geolocation collection outside pruntime, and submit it via secret channel to a Geolocation confidential contract to aggregate the worker counts at city level
  • Accepted by Simple Geolocation Probing #445
  • Bounty: $750
• M2: The full implementation
  • Accepted by geoprobe: simple geolocation probing refactoring #510
  • Move the geolocation to pruntime. Leverage Side Tasks (Implement side task #483) to send HTTP request
  • Enable E2E encryption channel to send message to Geolocation contract
  • Record expiration in the contract
  • Output the aggregated worker count by a Query
  • Bounty: $750

[h4x3rotab]

It turned out not fully solved. We are going to move the geolocation logic from pherry to pruntime with Side Tasks (#483).

[h4x3rotab]

The development is already finalized. Now leaving this issue to track the deployment on prod.

[h4x3rotab]

We are going to jump to the proactive geolocation prob. Tracked at #865