Location:
/build/sdk/api-reference/account/ vs. /build/sdk/guides/create_account/ vs. /build/sdk/overview/
Problem:
The Account API reference imports from @provablehq/sdk/testnet.js:
import { Account } from "@provablehq/sdk/testnet.js";The Create Account guide: the page most JS developers will land on first imports from @provablehq/sdk with no subpath:
import { Account } from '@provablehq/sdk';The SDK overview page only refers to the package as @provablehq/sdk and never mentions network-specific entry points (testnet.js, presumably mainnet.js, canary.js). Nothing in the surveyed pages explains when to use which.
Consequence:
A developer copies the guide's import, then copies an example from the API reference, and ends up with two import paths in the same file, one of which may import an entry point that doesn't exist for their target network. Agents generating SDK code will pick whichever they saw first and silently target the wrong network.
The fix:
Document the network entry-point convention in the SDK overview (@provablehq/sdk vs. @provablehq/sdk/testnet.js vs. mainnet/canary equivalents, with explicit guidance on which to use for which target). Then sweep every guide and API reference page to use the same import path or to explain why theirs differs.
Location:
/build/sdk/api-reference/account/vs./build/sdk/guides/create_account/vs./build/sdk/overview/Problem:
The Account API reference imports from
@provablehq/sdk/testnet.js:The Create Account guide: the page most JS developers will land on first imports from
@provablehq/sdkwith no subpath:The SDK overview page only refers to the package as
@provablehq/sdkand never mentions network-specific entry points (testnet.js, presumablymainnet.js,canary.js). Nothing in the surveyed pages explains when to use which.Consequence:
A developer copies the guide's import, then copies an example from the API reference, and ends up with two import paths in the same file, one of which may import an entry point that doesn't exist for their target network. Agents generating SDK code will pick whichever they saw first and silently target the wrong network.
The fix:
Document the network entry-point convention in the SDK overview (
@provablehq/sdkvs.@provablehq/sdk/testnet.jsvs. mainnet/canary equivalents, with explicit guidance on which to use for which target). Then sweep every guide and API reference page to use the same import path or to explain why theirs differs.