Deprecations
This page explains deprecated and legacy-supported APIs in practical terms.
Current deprecated public API
BroadcastAPI.accountWitnessProxy
Status: deprecated but still callable as a compatibility surface.
Current Blurt Layer 1 source rejects witness proxies after hardfork 0.8 in account_witness_proxy_evaluator. New code should use direct witness voting through BroadcastAPI.accountWitnessVote instead.
The helper remains serializable so historical/testnet/compatibility callers see a protocol-shaped operation, but current mainnet applications should not present witness proxying as an available workflow.
BroadcastAPI.claimAccount and BroadcastAPI.createClaimedAccount
Status: deprecated but still callable as compatibility surfaces.
Current Blurt Layer 1 source rejects claim_account and create_claimed_account after hardfork 0.2 in their evaluators. New code should use account-creation flows supported by current chain rules instead of claimed-account tickets.
The helpers remain serializable for compatibility, but current mainnet applications should not advertise them as supported account onboarding workflows.
Nexus.listPopComunities
Status: deprecated but still supported.
Use the correctly spelled Nexus.listPopCommunities instead.
The historical misspelling Nexus.listPopComunities remains available for backward compatibility. It should not be used in new code.
Compatibility rule
Deprecated does not mean removed.
For dblurt, a deprecated API remains callable until there is a deliberate maintainer decision to remove it in a future compatibility-breaking release. New documentation and examples should use the replacement API.
Overload guidance
Nexus methods with pagination or observer context may support both legacy positional signatures and newer option-object signatures.
New code should prefer option-object forms when available because they keep query state together:
await client.nexus.getRankedPosts({
sort: 'trending',
tag: 'blurt',
limit: 10,
observer: null
});Existing positional signatures remain compatibility surfaces unless a future release intentionally changes that policy.
Related API details: