# Milestone 0:
*Alpha on private and/or public testnet (already achieved)*

Based on about one person-year of sweat equity, the team has already released a limited “friend and family” (but public, pre-) alpha, with the goal of getting early feedback. The alpha will help attract motivated, enthusiastic evangelists that are excited to use the system and grow our community. We aim to actively use Dexorder in a test environment that is a private “digital twin” of the production Arbitrum Uniswap pools, so that we can flush out bugs in the UX, improve its usability, and validate its functionality.

An early public alpha test has been released at https://alpha.dexorder.trade and is open to the review committee of this grant. It is running on a private (Anvil based) chain and will be released to the public Arbitrum Sepolia testnet (but not publicized) as we continue development, and according to this roadmap. We are actively adding features and order types to the alpha as you read this proposal.

# Milestone 1
*Finalize all core contract code slated for v1, and associated UX*

Starts month 1, lasts 1 months–concurrent with Milestone 2  
Estimated allocation: $20k  
KPI:  
- Contract code that implements all exposed functionality used by the minimal dApp
- Completed (already alpha) work:
  - Overall dApp structure
  - Backend
  - TradingView integration
  - Order functionality:
    - Limit Ladders
    - DCA/TWAP
    - Cancel All

- Milestone work:
  - Additional order functionality:
    - Diagonal limit orders
    - One-Cancels-the-Other (OCO) order groups
    - Conditional Orders (for example, stop-loss and take-profit)
    - Tiered allocations (70% of the total order amount allocated to a Ladder with 30% in a DCA)
    - Deadlines and delayed start times
    - Custom Order builder (detailed editing of each tranche)
  - Display lines/shapes for already-placed orders

Prior to engaging in any security audits or bug bounty programs, the team will finalize all contract code and freeze further contract development. This step will include careful analysis of gas efficiency, access controls, and execution infrastructure. It will also include an internal code quality review, with the aim of releasing clean, well commented Solidity source code for public comment, review and audit.

Contract feature lock will be driven by concurrent implementation of minimal dApp features (see Milestone 3) accessing all desired aspects of the order types slated for v1.

# Milestone 2
*Infrastructure and backend development*

Starts month 1, lasts 2 months  
Estimated allocation: $20k (additional over Milestone 1)  
KPI:  
- Stable private testnet deployment lasting at least 2 weeks
- Observed no necessary changes to core contracts
- Several order types functioning as expected
- Steady closure of open bugs

Although the OMS uses on-chain resources for the order lifecycle (including order execution), the dApp depends on certain off-chain facilities to support its dynamic/live UX. For example, restartable Python and NodeJS components extract on-chain logs and EVM storage data, and transmit state changes to live dApp instances.

Note that the back end is not a source of truth and does not persist user data. It acts only as a bridge to the blockchain for the code running in users’ browsers and for the backend’s triggering of executions. Portions of this system may be released so that third parties may perform this execution function too, on top of our code. This is a familiar architecture in Web3.

We expect to stabilize portions of the project in Milestone 2 (e.g. the EVM contracts) about a month prior to stabilizing the backend, other infrastructure, and the UX. We anticipate that the dApp and other features which interact with the core contracts will undergo ongoing development in order to benefit from early user interactions and input.

# Milestone 3
*Release Alpha on Arbitrum-Sepolia*

Starts month 3, lasts 1 month  
Estimated allocation: $20k  
KPI:  
- Stable(ish) public alpha on Arbitrum testnet
- Acquisition of at least 50 active evangelists

The team will deploy the latest versions of core and periphery contracts to the Arbitrum testnet, and will host the dApp on always-on cloud resources with the aim of maintaining as close to 100% uptime as possible. This will help the team understand ongoing support and maintenance resources, and gauge stability of the backend.

During this period, the team will publicize the Dexorder Alpha’s existence in relevant social media groups, among a more extended set of friends and family, and within relevant trader communities.

# Milestone 4
*Beta release on Arbitrum mainnet*

Starts month 4, lasts 1 month  
Estimated allocation: $20k  
KPI:  
- Final audit-ready code of both contracts, dApp/UX, and public portions of the backend
- Release onto Arbitrum mainnet
- Identified bugs, improvements and features slated for closure by this public Beta

The team will identify all bugs, improvements, and feature additions slated for closure by the end of the audit for public Beta. Finally, it will release the contracts and dApp functionality to Arbitrum mainnet. A stated purpose of this milestone is to finalize the code that will be submitted for audit and bug bounties (see below).

# Milestone 5
*Entity formation and legal agreements*

Starts month 1, lasts 5 months–concurrent w/ Milestones 1-4
Estimated allocation: $50k (for legal fees and services)
KPI:
- Published entity information, including public portions of the operating agreement (if any).

While progressing the technical portions of the project (which take priority over starting work on this milestone), we will identify counsel and engage to form an entity (and author its operating agreements). The entity will house the intellectual property ownership rights, own the project’s governance, control the project’s interfaces with the fiat currency financial system (e.g., bank accounts), and safeguard the project’s wallet keys and on-chain resources. The team will be efficient in this use of funds, and may engage in simpler contractual agreements with existing entities in lieu of forming a new entity. The team also anticipates requesting opinion letters if specific regulatory concerns are identified.

At a high level, we estimate on the order of $10k each for foreign entity formation, opinion letters relative to regulations, minimum bank deposits/retainers, terms of service, LLC and other agreements, etc. The allocation requested is an underestimate, but the team will stagger spend according to the project’s growth and instant needs.

# Milestone 6
*User acquisition & continued dApp improvements*
Starts month 5, lasts 2 months–concurrent with Milestone 7  
Estimated allocation: $20k  
KPI:  
- Conversion ratios: page landing, connected wallet, placed order
- Discord/Reddit active users

The team will develop marketing resources, including short-form video, text documentation and tutorials, and online step-by-step how-to resources highlighting Dexorder’s features and value proposition. The initial marketing plan will distribute minimum buys across multiple channels including crypto-focused ad networks like Coinzilla, crypto-friendly platforms like Reddit, and direct placements on sites like dexscreener. Tim has extensive experience in ad tech and will identify the best performing spends across multiple metrics for awareness and engagement.

We will also be actively engaged with open communities in our Discord and sub-Reddit. Tim grew the Zeropond project (2016) out of his involvement in the Zcash community chats, and realized multi-million dollar global sales without any marketing spend, just enthusiastic engagement with the grassroots community who wanted the project to grow.

Concurrent with the audit (see Milestone 7), the team will be focused on community interactions and early user/evangelist acquisition with the aim of accelerating public awareness and adoption.

At this stage, we anticipate Dexorder to be in a fairly stable Beta release, handling real orders against actual Uniswap v3 pools on Arbitrum One mainnet; but, we will be limiting the total number of users, the number of orders per user, and will also impose order size limits so that the financial exposure to unaudited and beta code will be limited. We may also limit the set of Uniswap pools that Dexorders interact with.

During these two months the audits will be occurring concurrently (see Milestone 7), and the team will be continuously improving the dApp and back end.

# Milestone 7
*Perform thorough code/security audit*

Starts month 5, lasts 2 months  
Estimated allocation: $60k (for audit fees and incentives)  
KPI:  
- Positive audit results and/or improvement recommendations
- Published regression & unit testing framework for the Dexorder contracts
- All public beta bugs/improvements are closed

We plan to engage in a thorough security audit via a variety of private and public resources, including hiring a private audit firm and/or registering with public bug bounty systems such as code4rena and codehawks.

While we recognize the importance of independent third party attestations about the safety and quality of our contracts, we are also familiar with the many limitations of auditors, and the potential for “security theater.” Therefore, we also intend to post our testing frameworks and associated results prior to live Aribtrum One mainnet deployment of the final contracts.

We intend to audit this internal testing framework, which we plan to utilize during development to drive feature lock. This audited testing framework will extend the utility and value of the initial audit.

All bugs and features slated for the public production release will be closed by the end of this milestone.

# Milestone 8
*Incorporate security audit results*

Starts month 7, lasts 1 month  
Estimated allocation: $20k  
KPI:  
- Satisfaction of all audit recommendations
- Sign-off by private auditors
- Feature list for final public release of dApp identified


We anticipate the audit process will surface various recommendations and may identify faults in the system. Audit recommendations will be incorporated into the system and any new bugs will be closed. The team will identify the set of bug fixes requiring development for final public production release.

# Milestone 9
*Production release of final contracts to Arbitrum one mainnet*

Starts month 9, lasts 1 month  
Estimated allocation: $20k  
KPI:
- Full public release


Once final private audit sign-off is received, the finalized contracts will be released to the Arbitrum mainnet, and the public dApp will be switched over to utilize finalized contracts. Ongoing user community growth will occur. The dev team will continue to make dApp improvements if necessary.

# Milestone 10
*Infrastructure Dev Tools*


Starts month 10+, lasts 2 months  
Estimated allocation: None (will utilize grant $ remaining from prior Milestones)  
KPI:  
- SDK release
	
Dexorders are stored entirely on-chain and may be placed by anyone who can construct and send a Dexorder contract transaction. We will build a Javascript SDK to make it easy for programmers to build Dexorders and submit them directly to the Arbitrum contracts without any interaction with the Dexorder UX or backend. This opens up Dexorder to automated and algorithmic trading. The SDK will be open sourced and posted publicly on GitHub.

In addition, we will consider how to release a Solidity Uniswap v4 + Dexorder hook SDK to naturally integrate Dexorder’s functionality into v4 pools.
