Post by ranimth07 about Geodnet Token ($GEOD)

  • User Avatar
    @ranimth07Utility+1•3

    $GEOD I looked at GEODNET from the side of a would-be RTK customer in Indonesia: docs → trial → coverage. No hardware, no account created.

    1) Coverage gaps are invisible, and StableHex isn't aimed at them. Your FAQ says 2 cm needs a base station within 25 km. Using your public coverage_stations API, Jakarta has 9 non-offline stations within 25 km and Surabaya has 10. Balikpapan has 0, and the nearest is ~338 km away. That's right next to IKN, Indonesia's new capital, which is under construction. On the coverage map, searching "Balikpapan" drops a pin but stays zoomed out to the whole world. The trial form asks for an exact test location, but nothing checks it against coverage.

    GIP-13 says StableHex (6×) targets "remote area, no existing coverage". Yet the StableHex Center lists 1,072 active hexes and none are in Indonesia. By H3 base cell, most are in North America (~600) and Europe (~320). How are StableHex locations picked, and can customers or operators request one?

    2) A quick fix: on rtkdocs.geodnet.com, the "Free RTK Trial" button under "How to obtain an account" goes to geodnet.com/free, which is a 404. The working page is /free-rtk-trial.

    3) A Solana question. GIP-7 promised Solana Location NFTs, Solana governance and Solana revenue-splitting before Polygon support ends in March 2027. Today the console docs still say "Polygon wallet (required)" for Location NFT, staking and revenue share, with Solana optional. The Location NFT rules still require a Polygon address, and voting is MetaMask-only. With about 5 months left, is there a timeline for the Solana NFT airdrop?

    Suggestions: make map search zoom in and show "nearest station: X km, expected accuracy". Show StableHexes on the public coverage map. Publish a GIP-7 migration checklist.

    Checked in my browser with help from an AI agent.