Travel Fi is a community-driven map application designed to share critical Points of Interest (POIs) for travelers and residents of large cities.

# Open Grant Proposal: `Travel Fi`

**Travel Fi:**

**Proposal Category:** `Developer and data tooling`

**Individual or Entity Name:** `Dmytro Tieriekhov`

**Proposer:** `omni395`

**Project Repo(s)** `https://github.com/omni395/travel_fi`

**(Optional) Filecoin ecosystem affiliations:** `None`

**(Optional) Technical Sponsor:** `None`

**Do you agree to open source all work you do on behalf of this RFP under the MIT/Apache-2 dual-license?:** `Yes`.

# Project Summary

Travel Fi is a community-driven map application designed to share critical Points of Interest (POIs) for travelers and residents of large cities. The platform targets budget backpackers, digital nomads, solo travelers from developing countries, vanlife travelers, and urban residents needing essential urban infrastructure. It addresses key needs across categories including prepaid SIM and eSIM kiosks, public toilets and showers, free water refill points, luggage storage, charging stations, low-fee ATMs, 24/7 pharmacies, and free parking spots.
The application is built on Rails 8.1 using PostgreSQL and PostGIS for spatial queries, OpenLayers 10 for interactive clustering and map overlays, StimulusReflex, ActionCable (SolidCable) for real-time WebSocket communication, and SolidQueue for background job processing. System state changes and audit logs are managed via PaperTrail as a single source of truth.
Travel Fi incorporates Web3 mechanics through an ERC-20 utility token (TFT) with a capped emission of 1,000,000,000 tokens. Users earn tokens by adding and verifying POIs while physically present at the location.

## Impact

Travel Fi addresses the critical pain point of unreliable urban infrastructure data for budget backpackers, digital nomads, solo travelers, vanlife travelers, and city residents. Existing mapping solutions rely on centralized databases that frequently contain outdated or unverified operational statuses for essential services. By integrating a physical 100-meter Proof of Location model with Web3 economic incentives, Travel Fi creates a self-verifying, crowdsourced layer for physical location data.
Getting this right enables a decentralized, community-driven alternative to proprietary map providers, ensuring highly accurate real-time data while rewarding active contributors via TFT tokens. The primary risk of not addressing this issue is the continued dependence on centralized map platforms that lack granular, crowdsourced verification, leaving mobile users without trustworthy real-time infrastructure data.
Within the Web3 and location-based services ecosystem, Travel Fi demonstrates how crypto-economic incentives and spatial verification can power everyday utility applications. Success looks like a growing network of active users continuously mapping and verifying urban infrastructure on-location, establishing an open, resilient, and accurate global dataset

## Outcomes

## Deliverables & Success Metrics

### Final Outcomes & Deliverables

Travel Fi delivers a community-driven, real-time map application designed for urban infrastructure verification:

* **Interactive Mapping & Spatial Core:** Built on OpenLayers 10 with PostgreSQL and PostGIS to handle spatial queries, interactive POI clustering, and map overlays.
* **Real-Time Communication & Processing:** Integrated via Rails 8.1 using ActionCable (SolidCable) for real-time WebSocket updates and SolidQueue for background job execution.
* **Proof of Location & Verification:** A 100-meter physical proximity check (`Proof of Location`) for submitting and verifying POIs, ensuring high data accuracy.
* **Consensus & Audit System:** Direct editing window for POI authors paired with a multi-user edit proposal (`SuggestedEdit`) consensus mechanism. All state changes are securely logged via PaperTrail as a single source of truth.
* **Token Economy:** Integration of the TFT ERC-20 utility token (1,000,000,000 capped supply) to reward users for on-site submissions and verifications.

### Success Metrics & Measurement

Project success will be measured using the following key performance indicators:

* **Data Volume & Growth:** Total number of registered Points of Interest (POIs) across key categories (water points, SIM kiosks, ATMs, restrooms, etc.).
* **Verification Rate:** Ratio of community-verified POIs vs. unverified submissions.
* **Active Contributors:** Number of unique users submitting, editing, or verifying POIs using the 100-meter Proof of Location mechanism.
* **Data Accuracy:** Minimal rate of reported inaccurate POIs due to the consensus and audit trail mechanics.

## Data Onboarding `N/A`

## Adoption, Reach, and Growth Strategies

### Target Audience & Onboarding Strategy

#### Target Audience & Market Size
* **Primary Target Audience:** Budget backpackers, digital nomads, solo travelers from developing countries, vanlife travelers, and urban residents in major cities who require essential infrastructure.
* **Audience Size & Need:** Millions of global travelers and urban dwellers daily rely on finding micro-infrastructure—such as prepaid SIM/eSIM kiosks, public toilets/showers, free water refill points, luggage storage, low-fee ATMs, 24/7 pharmacies, and free parking.
* **Current Engagement:** Initial outreach and product feedback are gathered through digital nomad communities, solo traveler forums, vanlife groups, and local urban commuter channels.

#### User Onboarding Plan
* **First 10 Users:** Direct manual onboarding of active travelers and local city contributors within target communities. Initial contributors will be invited to add and verify their local infrastructure POIs using the 100-meter Proof of Location mechanism.
* **First 100 Users:** Growth driven by incentivized crowdsourcing. Users earn TFT utility tokens for submitting new POIs and validating existing location data on-site. Viral community loops and localized travel forum recommendations will convert passive map consumers into active contributors.

## Development Roadmap

### Milestone 1: Core Engine, POI Content, Security & EIP-2771 Forwarder
* **Focus:** Build the social core of the application, establish baseline backend/contract security, and implement gasless meta-transactions.
* **Deliverables:**
1. Refinement of reward systems and gamification for POI interaction (creation, voting, photos, comments).
2. Two-stage reward scheme (Off-chain DB - On-chain Claim).
3. Contract Management in Admin Panel (Mint, Pause, fees, pools, Pundit, WebSocket events).
4. Smart Contract Monitoring (ContractSnapshot) (pool balance check jobs, alerts).
5. Implementation of EIP-2771 Forwarder & Admin Hot-Wallet (Minimal Forwarder on L2, meta-transactions, gas tank).
6. Distributed Key Management (Custodial Vault / KMS) (migration from MessageEncryptor to cloud Vault/MPC).
* **Team & Roles:** 1 Full-stack Blockchain Developer (40-45 hrs/week).
* **Time:** 2 months (180 hours)
* **Funding:** $13,000 USD

### Milestone 2: Economy, Accessibility (PWA), and UI
* **Focus:** Migrate configs to DB, build offline PWA mode for poor connectivity, and UI polishing.
* **Deliverables:**
1. Dynamic economy management in DB (moving parameters from `gamification.yml` to Setting, admin panel, PaperTrail).
2. Market rate aggregation (CoinGecko API / Chainlink, caching, TFT to USDT equivalent calculation).
3. Offline PWA mode (IndexedDB, OpenLayers tile caching, offline queue, GPX/CSV).
4. UI/UX refinements (responsiveness, fixing visual bugs, improving interface performance).
* **Team & Roles:** 1 Full-stack Developer (30-35 hrs/week).
* **Time:** 1.5 months (130 hours)
* **Funding:** $8,000 USD

### Milestone 3: Community Governance, DAO & Token Utility
* **Focus:** User engagement, voting, token spending, and community governance.
* **Deliverables:**
1. User proposals page (feedback board for app improvements).
2. Voting for cities, categories, and local community features.
3. DAO verification of categories and POIs (token voting, quorums, verifier rewards).
4. Premium features for tokens (Token Spend) (TFT usage for feature unlocks, ad removal, highlighting places).
5. Bulk distributions (`sendRewardBatch`) (CSV upload in admin, batch contract logic).
* **Team & Roles:** 1 Full-stack Developer (30 hrs/week).
* **Time:** 1.5 months (140 hours)
* **Funding:** $8,000 USD

---

## Total Budget Requested

| Milestone # | Description | Deliverables | Completion Date | Funding |
|---|---|---|---|---|
| Milestone 1 | Core Engine, POI Content, Security & EIP-2771 | Social core, 2-stage rewards, admin contract mgmt, EIP-2771 forwarder, key vault | Month 2 | $13,000 |
| Milestone 2 | Economy, Accessibility (PWA) & UI | Dynamic settings DB, rate aggregation, offline PWA mode with tile caching, UI polish | Month 3.5 | $8,000 |
| Milestone 3 | Community, DAO & Token Utility | Proposals board, city voting, DAO POI verification, Token Spend utility, batch rewards | Month 5 | $8,000 |

**Total Requested Budget:** $29,000 USD

## Maintenance and Upgrade Plans

To ensure long-term sustainability, ongoing maintenance, and steady platform evolution, our post-grant upgrade pipeline focuses on four main areas:

* **Offline Capabilities & Mobile PWA:** Implementing progressive web app (PWA) offline mode with OpenLayers tile caching, local IndexedDB storage, offline queueing, and GPX/CSV export options to maintain usability in remote areas.
* **Community Governance & DAO Infrastructure:** Expanding voting systems to enable DAO-driven verification of POI categories, user proposal feedback boards, and token-weighted quorums with verifier rewards.
* **Enhanced Crow crowdsourcing & Moderation:** Rolling out the `SuggestedEdit` consensus framework for 100-meter local edit proposals, introducing soft crowdsourcing quick-toggles (e.g., status flags for closed or empty locations), and adding 5-star ratings (`PoiRating`).
* **Platform Utility & Protocol Scale:** Integrating rate-aggregation protocols (Chainlink / CoinGecko), implementing dynamic token spend utilities (such as ad removal or feature highlighting), expanding smart contract snapshots for monitoring, and preparing Telegram Mini App integration.

# Team

## Team Members
- Dmytro Tieriekhov — Lead Developer & Blockchain Architect
- Oksana Pismenenko — Project Inspirer & Financial Lead

## Team Member LinkedIn Profiles
- Dmytro Tieriekhov: https://www.linkedin.com/in/dmytro-tieriekhov/
- Oksana Pysmenenko: N/A

## Team Website
https://github.com/omni395/travel_fi

> Demo: https://noneternally-approbative-rosanne.ngrok-free.dev/ (admin@example.com/12345678 launching the server by agreement)
> Youtube - https://youtu.be/R1NnzuvNBAU

## Relevant Experience
Dmytro Tieriekhov is a full-stack software developer and blockchain architect with extensive experience in building production-grade web applications and EVM smart contracts. Specializing in Ruby on Rails backend architecture, PostgreSQL/PostGIS spatial systems, and Web3 integration (Solidity, ERC-20, gasless meta-transactions), he serves as the lead technical engineer driving the end-to-end execution of Travel Fi.

Oksana Pismenenko is the project's creative inspirer and financial lead, responsible for bringing the project vision to life, managing project finances, overseeing budget allocation, and driving the strategic concept for Web3 and map-based features.

## Team code repositories
- Primary Project Repository: https://github.com/omni395/travel_fi
- Proposer Github Profile: https://github.com/omni395

# Additional Information

- **How did you learn about the Open Grants Program?:** Learned through Filecoin Foundation ecosystem updates and the Karma funding map platform.
- **Email address:** omni395@gmail.com
- **Additional Context:** The core architecture and Web3 smart contracts of Travel Fi have been fully deployed and tested on the testnet, with background transaction relays, WebSocket-first live map synchronization, and administrative moderation tools already implemented.

No files, tests, or specific entry points are named. Start by reviewing the linked Travel Fi repository and the three roadmap milestones; completion would require delivering the broad outcomes described for the selected milestone, but the proposal does not define a single bounded task or testable definition of done.

Written by the indexing model from the issue text.