Howard Wu

We discussed the idea to use public credits for the fee. There are several tradeoffs that are made in doing this. For one, using public credits means we will need...

I think it can be closed for now. I'll add one more comment for all readers: There needs to be much better UI/UX-based web or client based services to help...

Reopening this issue as we may have come up with a way to support public fees without sacrificing concurrency (because of the `nonce`), and without introducing replay attack concerns.

The MVP for this feature has been implemented in #1867. There remains much more work needed to do to ensure safety and stability of this feature.

Closing since we now support public fees.

@zosorock As an update, we have merged the GPU PR. Let us know if we can get CI updated with GPU testing.

Closing as the feature freeze has taken place for mainnet. Future discussions can be raised as ARCs going forward.

The TLDR is we are going to hold off on this until boolean arrays are supported in Aleo instructions. ## Problem The reason this fails is that `1i64.to_bits_le()` becomes `[...

We haven't drafted anything yet. Currently, we've been experimenting with using routing networks to facilitate the common memory-bound array operations.

Also a good question, we're planning to overhaul the `StringType`. Currently, yes the `StringType` is fixed. Once we have array support, it will allow us to support an updatable `StringType`...