About the Builder

Who is building LOOTCoin and why this project is achievable

LOOTCoin is built by Keith Pitcher, founder and primary developer. He is responsible for the system architecture, implementation, and ongoing execution of the project. This includes the gameplay loop, Web3 infrastructure, anti-abuse systems, and the integration of real-world mechanics such as GPS validation and liveness-verified sessions.

This project is not outsourced or white-labeled. The core systems are designed and built in-house with a focus on correctness, fairness, and long-term sustainability.

Background and Relevant Experience

Keith is the founder and lead developer behind LOOTCoin, with over two decades of hands-on experience in systems, infrastructure, and full-stack software development. He has been building with blockchain technology since 2011, working across multiple market cycles and major shifts in the underlying stack.

His background spans long-term software engineering, system infrastructure, architecture, and security-adjacent design. This includes building and operating production systems that must function under real constraints, real users, and adversarial conditions. Earlier in his career, he built a PC Computing award-recognized service during the dot-com era, long before modern cloud infrastructure, managed services, or mature developer tooling existed. He was also an Ernst & Young Entrepreneur of the Year Finalist, reflecting third-party recognition for execution and leadership.

LOOTCoin itself is not a recent idea. The core concept of tying real-world exploration to meaningful digital rewards has been refined over many years. For a long time, the supporting technology was not ready. Only when mobile hardware, GPS accuracy, blockchain infrastructure, and gasless transaction tooling aligned did the project become feasible in a way that could scale fairly, resist abuse, and remain usable for real players.

Relevant experience includes:

  • Long-term software engineering and system architecture work
  • Blockchain and Web3 development since 2011, including smart contracts and token systems
  • Designing systems that must withstand abuse, automation, and adversarial behavior
  • Building and operating production software with real users and real constraints

What Has Been Built for LOOTCoin

Keith is personally responsible for the design and implementation of LOOTCoin’s core systems, including:

  • Gameplay architectureThe real-world exploration loop, location validation logic, and reward eligibility rules.
  • Token and reward mechanicsLOOT token usage, LOOTChest reward distribution, and support for external NFT drops and partner assets.
  • Gasless Web3 user experienceWallet abstraction and transaction flows designed to reduce friction for players who are not crypto-native.
  • Anti-bot and Sybil resistance systemsToken-based gameplay sessions backed by biometric liveness detection, designed to confirm human presence without requiring identity verification or KYC.
  • Session scoped authorizationShort-lived, non-transferable session tokens that limit automation, replay attacks, and large-scale farming.

These systems are live, evolving, and refined based on real-world usage rather than theoretical models.

How the Project Is Built

The development of LOOTCoin follows a few core principles:

  • Fairness over hypeSystems that are easy to game eventually fail, regardless of marketing or token mechanics.
  • Presence over identityThe goal is to confirm that a real person is playing in the moment, not to collect or store personal data.
  • Layered defensesNo single anti-abuse mechanism is sufficient on its own. Abuse resistance must assume adversarial behavior.
  • Iteration over promisesReal users expose real problems. Progress comes from shipping, observing, and improving.

Ongoing Commitment

LOOTCoin is an active, founder-built project. Keith remains directly responsible for its technical direction, execution quality, and long-term sustainability.

Progress, tradeoffs, and design decisions are documented openly in the Build Log so that anyone interested can see how the project is actually evolving over time.

Additional Context

For those who want more background or long-form technical writing:

For ongoing updates, shipped features, and technical decisions, see the Build Log.