Skip to content

The Beautiful Bactrian Camel 🐫 (v0.3.0) Developer Release Notes
Compare
Choose a tag to compare
@InoMurko InoMurko released this 24 Oct 20:01
· 15 commits to master since this release
v0.3.0
1abd873
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Every release promises new and exciting things happening with Boba Network, and the Beautiful Bactrian Camel (v0.3.0) release is no exception. Amazing new partners, great new features, and the continual effort to make user experience even better for contributing developers and users alike. Let's dive right into the latest changes and fixes.

We’re Ironing Out the Wrinkles to Make Transactions Even Smoother

  • We fixed the ABI, or Application Binary Interface, which is an interface that makes sending transactions easier. It was encountering errors, and we resolved them.

  • Because some tokens are not ERC20 compatible, our standard ABI wasn’t working for those tokens, and as stated above, we use ABI to make sending transactions easier. In order to solve this problem, we’re now fetching token info (name, symbol, etc) from a maintained single file instead of querying it from the blockchain, and as a result, this improves speed as well.

    See the PRs for more details:

    [PR#376]
    [PR#408]

New Members of the Boba Network Multichain Ecosystem

There have been some incredible new additions to the multichain ecosystem here at Boba Network, so let’s take a look at what’s new.

  • Since we’ve added more chains to the Boba’s ecosystem, we’ve created a brand spanking new page on the gateway where you can easily see and access all of the chains available on Boba Network, both Mainnet and Testnet. See the image below to check it out.

Screen Shot 2022-10-31 at 2 07 28 PM

  • Beamer is now available on the Mainnet, so in this release, you’ll see that reflected on the ecosystem page, as you can see from the image below.

Screen Shot 2022-10-26 at 12 28 25 PM

  • We added SushiSwap to the ecosystem page

  • We added the L2StandardTokenFactory address for the Boba Mainnet

    See the PRs for more details:

    [PR#384]
    [PR#411]
    [PR#430]
    [PR#427]

Bridge to Alt L1s

You may have already heard, but Boba Network now offers bridging to non-Ethereum L1s, and we’ve made several changes to reflect that.

  • We’ve added the ability to bridge from Boba to other L1s, like BNB and AVAX

186454635-2e3bded0-9b89-43ee-a9ff-1963514be998

  • We’ve improved the UI/UX of bridging to non-Ethereum L1s, for instance, by disabling the button for transactions when not enough ETH is detected in the user’s wallet to cover estimated transaction fees.

    See the PRs for more details:

    [PR#297]
    [PR#401]

We’re Getting Ready for Boba V3

Boba v3 is coming, and we’re already preparing for it to land.

  • We’ve moved Bedrock-specific architecture to our new v3-repositories in anticipation for Boba V3, which, if you didn’t know, is going to introduce a lot of awesome changes to the Boba Network, which will be compatible with Optimism’s bedrock, and will utilize the Erigon client to continue to encourage client-diversity. Bedrock submodules were removed in this effort to start making the transition to Boba v3.

    See the PR for more details:

    [PR#389]

Tweaks and Changes Here and There

Overall improvements have been made to a variety of areas, because we’re thorough. So here’s what we’ve been up to, gradually making Boba more intuitive for users and contributing developers alike.

  • We’ve implemented an important fix, ensuring that if minting fails on the other layer during bridging, the NFT being bridged returns back to the original owner.

  • We’ve improved on loading speed because faster is better, obviously

  • We’re reducing crashes and errors by increasing the interval for fetching gas prices, so that you can focus on your transactions, and we focus on making that process as smooth as possible.

  • We worked on updating the message relayer so that the message relayer should only relay the messages to the L1 liquidity pool and L1 message contract. For obvious reasons, We don't want to cover the cost for relaying the random messages, so we added a whitelist for the message relayer and message relayer fast.

  • …And we fixed some typos and error code messages

    See the PRs for more details:

    [PR#419]
    [PR#410]
    [PR#394]
    [PR#394]
    [PR#416]
    [PR#359]
    [PR#379]

Assets 2
Loading