/**
 * did:webvh resolution using caller-provided {@link HttpGetService}, so the
 * `did.jsonl` log and `did-witness.json` fetches share the verifier's cache
 * and any fetch wrapping the caller installed (e.g. a CORS-proxy fallback).
 *
 * Resolution, log verification (SCID, hash chain, entry proofs, witnesses)
 * and `did#fragment` dereferencing all come from
 * `@interop/did-method-webvh`'s driver. This module only adapts
 * `HttpGetService` to the fetch shape that driver accepts.
 */
import type { DidMethodDriver } from '@interop/did-io';
import type { HttpGetService } from '../services/http-get-service/http-get-service.js';
/**
 * did-io driver for did:webvh that loads the DID log via `httpGetService`.
 *
 * A bare DID resolves to its verified DID document; a `did#fragment` URL
 * resolves to that node (e.g. a verification method) with an `@context`.
 * Resolution failures throw a `DIDResolutionError` carrying the resolution
 * error `code`.
 *
 * The underlying driver implements only the resolution half of did-io's
 * `DidMethodDriver` (`method`, `get`, `resolveDID`), which is all
 * `CachedResolver` calls. It has none of the key-generation members, which a
 * verifier never uses, hence the cast.
 *
 * @param httpGetService {HttpGetService}
 * @returns {DidMethodDriver}
 */
export declare function didWebvhDriverWithHttpGet(httpGetService: HttpGetService): DidMethodDriver;
//# sourceMappingURL=did-webvh-driver-with-http-get.d.ts.map