# Any suggestions what values to be used here? **URL:** \ **Category:** TypeScript SDK\ **Created:** [May 10, 2024, 11:48am UTC](https://forum.fuel.network/t/any-suggestions-what-values-to-be-used-here/5268 "2024-05-10T11:48:02Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Author:** ![p.s](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/p.s/32/2491_2.png) [@p.s](https://forum.fuel.network/u/p.s)\ **Post date:** [May 10, 2024, 1:36pm UTC](https://forum.fuel.network/t/any-suggestions-what-values-to-be-used-here/5268/10 "2024-05-10T13:36:48Z")
You may find the [nightly docs](https://docs.fuel.network/docs/nightly/sway/blockchain-development/native_assets/#the-subid-type) more helpful. If you could share a link to your repository, I _may_ be able to assist further 🙂 * * * Just found the following post you might find useful! > [@Ownership of native assets](https://forum.fuel.network/t/ownership-of-native-assets/3106/5): > > It’s up to the developer! If the contract only creates a single token, we expect the SubId will often be 0 For NFTs, the SubIds might be sequential In the case of “vault” type tokens, the subId might be the AssetId of the underlying asset ENS-style naming applications might use a namehash-type algorithm You can even use asset sub-ids to represent contract state! Pass some state into the asset subId, and you can then reconstruct the assetId in a separate contract or predicate to prove state (I… --- _[View the full topic](https://forum.fuel.network/t/any-suggestions-what-values-to-be-used-here/5268)._