Skip to content

feat(demo): run the local RFQ demo with one command#50

Open
0xMuang wants to merge 1 commit into
feature/operator-dashboard-api-proxyfrom
feature/demo-one-command-launcher
Open

feat(demo): run the local RFQ demo with one command#50
0xMuang wants to merge 1 commit into
feature/operator-dashboard-api-proxyfrom
feature/demo-one-command-launcher

Conversation

@0xMuang

@0xMuang 0xMuang commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

What changed\n\n- add scripts/demo.sh to start the local demo stack\n- start Anvil, deploy the selected asset profile, RFQ backend, Operator API and dashboard in order\n- pass the generated deployment artifact to the read-only Operator API\n- print the dashboard URL and clean up all child services on Ctrl-C\n- refresh the RFQ demo guide and regression markers\n- harden demo maker restore with an explicit monotonic operator nonce\n\n## Verification\n\n- RFQ-only Anvil E2E passed\n- one-command launcher reached the dashboard-ready state\n- Ctrl-C stopped ports 8545, 8787, 8788 and 8790\n- dashboard and RFQ backend smoke tests passed\n\nCloses #49

Operators should be able to reproduce the protected RFQ flow without manually coordinating four local services.\n\nConstraint: the launcher remains local Anvil-only and reuses the existing artifact-driven E2E deployment.\nRejected: asking presenters to start and stop each service manually | it creates avoidable setup and cleanup failures.\nConfidence: high\nScope-risk: moderate\nDirective: Keep the launcher as a reference/demo workflow; do not treat its deterministic accounts as production custody.\nTested: scripts/e2e-anvil.sh --profile buidl-like --mode rfq; scripts/demo.sh startup and Ctrl-C cleanup; dashboard and RFQ backend smoke tests; git diff --check.\nNot-tested: hosted production orchestration, real TA/Securitize integration and live-chain deployment.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant