Pear Worklet WDK
Low-level HRPC infrastructure for running WDK inside a Bare worklet
Pear Worklet WDK is the low-level transport and handler layer for running WDK inside a Bare worklet. It provides the HRPC client, the registerRpcHandlers() server helper, and the typed request payloads needed to initialize WDK, call wallet methods, and reset selected wallet modules from the host app.
Powered by @tetherto/pear-wrk-wdk.
Features
- Bare worklet bridge: Connect a host app to a worklet through the shipped
HRPCclient and generated HRPC schema - Typed lifecycle requests: Initialize WDK with
initializeWDK({ config, encryptionKey, encryptedSeed })and tear it down withdispose() - Selective wallet resets: Re-register only the wallet modules listed in a new worklet
networksconfig usingresetWdkWallets({ config }) - Generic wallet method calls: Call account methods through
callMethod({ methodName, network, accountIndex, args, options }) - Dynamic registration hooks: Register additional wallets or protocols with
registerWallet()andregisterProtocol()
Why this matters
- You can keep WDK state and signing operations off the main thread in Bare-based apps
- You can reconfigure selected wallet modules without fully disposing the worklet
- You can use one transport layer across custom mobile, desktop, or embedded Bare integrations
Use this package when you need direct control over the worklet host and RPC layer. If you want generated worklet entry files instead, start with @tetherto/wdk-worklet-bundler.
Pear Worklet WDK Configuration
Build the worklet context and pass the JSON config payloads used by initialize and reset requests
Pear Worklet WDK API Reference
Review the exported class, server helper, and request shapes