node bundlr expects a string or uint8 of the secret key to use for funding. Please supply it here.
the bundlr network to connect to. supplying "devnet" or "mainnet" will automatically connect you to an appropriate bundlr node for those solana chains.
must be at least 1. Bundlr is funded off of an account kept by them. When current funding is insufficient for an upload, solstory will calculate how much the current item costs and add that amount, multiplied by the bundlrFundingRatio, to the account. This takes a full solana transaction confirmation, so selecting a higher ratio will allow you to amortize this cost over a larger number of transaction. For example, a ratio of 100 will allow for effectively 1.01 solana transactions for upload instead of a 2 solana transactions (one for the bundlr fee, one for the solstory stuff) per upload. Use cases with inconsistent or possibly unbounded item sizes may wish instead to manually prefund and set this ratio to something low, like 1.1.
bundlr needs to sign messages to validate client side transactions, the function to do this can be found in useWallet of the @solana-labs/wallet-adapter github repo.
bundlr needs to sendTransactions to validate client side transactions, the function to do this can be found in useWallet of the @solana-labs/wallet-adapter github repo.
the bundlr network to connect to. supplying "devnet" or "mainnet" will automatically connect you to an appropriate bundlr node for those solana chains.
must be at least 1. Bundlr is funded off of an account kept by them. When current funding is insufficient for an upload, solstory will calculate how much the current item costs and add that amount, multiplied by the bundlrFundingRatio, to the account. This takes a full solana transaction confirmation, so selecting a higher ratio will allow you to amortize this cost over a larger number of transaction. For example, a ratio of 100 will allow for effectively 1.01 solana transactions for upload instead of a 2 solana transactions (one for the bundlr fee, one for the solstory stuff) per upload. Use cases with inconsistent or possibly unbounded item sizes may wish instead to manually prefund and set this ratio to something low, like 1.1.
Generated using TypeDoc
This is the api object. You can treat it just like a regular anchor program object, but it has the additional "client" and "server" namespaces for common client and server tasks.