/**
 * did:web resolution using caller-provided {@link HttpGetService} so DID document
 * fetches share the same cache as JSON-LD context loads (e.g. Keyv in
 * transaction-service). The stock {@link DidWebResolver} uses
 * `@interop/http-client` and bypasses that cache.
 *
 * Fragment dereference logic matches `@interop/did-web-resolver`
 * `getNode` (suite context map aligned with that package).
 */
import { DidWebResolver } from '@interop/did-web-resolver';
import type { HttpGetService } from '../services/http-get-service/http-get-service.js';
/**
 * did-io driver for did:web that loads documents via `httpGetService`.
 *
 * Returns a {@link DidWebResolver} instance (which implements `did-io`'s
 * `DidMethodDriver`, so it can be registered via `CachedResolver.use(...)`, and
 * exposes `use(...)` for registering key suites) with only `get` overridden to
 * route fetches through the caller's `httpGetService`. The generation/key
 * methods (`generate`, `fromKeyPair`, etc.) are inherited unchanged; a verifier
 * never calls them.
 */
export declare function didWebDriverWithHttpGet(httpGetService: HttpGetService, options?: ConstructorParameters<typeof DidWebResolver>[0]): DidWebResolver;
//# sourceMappingURL=did-web-driver-with-http-get.d.ts.map