Design: Product scope for hybrid routing (manual split vs automation) #65
Labels
No labels
agent:fix_bugfix
agent:fix_conflicts
agent:fix_security
agent:gap_analysis
agent:implement
agent:implement
agent:implement
agent:open_issues
agent:ready
agent:research
agent:security_audit
agent:verify
architecture
backend
blocker:hybrid
blocker:launch
blocker:limit-orders
blocker:v2
block:log_only
block:security
bug
ci
contracts
correctness
deploy
dev
devops
docs
documentation
duplicate
e2e
enhancement
epic
feature
frontend
functional-completion
gas
good first issue
governance
help wanted
high-risk
hooks
hybrid
indexer
infra
infrastructure
integrators
invalid
launch-blocker
limit-orders
localnet
localterra
low priority
missing-implementation
needs-design
ops
performance
priority
high
priority
medium
product
qa
QA
question
ready
ready
research
scripts
security
security-hardening
smartcontracts
tech-debt
testing
ux
UX
v2
verification
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
code/cl8y-dex-terraclassic#65
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type
needs-design
Evidence
frontend-dapp/src/pages/SwapPage.tsx— manualpool_input/book_inputindexer/src/api/route_solver.rs— clients patchhybridoff-chainRationale
Defines V1 launch (user-only split) vs future indexer-assisted routing.
Dependencies
Coordinate with #64; may merge into one ADR if preferred.
Acceptance criteria
Epic
#56
marked this issue as related to #56
mentioned in issue #75
@PlasticDigits checked both ADR + implementation.
ADR exists and decides manual split + server-assisted simulation:
docs/adr/0001-hybrid-quoting-and-routing.md— GET/api/v1/route/solvestays pool-only for backward compat, POST accepts optionalhybrid_by_hoparray (one optional payload per hop, aligned with BFS order). Indexer merges splits into router ops and runs chain'ssimulate_swap_operationsfor the full hybrid quote.Implementation present:
indexer/src/api/route_solver.rs:49—hybrid_by_hop: Option<Vec<Option<HybridHopJson>>>on POST bodyroute_solver.rs:213—apply_hybrid_by_hopmerge logicNothing appears to be blocking. If there's a deeper design gap I'm missing, tag me with specifics.