Project Name
Latitude Finance
Team / Organization Name
Latitude Finance
Primary Contact
Discord: @xfactor3617
Email: [Lxveal1983@gmail.com](mailto:Lxveal1983@gmail.com)
Telegram: xfactor2099
Team Members
Lamont Veal
Lead Developer
Full-time
LinkedIn: linkedin.com/in/lamont-veal-63a1b0186/
Project Summary
Latitude Finance is a privacy-preserving token launchpad and programmable market infrastructure project designed for the Logos ecosystem.
Latitude proposes a Logos-centric architecture for RFP-015 in which Logos remains the canonical layer for project tokens, collateral, privacy, custody, authorization, and final settlement, while Uniswap v4 provides programmable bonding-curve market execution through LatitudeHook.
LatitudeHook is a Uniswap v4 Hook that enables Logos-native markets to execute virtual constant-product bonding curves from Uniswap-supported chains. Logos remains the sovereign layer for canonical assets, privacy, and settlement, while Uniswap v4 provides programmable market execution and access to external liquidity infrastructure.
This architecture allows Logos markets to interact with established DeFi infrastructure without requiring external chains to become the canonical home of Logos assets.
Technical Approach
Latitude Finance separates the protocol into three primary layers:
Logos — Sovereign Market Layer
Logos is responsible for:
- canonical project tokens;
- canonical collateral;
- public and private accounts;
- market creation;
- user authorization;
- asset custody;
- reserve accounting;
- pending trade state;
- settlement verification;
- final settlement.
LatitudeHook / Uniswap v4 — Execution Layer
LatitudeHook is responsible for:
- virtual bonding-curve execution;
- virtual reserve management;
- deterministic pricing;
- buy and sell calculations;
- protocol fees;
- slippage enforcement;
- market-state transitions;
- execution results.
Cross-Chain Messaging
Cross-chain messaging connects Logos markets to LatitudeHook and returns execution results to Logos.
The initial implementation will use Hyperlane general message passing where technically appropriate.
Messages will include authenticated trade instructions, settlement results, sequence numbers, nonces, and state information necessary to prevent stale or duplicate execution.
Architecture
LOGOS / LEZ
Tokens • Collateral • Privacy
Authorization • Asset Custody
Market Settlement
│
Trade Intent
│
▼
Cross-Chain Messaging
│
▼
LATITUDEHOOK
Uniswap v4
Virtual Constant-Product Curve
Vt × Vc = k
Pricing • Fees • Execution
│
Settlement Result
│
▼
Cross-Chain Messaging
│
▼
LOGOS / LEZ
Verify • Transfer • Settle
Logos remains authoritative for real assets and user ownership.
LatitudeHook maintains the virtual market state required to calculate pricing and market execution.
LatitudeHook
LatitudeHook is the primary programmable execution component of Latitude Finance.
It is a Uniswap v4 Hook that executes a virtual constant-product bonding curve for Logos markets.
Rather than making an external Uniswap deployment the canonical location of a Logos asset, LatitudeHook maintains the virtual reserve state necessary to calculate market pricing and execution.
The Hook manages information including:
- virtual token reserve;
- virtual collateral reserve;
- remaining sale supply;
- available collateral;
- market sequence;
- protocol fee;
- market status.
The virtual reserve state determines market pricing, while Logos canonical state determines actual ownership, available reserves, and settlement.
This separation allows Logos to remain the sovereign market layer while Latitude uses Uniswap v4 as programmable execution infrastructure.
Constant-Product Bonding Curve
Latitude will implement the constant-product virtual-reserve model specified by RFP-015.
The invariant is:
Where:
Vt = virtual project-token reserve
Vc = virtual collateral reserve
k = constant-product invariant
For a buy:
tokens_out =
Vt - k / (Vc + effective_collateral_in)
For sells, the inverse reserve transition determines the collateral output.
Latitude will support deterministic integer arithmetic and documented rounding behavior.
Protocol fees will be calculated before the effective trade amount is applied to the bonding curve.
The curve will support both buying and selling during the active sale period, with the ability to support one-directional markets where appropriate.
Market Creation
A creator will be able to create a Logos-native bonding-curve market by configuring:
- project token;
- collateral token;
- sale quantity
D;
- optional DEX or graduation reserve
R;
- virtual token reserve
Vt;
- virtual collateral reserve
Vc;
- protocol configuration.
The sale reserve and optional graduation reserve will remain separately accounted for.
The market will close when the available sale supply is exhausted.
Trade Execution
A Latitude trade begins on Logos.
For a buy or sell, Logos validates the user's request and verifies that the required assets are available.
The required assets are locked while the trade is pending.
Logos then creates a TradeIntent containing the minimum information required for external execution, such as:
- market ID;
- trade direction;
- amount;
- minimum output;
- expected sequence;
- deadline;
- nonce.
The TradeIntent is delivered to the Latitude execution environment.
LatitudeHook verifies the expected market state and performs the bonding-curve calculation through Uniswap v4.
After execution, a SettlementResult is returned to Logos containing:
- market ID;
- input amount;
- output amount;
- protocol fee;
- updated virtual reserves;
- previous sequence;
- new sequence;
- state hash.
Logos verifies the result before changing canonical financial state.
Settlement Model
Cross-chain execution is asynchronous.
Latitude therefore uses a pending-settlement model.
User Trade
│
▼
Logos validates and locks assets
│
▼
TradeIntent
│
▼
LatitudeHook executes
│
▼
SettlementResult
│
▼
Logos verifies and settles
A trade moves through states such as:
PENDING → SETTLED
or
PENDING → CANCELLED
If execution fails or the transaction exceeds its permitted timeout, the trade can be cancelled and locked assets released according to the settlement rules.
This prevents cross-chain messaging failures from permanently locking user assets.
Sequence and Replay Protection
Each Latitude market maintains a monotonically increasing sequence number.
A TradeIntent must contain the sequence number expected by LatitudeHook.
For example:
Market Sequence: 18
Trade expects: 18
│
▼
Trade executes
│
▼
New Sequence: 19
A delayed or duplicate message still expecting sequence 18 will be rejected.
Latitude will combine sequence validation with nonces, authenticated origin verification, sender verification, deadlines, and settlement-state tracking.
This protects against:
- stale execution;
- duplicate execution;
- replayed messages;
- reordered messages;
- conflicting market states;
- double settlement.
Privacy Architecture
Privacy remains centered on Logos.
LatitudeHook does not require access to a user's private Logos identity, private portfolio, or complete account state.
The public participation path is:
Public Logos Account
↓
Latitude Market
↓
LatitudeHook
↓
Logos Settlement
The private participation path follows the Logos privacy model:
Private Logos Account
↓
Deshield
↓
Fresh Public Account
↓
Latitude Market
↓
LatitudeHook
↓
Logos Settlement
↓
Re-shield
↓
Private Logos Account
Only the information necessary to execute the market transaction is exposed to the external execution layer.
The Logos-side application and SDK will manage the private interaction flow and clearly disclose which transaction information is public.
RFP-015 Architectural Extension
Latitude deliberately extends the reference architecture described by RFP-015.
RFP-015 describes a bonding-curve token launchpad operating directly on LEZ. Latitude proposes keeping the canonical financial and privacy state on Logos while allowing the bonding-curve execution layer to use Uniswap v4 infrastructure.
This extension is intended to increase the reach of Logos markets rather than reduce the role of Logos.
Logos remains responsible for:
- canonical assets;
- private state;
- custody;
- authorization;
- reserve solvency;
- final settlement.
LatitudeHook provides the programmable market-execution layer.
During the specification milestone, Latitude will work with Logos maintainers to determine which RFP-015 requirements must remain directly enforced on LEZ and how the cross-chain execution architecture should satisfy the required security, reserve, and settlement properties.
Multi-Chain Direction
The MVP will initially integrate Logos with one Uniswap v4 execution environment so that the protocol can be tested against a clearly defined security and settlement model.
The longer-term Latitude architecture is designed to support Logos markets from additional Uniswap-supported chains.
Uniswap v4 Markets
│
▼
LatitudeHook
│
▼
Logos
Assets • Privacy • Settlement
External environments act as execution venues.
Logos remains the canonical market and settlement environment.
Support for additional execution chains is outside the initial RFP MVP unless mutually agreed with Logos.
Protocol Fees
Latitude will implement a per-swap protocol fee denominated in collateral.
For buys, the protocol fee is deducted from the input collateral before calculating the effective bonding-curve trade.
For sells, the fee is deducted from the collateral output.
Canonical fee settlement will occur on Logos so that Logos remains authoritative over real collateral movement.
User Interface
Latitude will provide a Logos-focused application for creating and participating in bonding-curve markets.
The application will support:
- wallet connection;
- public/private participation;
- market discovery;
- token selection;
- buy;
- sell;
- collateral selection;
- current price;
- expected output;
- protocol fee;
- price impact;
- bonding-curve progress;
- sale progress;
- transaction status;
- cross-chain execution status;
- privacy disclosures;
- market analytics.
Creators will also be able to configure and monitor their Logos-native markets.
Analytics
Latitude will provide aggregate market analytics without attempting to associate private Logos users with individual market participation.
Analytics will include:
- total collateral raised;
- current spot price;
- tokens sold;
- remaining sale supply;
- number of buys;
- number of sells;
- price-versus-supply curve;
- current curve position;
- market status;
- settlement status.
Testing Strategy
Latitude will prioritize financial correctness, deterministic execution, privacy boundaries, and cross-chain settlement safety.
Testing will cover:
- constant-product invariant preservation;
- deterministic buy calculations;
- deterministic sell calculations;
- exact-output calculations;
- fee calculations;
- integer rounding;
- zero-input rejection;
- slippage protection;
- insufficient supply;
- insufficient collateral;
- automatic market close;
- sequence monotonicity;
- stale sequence rejection;
- duplicate nonce rejection;
- replay protection;
- invalid sender rejection;
- invalid origin rejection;
- timeout recovery;
- settlement recovery;
- cross-chain integration;
- fuzz testing;
- invariant testing.
Milestones, Payout, and Timeline
Milestone 1 — Specification, Architecture, and Threat Model
Weeks 1–2
Objective
Finalize the Latitude protocol architecture before implementing cross-chain financial state.
Deliverables
- formal Latitude architecture specification;
- RFP-015 deviation specification;
- constant-product formula specification;
- rounding specification;
- market-state schema;
- TradeIntent schema;
- SettlementResult schema;
- cross-chain state machine;
- sequence-number model;
- timeout and cancellation model;
- privacy-boundary specification;
- security threat model;
- Logos development environment;
- Uniswap v4 development environment;
- initial test harnesses.
Key Risks Addressed
- state divergence;
- asynchronous execution;
- replayed messages;
- stale messages;
- double settlement;
- concurrent intents;
- rounding mismatch;
- reserve insolvency.
Milestone Completion — $1,000
A deterministic test vector executed through independent Logos-side and Solidity-side math implementations must produce identical expected market results.
Milestone 2 — Logos Canonical Market Core
Weeks 3–4
Objective
Build the Logos component responsible for canonical assets, market authorization, reserves, privacy integration, and settlement state.
Deliverables
- Logos Market Adapter;
- market creation;
- sale reserve
D;
- optional reserve
R;
- real collateral accounting;
- creator configuration;
- buy authorization;
- sell authorization;
- asset locking;
- nonce generation;
- sequence tracking;
- pending trade registry;
- expiry handling;
- settlement interface;
- public-account path;
- program tests;
- CLI skeleton.
Milestone Completion — $1,000
A user can create a Logos-native market, fund its reserves, submit a mock buy or sell request, lock the necessary assets, and safely cancel or settle the operation.
Milestone 3 — LatitudeHook / Uniswap v4 Execution Layer
Weeks 5–6
Objective
Implement the Latitude virtual constant-product bonding-curve execution engine using Uniswap v4.
Deliverables
- LatitudeHook;
- Latitude v4 routing component;
- Uniswap v4 PoolManager integration;
- market initialization;
- virtual token reserve;
- virtual collateral reserve;
- buy logic;
- sell logic;
- exact-output quoting;
- protocol-fee calculation;
- slippage enforcement;
- deterministic rounding;
- sequence validation;
- state-hash generation;
- Foundry tests;
- fuzz tests;
- invariant tests;
- test deployment.
Milestone Completion — $1,000
A synthetic Logos market can execute deterministic buys and sells through LatitudeHook while maintaining the required constant-product invariant.
Milestone 4 — Cross-Chain Interoperability
Weeks 7–8
Objective
Connect Logos to the Latitude execution environment.
Deliverables
- Logos-side interoperability adapter;
- Latitude execution router;
- message encoding;
- Logos trade dispatch;
- execution-environment message reception;
- origin validation;
- sender validation;
- SettlementResult dispatch;
- Logos result reception;
- nonce verification;
- sequence synchronization;
- duplicate-message protection;
- relayer test configuration;
- cross-chain integration tests.
Milestone Completion — $1,000
A Logos-originated TradeIntent reaches LatitudeHook, executes through Uniswap v4, and returns an authenticated SettlementResult to Logos while canonical project-token ownership remains on Logos.
Milestone 5 — Complete Settlement and Privacy Path
Weeks 9–10
Objective
Complete the financial round trip and integrate the Logos privacy interaction model.
Deliverables
- buy settlement;
- sell settlement;
- collateral settlement;
- project-token settlement;
- protocol-fee routing;
- timeout recovery;
- locked-asset recovery;
- stale-intent rejection;
- insufficient-reserve rejection;
- automatic close at
D = 0;
- public-account path;
- deshield → trade → re-shield path;
- fresh public-account handling;
- private-path SDK integration;
- privacy-disclosure UX;
- privacy specification;
- end-to-end test scenarios.
Milestone Completion — $1,000
The complete private trade flow succeeds from a Logos private account through LatitudeHook execution and back to final Logos settlement and re-shielding.
Milestone 6 — Productization, Security Testing, and MVP Release
Weeks 11–12
Objective
Deliver a reproducible, open-source Latitude Finance MVP.
Deliverables
- Latitude application;
- creator dashboard;
- participant dashboard;
- price-versus-supply visualization;
- market analytics;
- cross-chain transaction status;
- actionable error states;
- SDK documentation;
- CLI completion;
- IDL where applicable;
- deployment scripts;
- CI;
- end-to-end tests;
- replay tests;
- concurrency tests;
- failure-injection tests;
- fuzz and invariant test suite;
- complete README;
- architecture documentation;
- security assumptions;
- privacy documentation;
- compute and cost measurements where applicable;
- public source repository;
- MIT + Apache-2.0 licensing;
- testnet demonstration.
Milestone Completion — $1,000
A developer following the Latitude documentation can deploy the required components, create a Logos-native bonding-curve market, execute a test trade through LatitudeHook, and complete settlement on Logos.
Total Requested Budget
$6,000 USD
| Milestone |
Amount |
| Milestone 1 |
$1,000 |
| Milestone 2 |
$1,000 |
| Milestone 3 |
$1,000 |
| Milestone 4 |
$1,000 |
| Milestone 5 |
$1,000 |
| Milestone 6 |
$1,000 |
| Total |
$6,000 |
Timeline
12 Weeks
| Period |
Development |
| Weeks 1–2 |
Specification, Architecture, Threat Model |
| Weeks 3–4 |
Logos Canonical Market Core |
| Weeks 5–6 |
LatitudeHook + Uniswap v4 |
| Weeks 7–8 |
Cross-Chain Interoperability |
| Weeks 9–10 |
Settlement + Privacy |
| Weeks 11–12 |
Productization + MVP |
Deployment to subsequent Logos testnet and mainnet environments will follow network availability and coordination with Logos.
Relevant Experience
Lamont Veal is a software and blockchain developer with approximately six years of Solidity development experience.
He has completed the Uniswap Hooks Incubator UHI9 and has experience developing Uniswap v4 Hooks, confidential DeFi applications, AMMs, cross-chain systems, tokenized assets, and smart-contract infrastructure.
Technical experience relevant to Latitude includes:
- Solidity;
- Rust
- Foundry;
- Hardhat;
- Uniswap v4;
- custom Hooks;
- AMMs;
- bonding curves;
- privacy-preserving DeFi;
- Hyperlane;
- cross-chain messaging;
- smart-contract security;
- fuzz testing;
- invariant testing;
- React / Next.js;
- TypeScript;
- ethers.js.
Professional experience also includes serving as a Technical Account Manager at Ledger, providing technical support and account management for enterprise blockchain customers.
Post-Delivery Plan
Following successful completion of the MVP, Latitude Finance will continue toward deployment on Logos mainnet as the Logos network and required infrastructure become available.
The initial RFP implementation will focus on the bonding-curve launchpad, privacy interaction model, and one external Uniswap v4 execution environment.
Future development can expand Latitude to additional Uniswap-supported chains and additional programmable market types.
The long-term goal is to allow Logos-native markets to access broader decentralized liquidity infrastructure while Logos remains the canonical environment for assets, privacy, authorization, and settlement.
Open Source
All RFP-funded Latitude Finance code will be released publicly under the required MIT and Apache-2.0 licenses.
Source code, tests, deployment tooling, architecture documentation, SDK documentation, privacy documentation, and instructions necessary to reproduce the MVP will be publicly available.
Permissions and Consent
- I confirm Logos may contact me using the primary contact information provided above for follow-ups and next steps.
- I consent to Logos using information from this proposal publicly, including blogs, case studies, social posts, or analytical reporting. Redactions can be requested at any time.
Program Requirements
- I have read and agree to the Logos RFP Terms and Conditions and understand that no Grant is awarded and no right to payment arises unless a Grant Agreement is executed.
- I understand that RFP specifications are proposals rather than instructions, that Logos makes no representations as to their legal or regulatory treatment, and that I am responsible for assessing what I build, deploy, or operate and for complying with applicable laws.
- I understand this project must be open-sourced under the MIT and Apache 2.0 licenses unless explicitly approved otherwise.
- I am prepared to deliver milestone-based outcomes.
Project Name
Latitude Finance
Team / Organization Name
Latitude Finance
Primary Contact
Discord: @xfactor3617
Email: [Lxveal1983@gmail.com](mailto:Lxveal1983@gmail.com)
Telegram: xfactor2099
Team Members
Lamont Veal
Lead Developer
Full-time
LinkedIn: linkedin.com/in/lamont-veal-63a1b0186/
Project Summary
Latitude Finance is a privacy-preserving token launchpad and programmable market infrastructure project designed for the Logos ecosystem.
Latitude proposes a Logos-centric architecture for RFP-015 in which Logos remains the canonical layer for project tokens, collateral, privacy, custody, authorization, and final settlement, while Uniswap v4 provides programmable bonding-curve market execution through LatitudeHook.
LatitudeHook is a Uniswap v4 Hook that enables Logos-native markets to execute virtual constant-product bonding curves from Uniswap-supported chains. Logos remains the sovereign layer for canonical assets, privacy, and settlement, while Uniswap v4 provides programmable market execution and access to external liquidity infrastructure.
This architecture allows Logos markets to interact with established DeFi infrastructure without requiring external chains to become the canonical home of Logos assets.
Technical Approach
Latitude Finance separates the protocol into three primary layers:
Logos — Sovereign Market Layer
Logos is responsible for:
LatitudeHook / Uniswap v4 — Execution Layer
LatitudeHook is responsible for:
Cross-Chain Messaging
Cross-chain messaging connects Logos markets to LatitudeHook and returns execution results to Logos.
The initial implementation will use Hyperlane general message passing where technically appropriate.
Messages will include authenticated trade instructions, settlement results, sequence numbers, nonces, and state information necessary to prevent stale or duplicate execution.
Architecture
Logos remains authoritative for real assets and user ownership.
LatitudeHook maintains the virtual market state required to calculate pricing and market execution.
LatitudeHook
LatitudeHook is the primary programmable execution component of Latitude Finance.
It is a Uniswap v4 Hook that executes a virtual constant-product bonding curve for Logos markets.
Rather than making an external Uniswap deployment the canonical location of a Logos asset, LatitudeHook maintains the virtual reserve state necessary to calculate market pricing and execution.
The Hook manages information including:
The virtual reserve state determines market pricing, while Logos canonical state determines actual ownership, available reserves, and settlement.
This separation allows Logos to remain the sovereign market layer while Latitude uses Uniswap v4 as programmable execution infrastructure.
Constant-Product Bonding Curve
Latitude will implement the constant-product virtual-reserve model specified by RFP-015.
The invariant is:
Where:
For a buy:
For sells, the inverse reserve transition determines the collateral output.
Latitude will support deterministic integer arithmetic and documented rounding behavior.
Protocol fees will be calculated before the effective trade amount is applied to the bonding curve.
The curve will support both buying and selling during the active sale period, with the ability to support one-directional markets where appropriate.
Market Creation
A creator will be able to create a Logos-native bonding-curve market by configuring:
D;R;Vt;Vc;The sale reserve and optional graduation reserve will remain separately accounted for.
The market will close when the available sale supply is exhausted.
Trade Execution
A Latitude trade begins on Logos.
For a buy or sell, Logos validates the user's request and verifies that the required assets are available.
The required assets are locked while the trade is pending.
Logos then creates a TradeIntent containing the minimum information required for external execution, such as:
The TradeIntent is delivered to the Latitude execution environment.
LatitudeHook verifies the expected market state and performs the bonding-curve calculation through Uniswap v4.
After execution, a SettlementResult is returned to Logos containing:
Logos verifies the result before changing canonical financial state.
Settlement Model
Cross-chain execution is asynchronous.
Latitude therefore uses a pending-settlement model.
A trade moves through states such as:
If execution fails or the transaction exceeds its permitted timeout, the trade can be cancelled and locked assets released according to the settlement rules.
This prevents cross-chain messaging failures from permanently locking user assets.
Sequence and Replay Protection
Each Latitude market maintains a monotonically increasing sequence number.
A TradeIntent must contain the sequence number expected by LatitudeHook.
For example:
A delayed or duplicate message still expecting sequence 18 will be rejected.
Latitude will combine sequence validation with nonces, authenticated origin verification, sender verification, deadlines, and settlement-state tracking.
This protects against:
Privacy Architecture
Privacy remains centered on Logos.
LatitudeHook does not require access to a user's private Logos identity, private portfolio, or complete account state.
The public participation path is:
The private participation path follows the Logos privacy model:
Only the information necessary to execute the market transaction is exposed to the external execution layer.
The Logos-side application and SDK will manage the private interaction flow and clearly disclose which transaction information is public.
RFP-015 Architectural Extension
Latitude deliberately extends the reference architecture described by RFP-015.
RFP-015 describes a bonding-curve token launchpad operating directly on LEZ. Latitude proposes keeping the canonical financial and privacy state on Logos while allowing the bonding-curve execution layer to use Uniswap v4 infrastructure.
This extension is intended to increase the reach of Logos markets rather than reduce the role of Logos.
Logos remains responsible for:
LatitudeHook provides the programmable market-execution layer.
During the specification milestone, Latitude will work with Logos maintainers to determine which RFP-015 requirements must remain directly enforced on LEZ and how the cross-chain execution architecture should satisfy the required security, reserve, and settlement properties.
Multi-Chain Direction
The MVP will initially integrate Logos with one Uniswap v4 execution environment so that the protocol can be tested against a clearly defined security and settlement model.
The longer-term Latitude architecture is designed to support Logos markets from additional Uniswap-supported chains.
External environments act as execution venues.
Logos remains the canonical market and settlement environment.
Support for additional execution chains is outside the initial RFP MVP unless mutually agreed with Logos.
Protocol Fees
Latitude will implement a per-swap protocol fee denominated in collateral.
For buys, the protocol fee is deducted from the input collateral before calculating the effective bonding-curve trade.
For sells, the fee is deducted from the collateral output.
Canonical fee settlement will occur on Logos so that Logos remains authoritative over real collateral movement.
User Interface
Latitude will provide a Logos-focused application for creating and participating in bonding-curve markets.
The application will support:
Creators will also be able to configure and monitor their Logos-native markets.
Analytics
Latitude will provide aggregate market analytics without attempting to associate private Logos users with individual market participation.
Analytics will include:
Testing Strategy
Latitude will prioritize financial correctness, deterministic execution, privacy boundaries, and cross-chain settlement safety.
Testing will cover:
Milestones, Payout, and Timeline
Milestone 1 — Specification, Architecture, and Threat Model
Weeks 1–2
Objective
Finalize the Latitude protocol architecture before implementing cross-chain financial state.
Deliverables
Key Risks Addressed
Milestone Completion — $1,000
A deterministic test vector executed through independent Logos-side and Solidity-side math implementations must produce identical expected market results.
Milestone 2 — Logos Canonical Market Core
Weeks 3–4
Objective
Build the Logos component responsible for canonical assets, market authorization, reserves, privacy integration, and settlement state.
Deliverables
D;R;Milestone Completion — $1,000
A user can create a Logos-native market, fund its reserves, submit a mock buy or sell request, lock the necessary assets, and safely cancel or settle the operation.
Milestone 3 — LatitudeHook / Uniswap v4 Execution Layer
Weeks 5–6
Objective
Implement the Latitude virtual constant-product bonding-curve execution engine using Uniswap v4.
Deliverables
Milestone Completion — $1,000
A synthetic Logos market can execute deterministic buys and sells through LatitudeHook while maintaining the required constant-product invariant.
Milestone 4 — Cross-Chain Interoperability
Weeks 7–8
Objective
Connect Logos to the Latitude execution environment.
Deliverables
Milestone Completion — $1,000
A Logos-originated TradeIntent reaches LatitudeHook, executes through Uniswap v4, and returns an authenticated SettlementResult to Logos while canonical project-token ownership remains on Logos.
Milestone 5 — Complete Settlement and Privacy Path
Weeks 9–10
Objective
Complete the financial round trip and integrate the Logos privacy interaction model.
Deliverables
D = 0;Milestone Completion — $1,000
The complete private trade flow succeeds from a Logos private account through LatitudeHook execution and back to final Logos settlement and re-shielding.
Milestone 6 — Productization, Security Testing, and MVP Release
Weeks 11–12
Objective
Deliver a reproducible, open-source Latitude Finance MVP.
Deliverables
Milestone Completion — $1,000
A developer following the Latitude documentation can deploy the required components, create a Logos-native bonding-curve market, execute a test trade through LatitudeHook, and complete settlement on Logos.
Total Requested Budget
$6,000 USD
Timeline
12 Weeks
Deployment to subsequent Logos testnet and mainnet environments will follow network availability and coordination with Logos.
Relevant Experience
Lamont Veal is a software and blockchain developer with approximately six years of Solidity development experience.
He has completed the Uniswap Hooks Incubator UHI9 and has experience developing Uniswap v4 Hooks, confidential DeFi applications, AMMs, cross-chain systems, tokenized assets, and smart-contract infrastructure.
Technical experience relevant to Latitude includes:
Professional experience also includes serving as a Technical Account Manager at Ledger, providing technical support and account management for enterprise blockchain customers.
Post-Delivery Plan
Following successful completion of the MVP, Latitude Finance will continue toward deployment on Logos mainnet as the Logos network and required infrastructure become available.
The initial RFP implementation will focus on the bonding-curve launchpad, privacy interaction model, and one external Uniswap v4 execution environment.
Future development can expand Latitude to additional Uniswap-supported chains and additional programmable market types.
The long-term goal is to allow Logos-native markets to access broader decentralized liquidity infrastructure while Logos remains the canonical environment for assets, privacy, authorization, and settlement.
Open Source
All RFP-funded Latitude Finance code will be released publicly under the required MIT and Apache-2.0 licenses.
Source code, tests, deployment tooling, architecture documentation, SDK documentation, privacy documentation, and instructions necessary to reproduce the MVP will be publicly available.
Permissions and Consent
Program Requirements