{"version":3,"file":"erc4626-DTDMsHkP-DJ2aMRTo.d.mts","names":["t","SignAndBroadcast","ERC4626Capability","NetworkConfig","CreateERC4626Options","createERC4626","n"],"sources":["../../adapter-evm-core/dist/erc4626-DTDMsHkP.d.mts"],"sourcesContent":["import { t as SignAndBroadcast } from \"./helpers-ZShvV2Sa.mjs\";\nimport { ERC4626Capability, NetworkConfig } from \"@openzeppelin/ui-types\";\n\n//#region src/capabilities/erc4626.d.ts\n\n/**\n * Options for {@link createERC4626}.\n *\n * `vaultAddress` is the deployment-specific ERC-4626 vault the capability operates against\n * (its methods take amount/share arguments rather than per-call addresses). The capability\n * never touches wallet/signing infrastructure — writes route through `signAndBroadcast`.\n */\ninterface CreateERC4626Options {\n  signAndBroadcast: SignAndBroadcast;\n  vaultAddress: string;\n}\n/**\n * Create the EVM ERC-4626 tokenized-vault capability.\n *\n * Mirrors {@link createERC3643} / {@link createIRS}: assembles the service, adapts the\n * injected `signAndBroadcast` into the service's executor via the shared\n * {@link adaptSignAndBroadcast} helper, and wraps the result with `guardRuntimeCapability`\n * for the `RuntimeCapability` surface and idempotent `dispose()`.\n */\ndeclare function createERC4626(config: NetworkConfig, options: CreateERC4626Options): ERC4626Capability;\n//#endregion\nexport { createERC4626 as n, CreateERC4626Options as t };\n//# sourceMappingURL=erc4626-DTDMsHkP.d.mts.map"],"mappings":";;;;;;AAaoC;;;;;;;UAD1BI,oBAAAA;oBACUH;;;;;;;;;;;iBAWHI,aAAAA,SAAsBF,wBAAwBC,uBAAuBF"}