Ahmed Sagdati

> Would you mind sharing more details about your current use-case? Depending on your use-case, you might be better off using `forc-pkg` directly I'm creating a repo that will contain...

@mitchmindtree @bingcicle Although this might go without saying, we'll just recap what @hal3e and I noticed while perusing the forc project: The problem occurs when multiple projects share a sway...

An update: Wrote a small [utility](https://github.com/segfault-magnet/regenesis_storage_bench) to benchmark our use case. Our expected data volume is enormous -- a 1TB rocksdb database at the moment of regenesis. Benchmarking for this...

Tried one more format, [Parquet](https://parquet.apache.org/). Even though we don't benefit from the columnar layout parquet has the advantage of encoding data in chunks (solving the cursor + encoding problem). It...

Waiting to see how far away encoding support is in sway.

Waiting for https://github.com/FuelLabs/fuels-rs/pull/1249 to land so that we have some place to put the config needed.

Maybe to make it into a draft until things are ready? @digorithm @iqdecay

@MujkicA this doesn't seem ready for merging. Can we convert this to a draft until the updates in core are propagated?

In order to know the original type of some logged data, we need the log->type mapping from the JSON ABI of the contract which logged it. So if you call...

@SilentCicero "found more than one `fuel-core`" doesn't cause an error. It is a warning message (should probably be moved to a log instead of being in `stderr`) introduced after we...