# Resource logics: Connecting nullifiers and consumed resources

**URL:** <https://forum.anoma.net/t/resource-logics-connecting-nullifiers-and-consumed-resources/825>\
**Category:** RM\
**Created:** [October 14, 2024, 10:18am UTC](https://forum.anoma.net/t/resource-logics-connecting-nullifiers-and-consumed-resources/825 "2024-10-14T10:18:13Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![cwgoes](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.anoma.net/cwgoes/32/22_2.png) [@cwgoes](https://forum.anoma.net/u/cwgoes)\
**Post date:** [October 15, 2024, 8:13am UTC](https://forum.anoma.net/t/resource-logics-connecting-nullifiers-and-consumed-resources/825/15 "2024-10-15T08:13:35Z")

</div>

> [@Michael](#):
>
> Alternatively, we could establish an ownership standard and store this in the `value` field so that indexers can index it properly.

I think we should probably do this. I would consider the nullifier key a technical detail that must be dealt with properly for shielded resources, but that we should avoid relying on for any desired properties of applications (such as authorization), indexing, etc.

@xuyang @vveiln What role exactly do nullifier keys play in shielded proofs? Is it just randomness to ensure unlinkability, or is there some additional property being provided?

---

_[View the full topic](https://forum.anoma.net/t/resource-logics-connecting-nullifiers-and-consumed-resources/825)._