John Adler

This change would avoid having to offset the value by 1 to use allocated memory, right?

Ref: https://github.com/FuelLabs/fuel-types/pull/40

I think we can make this even simpler: just make entries in the address registry expire after `N` blocks. Boom, state growth capped (and it's append-only state, the best kind...

In practice, most of these fields won't exceed the limit of a `u32` even if their _type_ is `u64`. There will be consensus rules placing an upper bound on each...

Good idea!

Suggestion: either 8 or 32 bytes.

Note that Solidity uses a 4-byte selector for "custom errors" and I think structs that are logged. We could do that, or have simple numeric IDs.

If this requires an org-wide change then it should have org-wide buy-in. Might be time to follow-up on https://github.com/FuelLabs/rfcs/pull/8

> Given that many other chains have prefixes for different types of addresses, it seems that this should be achievable. For example Bitcoin: > You can tell the difference between...

> do we weaken any security guarantees by doing this Yes, we lose 1 bit of security. So, reducing from 256 to 255. > a chance that more than one...