# Compiler error: Unable to offset into the data section more than 2^12 bits. Unsupported data section length

**URL:** <https://forum.fuel.network/t/compiler-error-unable-to-offset-into-the-data-section-more-than-2-12-bits-unsupported-data-section-length/4233>\
**Category:** Sway\
**Tags:** testnet, feedback\
**Created:** [February 10, 2024, 3:08pm UTC](https://forum.fuel.network/t/compiler-error-unable-to-offset-into-the-data-section-more-than-2-12-bits-unsupported-data-section-length/4233 "2024-02-10T15:08:33Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![theAusicist](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/theausicist/32/1987_2.png) [@theAusicist](https://forum.fuel.network/u/theAusicist)\
**Post date:** [February 10, 2024, 3:08pm UTC](https://forum.fuel.network/t/compiler-error-unable-to-offset-into-the-data-section-more-than-2-12-bits-unsupported-data-section-length/4233/1 "2024-02-10T15:08:33Z")

</div>

I have a Sway contract that compiles to be of size 824.216 Kb (quite large) with the Beta-4 toolchain. When I transition to Beta-5, I get the following error, and my contract no longer compiles.

```bash
thread 'main' panicked at sway-core/src/asm_lang/allocated_ops.rs:716:23:
Unable to offset into the data section more than 2^12 bits. Unsupported data section length.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

```

Here’s the stack backtrace with `RUST_BACKTRACE=full`:

```bash
thread 'main' panicked at sway-core/src/asm_lang/allocated_ops.rs:716:23:
Unable to offset into the data section more than 2^12 bits. Unsupported data section length.
stack backtrace:
   0: 0x103c6a89c - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h298c9ab285ff3934
   1: 0x103c8ce98 - core::fmt::write::h4e276abdb6d0c2a1
   2: 0x103c66608 - std::io::stdio::_eprint::hacf0f815ff08f81b
   3: 0x103c6a6d8 - <std::time::SystemTimeError as core::fmt::Display>::fmt::ha84dff9814e351ac
   4: 0x103c6bc68 - std::panicking::default_hook::ha6550ffe49b63df1
   5: 0x103c6b9b0 - std::panicking::default_hook::ha6550ffe49b63df1
   6: 0x103c6c090 - std::panicking::rust_panic_with_hook::hddb0e884a202de7c
   7: 0x103c6bf6c - <std::panicking::begin_panic_handler::StaticStrPayload as core::panic::PanicPayload>::take_box::h172fd006fbea5e8c
   8: 0x103c6ad04 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h298c9ab285ff3934
   9: 0x103c6bd2c - _rust_begin_unwind
  10: 0x103d03218 - core::panicking::panic_fmt::h4d5168028d4c43c7
  11: 0x103629778 - <sway_core::asm_lang::allocated_ops::AllocatedOp as core::fmt::Display>::fmt::h864bc9b7d6f7f2e4
  12: 0x103629210 - <sway_core::asm_lang::allocated_ops::AllocatedOp as core::fmt::Display>::fmt::h864bc9b7d6f7f2e4
  13: 0x1035b4424 - <alloc::vec::Vec<sway_core::asm_generation::miden_vm::miden_vm_asm_builder::miden_op::DirectOp> as sway_core::asm_generation::miden_vm::miden_vm_asm_builder::ToMidenBytecode>::to_bytecode::h320b15fe9ce76bd2
  14: 0x1036adb20 - sway_core::asm_to_bytecode::h437eef83a4947f8d
  15: 0x102eab794 - forc_pkg::pkg::compile::h3e0c0b967e403972
  16: 0x102eb17b4 - forc_pkg::pkg::build::h1aa0adc2f9e97f5b
  17: 0x102eadca0 - forc_pkg::pkg::build_with_options::h69fe2ab27f2c724e
  18: 0x102ddc4b0 - forc::ops::forc_build::build::he8ef4f0d8e0eea1b
  19: 0x102dc4d1c - forc::cli::commands::build::exec::haaeb09a273b59986
  20: 0x102d40e84 - __mh_execute_header
  21: 0x102d4fb14 - __mh_execute_header
  22: 0x102d54aa4 - __mh_execute_header
  23: 0x102d4fc5c - __mh_execute_header
  24: 0x102d53fa0 - __mh_execute_header
  25: 0x103c5e614 - std::rt::lang_start_internal::h5b246d44f1526226
  26: 0x102d53f84 - __mh_execute_header
  27: 0x102d54b90 - _main

```

Is this a bug, or has the contract code size been reduced from the [~16.7 mb limit](https://forum.fuel.network/t/compiled-contracts-are-large/3946)?

---

<div class="post-metadata">

**Author:** ![theAusicist](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/theausicist/32/1987_2.png) [@theAusicist](https://forum.fuel.network/u/theAusicist)\
**Post date:** [February 12, 2024, 4:46am UTC](https://forum.fuel.network/t/compiler-error-unable-to-offset-into-the-data-section-more-than-2-12-bits-unsupported-data-section-length/4233/2 "2024-02-12T04:46:25Z")

</div>

bumping this to see if you guys could help with this @bitzoic @david!

---

<div class="post-metadata">

**Author:** ![IGI-111](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/igi-111/32/1348_2.png) [@IGI-111](https://forum.fuel.network/u/IGI-111)\
**Post date:** [February 12, 2024, 10:23am UTC](https://forum.fuel.network/t/compiler-error-unable-to-offset-into-the-data-section-more-than-2-12-bits-unsupported-data-section-length/4233/3 "2024-02-12T10:23:42Z")

</div>

Can you provide your build command and/or the source?  
Are you sure you have optimizations turned on?

---

<div class="post-metadata">

**Author:** ![theAusicist](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/theausicist/32/1987_2.png) [@theAusicist](https://forum.fuel.network/u/theAusicist)\
**Post date:** [February 12, 2024, 10:25am UTC](https://forum.fuel.network/t/compiler-error-unable-to-offset-into-the-data-section-more-than-2-12-bits-unsupported-data-section-length/4233/4 "2024-02-12T10:25:52Z")

</div>

it’s just `forc build`. No optimizations turned on

---

<div class="post-metadata">

**Author:** ![IGI-111](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/igi-111/32/1348_2.png) [@IGI-111](https://forum.fuel.network/u/IGI-111)\
**Post date:** [February 12, 2024, 10:30am UTC](https://forum.fuel.network/t/compiler-error-unable-to-offset-into-the-data-section-more-than-2-12-bits-unsupported-data-section-length/4233/5 "2024-02-12T10:30:00Z")

</div>

Do you still get the same issue if you compile with `--release`?  
`beta-5` is a lot less aggressive in the debug profile (to help debuggers) so if you have a huge contract you will benefit from turning optimizations on.

---

<div class="post-metadata">

**Author:** ![theAusicist](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/theausicist/32/1987_2.png) [@theAusicist](https://forum.fuel.network/u/theAusicist)\
**Post date:** [February 12, 2024, 5:47pm UTC](https://forum.fuel.network/t/compiler-error-unable-to-offset-into-the-data-section-more-than-2-12-bits-unsupported-data-section-length/4233/6 "2024-02-12T17:47:22Z")

</div>

nope, it’s still an issue unfortunately. Here’s the full backtrace if it helps

```bash
thread 'main' panicked at sway-core/src/asm_lang/allocated_ops.rs:716:23:
Unable to offset into the data section more than 2^12 bits. Unsupported data section length.
stack backtrace:
   0: 0x10596289c - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h298c9ab285ff3934
   1: 0x105984e98 - core::fmt::write::h4e276abdb6d0c2a1
   2: 0x10595e608 - std::io::stdio::_eprint::hacf0f815ff08f81b
   3: 0x1059626d8 - <std::time::SystemTimeError as core::fmt::Display>::fmt::ha84dff9814e351ac
   4: 0x105963c68 - std::panicking::default_hook::ha6550ffe49b63df1
   5: 0x1059639b0 - std::panicking::default_hook::ha6550ffe49b63df1
   6: 0x105964090 - std::panicking::rust_panic_with_hook::hddb0e884a202de7c
   7: 0x105963f6c - <std::panicking::begin_panic_handler::StaticStrPayload as core::panic::PanicPayload>::take_box::h172fd006fbea5e8c
   8: 0x105962d04 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h298c9ab285ff3934
   9: 0x105963d2c - _rust_begin_unwind
  10: 0x1059fb218 - core::panicking::panic_fmt::h4d5168028d4c43c7
  11: 0x105321778 - <sway_core::asm_lang::allocated_ops::AllocatedOp as core::fmt::Display>::fmt::h864bc9b7d6f7f2e4
  12: 0x105321210 - <sway_core::asm_lang::allocated_ops::AllocatedOp as core::fmt::Display>::fmt::h864bc9b7d6f7f2e4
  13: 0x1052ac424 - <alloc::vec::Vec<sway_core::asm_generation::miden_vm::miden_vm_asm_builder::miden_op::DirectOp> as sway_core::asm_generation::miden_vm::miden_vm_asm_builder::ToMidenBytecode>::to_bytecode::h320b15fe9ce76bd2
  14: 0x1053a5b20 - sway_core::asm_to_bytecode::h437eef83a4947f8d
  15: 0x104ba3794 - forc_pkg::pkg::compile::h3e0c0b967e403972
  16: 0x104ba97b4 - forc_pkg::pkg::build::h1aa0adc2f9e97f5b
  17: 0x104ba5ca0 - forc_pkg::pkg::build_with_options::h69fe2ab27f2c724e
  18: 0x104ad44b0 - forc::ops::forc_build::build::he8ef4f0d8e0eea1b
  19: 0x104abcd1c - forc::cli::commands::build::exec::haaeb09a273b59986
  20: 0x104a38e84 - __mh_execute_header
  21: 0x104a47b14 - __mh_execute_header
  22: 0x104a4caa4 - __mh_execute_header
  23: 0x104a47c5c - __mh_execute_header
  24: 0x104a4bfa0 - __mh_execute_header
  25: 0x105956614 - std::rt::lang_start_internal::h5b246d44f1526226
  26: 0x104a4bf84 - __mh_execute_header
  27: 0x104a4cb90 - _main

```

---

<div class="post-metadata">

**Author:** ![IGI-111](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/igi-111/32/1348_2.png) [@IGI-111](https://forum.fuel.network/u/IGI-111)\
**Post date:** [February 12, 2024, 6:11pm UTC](https://forum.fuel.network/t/compiler-error-unable-to-offset-into-the-data-section-more-than-2-12-bits-unsupported-data-section-length/4233/7 "2024-02-12T18:11:11Z")

</div>

It looks like you’re compiling for MidenVM but the thread you link in the OP is talking about the FuelVM specs. Which one are you actually targetting here?

There’s not much I can really do with just this stack trace and no source. Maybe if you could identify the exact version of Sway that introduces the problem, that might help narrow it down?

---

<div class="post-metadata">

**Author:** ![theAusicist](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/theausicist/32/1987_2.png) [@theAusicist](https://forum.fuel.network/u/theAusicist)\
**Post date:** [February 12, 2024, 6:25pm UTC](https://forum.fuel.network/t/compiler-error-unable-to-offset-into-the-data-section-more-than-2-12-bits-unsupported-data-section-length/4233/8 "2024-02-12T18:25:05Z")

</div>

right, not sure what MidenVM is, but here’s what I get with `fuelup show`. Targetting Beta-5 for Fuel. Quite literally using the default command: `forc build` (`forc build --release` yields the same results)

```bash

installed toolchains
--------------------
beta-4-aarch64-apple-darwin (default)
beta-5-aarch64-apple-darwin

active toolchain
----------------
beta-4-aarch64-apple-darwin (default)
  forc : 0.46.1
    - forc-client
      - forc-deploy : 0.46.1
      - forc-run : 0.46.1
    - forc-crypto : not found
    - forc-doc : 0.46.1
    - forc-explore : 0.28.1
    - forc-fmt : 0.46.1
    - forc-lsp : 0.46.1
    - forc-tx : 0.46.1
    - forc-wallet : 0.3.0
  fuel-core : 0.20.5
  fuel-core-keygen : Error getting version string

fuels versions
--------------
forc : 0.45
forc-wallet : 0.45

```

---

<div class="post-metadata">

**Author:** ![IGI-111](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/igi-111/32/1348_2.png) [@IGI-111](https://forum.fuel.network/u/IGI-111)\
**Post date:** [February 12, 2024, 7:41pm UTC](https://forum.fuel.network/t/compiler-error-unable-to-offset-into-the-data-section-more-than-2-12-bits-unsupported-data-section-length/4233/9 "2024-02-12T19:41:33Z")

</div>

Okay there’s a bunch of problems here: you have beta-4 selected, not beta-5.

And the backtrace you gave contains this:

```auto
13: 0x1035b4424 - <alloc::vec::Vec<sway_core::asm_generation::miden_vm::miden_vm_asm_builder::miden_op::DirectOp> as sway_core::asm_generation::miden_vm::miden_vm_asm_builder::ToMidenBytecode>::to_bytecode::h320b15fe9ce76bd2

```

Which means that you must, somehow, have the `midenvm` target selected instead of the `fuel` default one.  
What happens if you force it with `--build-target fuel`? What happens if you compile with the `beta-5-aarch64-apple-darwin` toolchain?  
What does your `Forc.toml` look like?

---

<div class="post-metadata">

**Author:** ![theAusicist](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/theausicist/32/1987_2.png) [@theAusicist](https://forum.fuel.network/u/theAusicist)\
**Post date:** [February 13, 2024, 3:55am UTC](https://forum.fuel.network/t/compiler-error-unable-to-offset-into-the-data-section-more-than-2-12-bits-unsupported-data-section-length/4233/10 "2024-02-13T03:55:03Z")

</div>

you are right, I sent you the Beta-4 toolchain `fuelup show` output as I’ve been using that as an alternative.

I get the same error with `forc build --build-target fuel` and `forc build --release --build-target fuel` (it somehow appears that midenvm target is being selected regardless even with no input from my side)

```bash
thread 'main' panicked at sway-core/src/asm_lang/allocated_ops.rs:716:23:
Unable to offset into the data section more than 2^12 bits. Unsupported data section length.
stack backtrace:
   0: 0x1031e289c - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h298c9ab285ff3934
   1: 0x103204e98 - core::fmt::write::h4e276abdb6d0c2a1
   2: 0x1031de608 - std::io::stdio::_eprint::hacf0f815ff08f81b
   3: 0x1031e26d8 - <std::time::SystemTimeError as core::fmt::Display>::fmt::ha84dff9814e351ac
   4: 0x1031e3c68 - std::panicking::default_hook::ha6550ffe49b63df1
   5: 0x1031e39b0 - std::panicking::default_hook::ha6550ffe49b63df1
   6: 0x1031e4090 - std::panicking::rust_panic_with_hook::hddb0e884a202de7c
   7: 0x1031e3f6c - <std::panicking::begin_panic_handler::StaticStrPayload as core::panic::PanicPayload>::take_box::h172fd006fbea5e8c
   8: 0x1031e2d04 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h298c9ab285ff3934
   9: 0x1031e3d2c - _rust_begin_unwind
  10: 0x10327b218 - core::panicking::panic_fmt::h4d5168028d4c43c7
  11: 0x102ba1778 - <sway_core::asm_lang::allocated_ops::AllocatedOp as core::fmt::Display>::fmt::h864bc9b7d6f7f2e4
  12: 0x102ba1210 - <sway_core::asm_lang::allocated_ops::AllocatedOp as core::fmt::Display>::fmt::h864bc9b7d6f7f2e4
  13: 0x102b2c424 - <alloc::vec::Vec<sway_core::asm_generation::miden_vm::miden_vm_asm_builder::miden_op::DirectOp> as sway_core::asm_generation::miden_vm::miden_vm_asm_builder::ToMidenBytecode>::to_bytecode::h320b15fe9ce76bd2
  14: 0x102c25b20 - sway_core::asm_to_bytecode::h437eef83a4947f8d
  15: 0x102423794 - forc_pkg::pkg::compile::h3e0c0b967e403972
  16: 0x1024297b4 - forc_pkg::pkg::build::h1aa0adc2f9e97f5b
  17: 0x102425ca0 - forc_pkg::pkg::build_with_options::h69fe2ab27f2c724e
  18: 0x1023544b0 - forc::ops::forc_build::build::he8ef4f0d8e0eea1b
  19: 0x10233cd1c - forc::cli::commands::build::exec::haaeb09a273b59986
  20: 0x1022b8e84 - __mh_execute_header
  21: 0x1022c7b14 - __mh_execute_header
  22: 0x1022ccaa4 - __mh_execute_header
  23: 0x1022c7c5c - __mh_execute_header
  24: 0x1022cbfa0 - __mh_execute_header
  25: 0x1031d6614 - std::rt::lang_start_internal::h5b246d44f1526226
  26: 0x1022cbf84 - __mh_execute_header
  27: 0x1022ccb90 - _main

```

Here’s my `fuelup show` with Beta-5 selected:

```bash

installed toolchains
--------------------
beta-4-aarch64-apple-darwin
beta-5-aarch64-apple-darwin (default)

active toolchain
----------------
beta-5-aarch64-apple-darwin (default)
  forc : 0.49.1
    - forc-client
      - forc-deploy : 0.49.1
      - forc-run : 0.49.1
    - forc-crypto : 0.49.1
    - forc-doc : 0.49.1
    - forc-explore : 0.28.1
    - forc-fmt : 0.49.1
    - forc-lsp : 0.49.1
    - forc-tx : 0.49.1
    - forc-wallet : 0.4.2
  fuel-core : 0.22.0
  fuel-core-keygen : 0.22.0

fuels versions
--------------
forc : 0.54.0
forc-wallet : 0.54.0

```

Base `Forc.toml`:

```toml
[workspace]
members = [
    # "contracts/pricefeed",
    "contracts/core/vault",
    # "contracts/core/router",
]

```

and the `Forc.toml` for each of the members before:

```toml
[project]
authors = ["me and you"]
entry = "main.sw"
license = "Apache-2.0"
name = "vault"

[dependencies]
helpers = { path = "../../helpers" }
core_interfaces = { path = "../interfaces" }
interfaces = { path = "../../interfaces" }

```

`helpers`, `core_interfaces`, and `interfaces` are just folders with abis/helper methods (all library files).

---

<div class="post-metadata">

**Author:** ![IGI-111](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/igi-111/32/1348_2.png) [@IGI-111](https://forum.fuel.network/u/IGI-111)\
**Post date:** [February 13, 2024, 4:26am UTC](https://forum.fuel.network/t/compiler-error-unable-to-offset-into-the-data-section-more-than-2-12-bits-unsupported-data-section-length/4233/11 "2024-02-13T04:26:28Z")

</div>

This is all very odd.  
beta-5 is supposed to use forc version 0.50.0.  
I know neither how you got an older version nor why it seems to want to compile for the wrong target.

I must say, I’ve never encountered anything quite like this. I think you may want to delete the whole toolchain and reinstall a clean one because evidently something is going very wrong here.

---

<div class="post-metadata">

**Author:** ![theAusicist](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/theausicist/32/1987_2.png) [@theAusicist](https://forum.fuel.network/u/theAusicist)\
**Post date:** [February 13, 2024, 4:32am UTC](https://forum.fuel.network/t/compiler-error-unable-to-offset-into-the-data-section-more-than-2-12-bits-unsupported-data-section-length/4233/12 "2024-02-13T04:32:09Z")

</div>

agreed. attempting to re-install the toolchain again. Download from Github is painfully slow, but will let you know if the build succeeds

---

<div class="post-metadata">

**Author:** ![theAusicist](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/theausicist/32/1987_2.png) [@theAusicist](https://forum.fuel.network/u/theAusicist)\
**Post date:** [February 13, 2024, 7:14am UTC](https://forum.fuel.network/t/compiler-error-unable-to-offset-into-the-data-section-more-than-2-12-bits-unsupported-data-section-length/4233/13 "2024-02-13T07:14:06Z")

</div>

i’ve reinstalled the toolchain (including `fuelup`) and it’s still an issue. When I try to use `fuelup toolchain install latest` and `fuelup toolchain install beta-5`, they are both installing forc version 0.49.1 which I understand is the buggy version. Any idea how I can force download `v0.50.0`?

---

<div class="post-metadata">

**Author:** ![IGI-111](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/igi-111/32/1348_2.png) [@IGI-111](https://forum.fuel.network/u/IGI-111)\
**Post date:** [February 13, 2024, 11:00am UTC](https://forum.fuel.network/t/compiler-error-unable-to-offset-into-the-data-section-more-than-2-12-bits-unsupported-data-section-length/4233/14 "2024-02-13T11:00:07Z")

</div>

Have you run `fuelup update` and/or `fuelup self update`?

---

<div class="post-metadata">

**Author:** ![theAusicist](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/theausicist/32/1987_2.png) [@theAusicist](https://forum.fuel.network/u/theAusicist)\
**Post date:** [February 13, 2024, 3:20pm UTC](https://forum.fuel.network/t/compiler-error-unable-to-offset-into-the-data-section-more-than-2-12-bits-unsupported-data-section-length/4233/15 "2024-02-13T15:20:13Z")

</div>

yes, no luck. I’ll keep using Beta-4 in the meantime as late as I can, or till I’m able to use the latest version of forc (\>=v0.50.0). Thanks for your help.

---

<div class="post-metadata">

**Author:** ![theAusicist](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/theausicist/32/1987_2.png) [@theAusicist](https://forum.fuel.network/u/theAusicist)\
**Post date:** [February 20, 2024, 4:45am UTC](https://forum.fuel.network/t/compiler-error-unable-to-offset-into-the-data-section-more-than-2-12-bits-unsupported-data-section-length/4233/16 "2024-02-20T04:45:06Z")

</div>

Alright, somehow I’m able to compile now both with Beta-5 and `latest` toolchain, BUT I’m not able to deploy said contracts with either the generated types (AbiFactory, and AbiHex), or the [`ContractFactory` method](https://docs.fuel.network/docs/fuels-ts/contracts/deploying-contracts/). This is the error I get: `FuelError: Invalid u16, too many bytes.`

The traceback:

```bash
     FuelError: Invalid u16, too many bytes.
      at NumberCoder.encode (node_modules/@fuel-ts/abi-coder/src/coders/number.ts:55:13)
      at TransactionCreateCoder.encode (node_modules/@fuel-ts/transactions/src/coders/transaction.ts:206:39)
      at TransactionCoder.encode (node_modules/@fuel-ts/transactions/src/coders/transaction.ts:372:40)
      at CreateTransactionRequest.toTransactionBytes (node_modules/@fuel-ts/providers/src/transaction-request/transaction-request.ts:189:35)
      at CreateTransactionRequest.byteSize (node_modules/@fuel-ts/providers/src/transaction-request/transaction-request.ts:518:17)
      at CreateTransactionRequest.calculateMinGas (node_modules/@fuel-ts/providers/src/transaction-request/transaction-request.ts:538:25)
      at _Provider.getTransactionCost (node_modules/@fuel-ts/providers/src/provider.ts:810:39)
      at ContractFactory.deployContract (node_modules/@fuel-ts/contract/src/contract-factory.ts:149:35)
      at /Users/sluzhba/Documents/Dev/Burra Labs/ruscet-contracts/tests/core/Tester.test.ts:87:22
      at step (tests/core/Tester.test.ts:33:23)

```

My guess is that there’s something in my contract that is causing this error, but can’t debug effectively because this contract file is ~2500 lines of code; but it appears that the error (`too many bytes` is loosely related to `unable to offest [...] more than 2^12 bits`. Maybe the contract is too big?

I’m using `fuels` v0.73.0 (fails with v0.74.0 too)