Engagement guide
This is the client-facing description of how work with the desk runs. Fees are stated in the signed engagement letter and do not appear here.
The pipeline
| Step | What happens | What you receive |
|---|---|---|
| 1. Intake | You submit entity, name, business email, jurisdiction, service, use case, and details through the site form or by email to desk@flashrouter.io. | A reference id. |
| 2. Written scope | The desk replies from a flashrouter.io address within two business days with a written scope or a written no. | Scope, or a reason. |
| 3. Verification | Entity documents and beneficial ownership are checked. Every address the desk will touch is screened against sanctions lists. On XRPL, a verification credential is issued to your account. | Verification confirmation; credential transaction hash on XRPL. |
| 4. Engagement letter | Scope, deliverables, fees, ownership, and what the desk never does, fixed in writing. | Countersigned letter. |
| 5. Build and simulate | Service-specific work (below). Nothing touches mainnet before this step is complete. | Simulation output, testnet hashes. |
| 6. Sign-off | You confirm the simulation in writing. | — |
| 7. Mainnet action | Each mainnet write is preceded by a receipt line: what, where, and how it is rolled back. | Transaction hashes. |
| 8. Handoff and evidence pack | Ownership transfers to your address. | Evidence pack (below). |
Replies come only from flashrouter.io addresses. Anything else claiming to be the desk is not.
Service-specific work
Flash loans. Depth is quoted first. You provide the strategy or a specification for it. The contract is simulated on a fork, deployed to Base Sepolia for you to run, then deployed to Base mainnet with source verified on the explorer and ownership transferred to your address.
Proof-of-Funds attestations. The desk confirms what your counterparty actually needs; if it is a bank letter, a source-of-funds report, or a regulator's form, an attestation is not that and the desk says so. The address is screened, the attestation is issued against two finalized observations, and you receive the envelope and a verify link. Attestations expire in 24 hours by design.
XRPL tradelines. Your account is read from the ledger, the facility is pre-checked, a verification credential is issued and accepted, you request the trust line from your own wallet, and the issuer authorizes it. Draws, repayments, accrual postings, and any collateral escrow are ledger transactions you can read on any explorer.
The evidence pack
Every engagement closes with a folder you can re-verify without the desk:
hashes.txt: every transaction hash with network and explorer link- contract addresses, verified source, ABI, and simulation traces (flash loans)
- attestation envelopes and verify responses (proof of funds)
- ledger snapshots of trust lines, escrows, and credentials (XRPL)
SHA256SUMS: a manifest over everything above
What the desk will not do
- Hold, pool, or move client assets, or hold any client key.
- Produce a balance, screenshot, or "transaction" that does not exist on a public ledger at a finalized block.
- Attest a balance that existed inside a single transaction, or shorten a window to make a failing balance pass.
- Report an XRPL tradeline to a credit bureau or describe it as consumer credit.
- Work with an entity that fails verification or an address that fails screening.
- State a fee, yield, or outcome on any public surface.
Contact
desk@flashrouter.io for engagements. abuse@flashrouter.io for misuse reports. security@flashrouter.io for vulnerability reports.