XDC のオラクルデータと証明
FeedPlumb · Launch, Build

FeedWire Plugin integration studio

Plugin price feeds and Automation wired into your contracts, tested and documented.

Workspace プランFixed-scope projects

Included in: Custom quote

FeedWire at a glance

Who it is for
Protocol teams that want Plugin integrated correctly the first time.
The problem it solves
Oracle integration bugs are among the most expensive in DeFi, and in-house teams often lack the time to get every edge case right.

What it does

  • Checked feed adapters with staleness, round and access handling
  • Automation upkeep locked to your forwarder
  • Foundry unit tests and read-only mainnet fork tests
  • An audit-preparation pack with every tool finding triaged
  • You keep your keys and deploy the contracts yourself

Engineering work, not an audit or a security guarantee. You will keep your keys and deploy yourself. We will never take custody, deploy with our own keys or send transactions to mainnet.

What we will deliver

  • Feed integration: each feed wrapped in a checked adapter (staleness, round checks, "No access" handling, optional bounds and deviation guard), in the feed's native decimals.
  • Automation: an upkeep whose performUpkeep is locked to a forwarder you control and re-checks its condition.
  • Tests: Foundry unit tests with mocks and read-only fork tests against XDC mainnet.
  • Audit preparation: Slither and Aderyn findings triaged, invariant-test skeletons and a threat model per contract.
  • A self-contained repository with the FeedKit templates pinned at a fixed version.
  • VRF (randomness) on request and quoted separately; Plugin VRF on XDC is experimental.

Request a quote

Tell us about your project and we'll come back with a fixed scope and price.

Available by quote. Plans and API keys are in your Workspace. Questions go to support@feedplumb.com.

How an engagement will run

  1. Intake: network, repository, toolchain, the feeds you need (addresses from Plugin's official list, decimals, heartbeat, access), acceptable staleness and failure behaviour, Automation trigger, admin roles and security contact.
  2. Integration: adapters and guards in your contracts; the upkeep will ship with its forwarder unset until you register it.
  3. Upkeep registration: you will register and fund the upkeep with Plugin Automation and set the forwarder from your owner account.
  4. Testing: unit, fork and invariant tests must pass, and every tool finding will be triaged as confirmed, false positive or accepted risk.
  5. Delivery: code, tests, commands, a deployment-parameter table, known risks and the audit-preparation pack, shared privately.

Request a custom scope

Integration work is scoped and quoted per project. Open Workspace or contact support@feedplumb.com with your network, repository and requirements.

How paid services work: Paid services terms.