Skip Go Fast primary sources — 2026-05-09

Classification takeaway

Skip Go Fast is most useful as a solver-financed fast-transfer protocol that sells latency by having solvers front destination-side liquidity and execution before final settlement catches up. It should be kept distinct from Skip Go API, which is a broader interoperability product layer and route aggregator. The protocol-level question is where speed, risk, and rent sit once a solver fills early and settles later.

Primary sources reviewed

1. Official Go Fast docs page — https://docs.skip.build/go/advanced-transfer/go-fast

   • Best first-party overview of the protocol’s user flow, fee model, supported chains, and solver framing.
   • Explicitly says Go Fast is a decentralized bridging protocol and links to the protocol contracts and solver implementation.

2. Skip Go docs introduction — https://docs.skip.build/go

   • Useful for distinguishing Go Fast the protocol from Skip Go the wider interoperability platform.
   • Shows how Go Fast sits alongside other bridges and messaging systems inside a broader routing product.

3. Supported ecosystems and bridges — https://docs.skip.build/go/general/supported-ecosystems-and-bridges

   • Helpful for scoping where Go Fast actually fits in the route stack.
   • Shows Go Fast as one component in an EVM/Cosmos interop menu rather than the whole platform.

4. Cross-chain failure cases — https://docs.skip.build/go/advanced-transfer/handling-cross-chain-failure-cases

   • Especially valuable because it documents failure and refund behavior rather than only happy-path marketing.
   • Confirms timeout/refund behavior when an intent receives no solver response before expiry.

5. Go Fast contracts README — https://raw.githubusercontent.com/skip-mev/go-fast-contracts/main/README.md

   • Best technical source for the protocol’s intent, fill, and settlement flow.
   • Explicitly describes maximally ERC-7683-compatible design goals and the source/destination settlement sequence.

6. Go Fast deployment guide — https://raw.githubusercontent.com/skip-mev/go-fast-contracts/main/DEPLOY.md

   • Reveals the cross-environment deployment model and how remote contracts are linked between Solidity and CosmWasm sides.
   • Useful evidence that Go Fast is concretely spanning EVM and Cosmos execution environments.

7. Reference solver README — https://raw.githubusercontent.com/skip-mev/skip-go-fast-solver/main/README.md

   • Best practical source for what “permissionless solver” means operationally.
   • Shows the real work includes monitoring orders, filling, settling, verifying transactions, rebalancing, and managing gas/capital across chains.

Key takeaways from primary sources

• Go Fast’s speed is fundamentally balance-sheet speed. The user experience is fast because solvers pre-position capital and accept settlement delay and reorg risk.
• The most useful distinction is between protocol completion and user-perceived completion. Users are done when the solver fills; the protocol is not done until reimbursement, verification, relaying, and rebalancing complete.
• The open-source solver docs are analytically important because they show where real centralization pressure can return: capital thresholds, chain connectivity, gas management, relayer operations, and operational sophistication.
• Go Fast belongs in the same family as other intent/solver systems, but it is not merely an abstract order API. The contracts and docs are concrete about submitted orders, fills, settlement initiation, relaying, and reimbursement.
• The protocol docs explicitly say enabling Go Fast prioritizes speed over lower fees. That means the system should be analyzed as a market for latency and temporary inventory, not just as generic interoperability infra.
• The failure documentation is unusually valuable. Timeout and refund paths make visible that the hardest problem is not only message verification; it is ensuring users have an understandable outcome when no solver is willing to warehouse the risk.
• The technical docs and solver README indicate settlement currently uses a cross-chain messaging system plus attestation/relay flow, which makes Go Fast a useful comparison class against proof-heavier designs like RIP-7755.

Mechanism lens

• Best current classification: solver-financed fast bridge / faster-than-finality transfer rail / latency market for cross-chain execution.
• Closest comparison classes in the current corpus:
  • ERC-7683 for intent-envelope and filler-network interoperability.
  • Across for solver-mediated bridging and fast-fill design.
  • RIP-7755 as a useful foil because it aims for proof-based post-execution compensation rather than attested messaging settlement.
  • Hyperlane as a likely important dependency/comparison in settlement and relay design.
• Reusable insight: “instant bridging” often means someone else is warehousing finality delay, inventory fragmentation, and rebalancing cost — and the real protocol question is who gets paid for that and under what failure/refund rules.

Whitepaper / docs status

• The official Go Fast docs link to a whitepaper hosted on Notion: https://skip-protocol.notion.site/EXT-Skip-Go-Fast-b30bc47ecc114871bc856184633b504b
• That whitepaper was not retrievable in a useful way through lightweight fetch tooling during this pass.
• The accessible docs and repositories were still strong enough to justify keeping Go Fast in the active corpus because the mechanism and implementation details were clear from first-party materials.