Access rules can include implicit requirements referencing special system-reserved resource addresses, which have specific meanings for the Radix Engine and are not part of the standard authorization zone system. These implicit requirements typically store their details as a hash, which means the subject of the requirement can't be easily resolved. This is where this endpoint comes in. It can resolve the subject of the implicit requirements, using a database of reverse hash lookups populated from ledger data.
The following resource addresses are supported:
When querying, you must provide a pair of the following for each requirement to resolve:
resource_address (one of the above)non_fungible_id, of the requirement.You can query a maximum of 100 implicit requirements at a time.
See the documentation on implicit-requirements for more information.
{"requirements":[{"resource_address":"<sample-implicit-requirement-resource-address>","non_fungible_id":"<sample-implicit-requirement-non-fungible-id>"}]}