Post every project I will be writing an apologue or two about the development process and mythology that stems from it. This would be the inaugural one, so let’s dive in to the saga of fBOMB. Obviously being a developer I must start with a requirements and some sort of npm/yarn install right?

{
  "devDependencies": {
    "@TL/CR": "^0.0.1",
    "@requirements": "^1.0.0",
    "@MaxFlowO2": "latest"
  }
} 

     So this saga comes with me as the 3rd gen developer of the first meme coin on Fantom. Yes, we are talking about $BOMB on chainID 250. Obviously there was a needed wrapper so wBOMB came from a developer named lookee. He also did a great UI. But the man, the myth, the legend also named Fiery Dev, aka @Dev_Enjoys on bird app came to me while doing updates with wBOMB. The challenge get BOMB to all the chains. The answer, omnichain. Why me? Answer, TinyDaemons…

     First thing is first you must get the original contracts so you can build localhost and or testnet editions for testing. So copied the verified source from FTMScan found here BOMBv3 and wBOMB. Next challenge was 1822 UUPS ERC20. I didn’t like OZ’s so rolled my own called Lib20 with a struct named Token, aka Lib20.Token. Tied that to EIP-20, and off to the races. Added the Non Blocking Receiver from LZ and made the payload uint256 amount, kind of obvious there.

Now here were the requirements:

• One way deposit BOMB/wBOMB → fBOMB

  • Smart contract handles 100% of burning it all

    • wBOMB can not burn

    • BOMB can burn

• Bridgable

  • LZ enabled via traverseChains(uint256 amount)

• Taxation

  • 1% on all intra-chain transactions

    • Same as wBOMB on Fantom

    • Same as BOMB on Fantom

  • 1% tax to treasury for bridging

  • Exemption for certain v2 AMM’s and Balancers

• Upgradable

  • EIP 1822 UUPS

• Tied to fbomb.finance

     We can fast forward to currently and stop the technical jargon and you can see the deployed contract source here. It is currently on Optimism and Fantom blockchains and will be migrated to five others very soon. Why take my word for it, look here.

     So I’ll post another update this when the UI is done, for for now I must say, “Bon voyage.” This was the birth of the Max-20/2023 UUPS LZ. I will be forever grateful for it. Heard a rumor about some MCLB token or something…

Thank you for the time,

Max Flow O₂

     Post every project I will be writing an apologue or two about the development process and mythology that stems from it. This would be the inaugural one, so let’s dive in to the saga of fBOMB. Obviously being a developer I must start with a requirements and some sort of npm/yarn install right?

{
  "devDependencies": {
    "@TL/CR": "^0.0.1",
    "@requirements": "^1.0.0",
    "@MaxFlowO2": "latest"
  }
} 

     So this saga comes with me as the 3rd gen developer of the first meme coin on Fantom. Yes, we are talking about $BOMB on chainID 250. Obviously there was a needed wrapper so wBOMB came from a developer named lookee. He also did a great UI. But the man, the myth, the legend also named Fiery Dev, aka @Dev_Enjoys on bird app came to me while doing updates with wBOMB. The challenge get BOMB to all the chains. The answer, omnichain. Why me? Answer, TinyDaemons…

     First thing is first you must get the original contracts so you can build localhost and or testnet editions for testing. So copied the verified source from FTMScan found here BOMBv3 and wBOMB. Next challenge was 1822 UUPS ERC20. I didn’t like OZ’s so rolled my own called Lib20 with a struct named Token, aka Lib20.Token. Tied that to EIP-20, and off to the races. Added the Non Blocking Receiver from LZ and made the payload uint256 amount, kind of obvious there.

Now here were the requirements:

• One way deposit BOMB/wBOMB → fBOMB

  • Smart contract handles 100% of burning it all

    • wBOMB can not burn

    • BOMB can burn

• Bridgable

  • LZ enabled via traverseChains(uint256 amount)

• Taxation

  • 1% on all intra-chain transactions

    • Same as wBOMB on Fantom

    • Same as BOMB on Fantom

  • 1% tax to treasury for bridging

  • Exemption for certain v2 AMM’s and Balancers

• Upgradable

  • EIP 1822 UUPS

• Tied to fbomb.finance

     We can fast forward to currently and stop the technical jargon and you can see the deployed contract source here. It is currently on Optimism and Fantom blockchains and will be migrated to five others very soon. Why take my word for it, look here.

     So I’ll post another update this when the UI is done, for for now I must say, “Bon voyage.” This was the birth of the Max-20/2023 UUPS LZ. I will be forever grateful for it. Heard a rumor about some MCLB token or something…

Thank you for the time,

Max Flow O₂