Per the documented example at https://docs.boba.network/other/bridges, to use Boba's NFT bridge our JS client must make an Ethers.js call to <NFTBridge.depositNFT()> to enter a bridge, and <NFTBridge.withdraw()> to exit a bridge.
We also must obtain the exit fee from a call to <BOBABillingContract>.exitFee().
Neither of these three contracts are supplied with ABI JSON in BobaNetwork's Github or documentation. Neither are they verified via "Verify & Publish" on BobaScan or BlockScout (for Bobabase). Nor are usable code examples given for doing these fundamental bridge operations. Example code such as boba_examples/nft_bridging uses unreachable/non-published resources like @boba/contracts/artifacts/contracts/bridges/L1NFTBridge.sol/L1NFTBridge.json, and the since-removed watcher library.
Per the documented example at https://docs.boba.network/other/bridges, to use Boba's NFT bridge our JS client must make an Ethers.js call to
<NFTBridge.depositNFT()>
to enter a bridge, and<NFTBridge.withdraw()>
to exit a bridge.We also must obtain the exit fee from a call to
<BOBABillingContract>.exitFee()
.Neither of these three contracts are supplied with ABI JSON in BobaNetwork's Github or documentation. Neither are they verified via "Verify & Publish" on BobaScan or BlockScout (for Bobabase). Nor are usable code examples given for doing these fundamental bridge operations. Example code such as
boba_examples/nft_bridging
uses unreachable/non-published resources like@boba/contracts/artifacts/contracts/bridges/L1NFTBridge.sol/L1NFTBridge.json
, and the since-removedwatcher
library.