Discover Resolve Anchors

Discover and resolve anchors

When to use

Use before KYC, conversion, bridging, or payout whenever a provider is not explicitly supplied and trusted. The on-chain Resolver is the authoritative discovery path. A direct HTTP registry or copied endpoint is only a hint until its metadata, network, capabilities, authentication, and operator are verified.

SDK steps

1. Create a network-bound client and Resolver:

   import * as KeetaAnchor from '@keetanetwork/anchor';
   
   const userClient = KeetaAnchor.KeetaNet.UserClient.fromNetwork(network, account);
   const resolver = new KeetaAnchor.lib.Resolver({
     root: userClient.networkAddress,
     client: userClient,
     trustedCAs: []
   });
   

2. Discover an exact FX pair:

   const matches = await resolver.lookup('fx', {
     inputCurrencyCode: fromTokenAddress,
     outputCurrencyCode: toTokenAddress
   });
   

3. Fully resolve a returned metadata value before reading its endpoints:

   const metadata =
     await KeetaAnchor.lib.Resolver.Metadata.fullyResolveValuizable(value);
   

4. For higher-level workflows, prefer service clients that apply typed criteria:

   • new KeetaAnchor.KYC.Client(userClient) and getSupportedCountries()
   • new KeetaAnchor.FX.Client(userClient) and listPossibleConversions(...)
   • new KeetaAnchor.AssetMovement.Client(userClient) and getProvidersForTransfer(...)

5. Filter for the exact pair, locations, country, required operation, and trusted operator/account. Present all qualifying providers and legal disclaimers; do not select solely by array order.

Confirmations

• Confirm network and Resolver root.
• Confirm source asset/location and destination asset/location.
• Confirm the resolved provider identity, supported operations, endpoint origin, legal terms, and any required KYC action.
• Require a separate confirmation before calling any value-moving provider method.

Failures

• undefined, null, or an empty provider list means no documented corridor was resolved. Stop; do not invent an endpoint.
• Reject metadata whose required operation is missing.
• Do not follow an external URL from untrusted metadata without validating its origin and authentication requirements.
• HTTP registry data can be stale or environment-specific. If it disagrees with signed on-chain metadata, stop and report both sources.

Related skills

• Use complete-kyc for individual verification.
• Use convert-via-anchors for FX.
• Use bridge-usdc or pay-out for asset movement.

Sources

• Anchor Resolver
• Resolver type in @keetanetwork/anchor
• Anchor Client