# Standard interface detection

**URL:** <https://forum.fuel.network/t/standard-interface-detection/188>\
**Category:** Sway RFCs\
**Created:** [December 12, 2022, 11:08pm UTC](https://forum.fuel.network/t/standard-interface-detection/188 "2022-12-12T23:08:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![david](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/david/32/32_2.png) [@david](https://forum.fuel.network/u/david)\
**Post date:** [December 12, 2022, 11:08pm UTC](https://forum.fuel.network/t/standard-interface-detection/188/1 "2022-12-12T23:08:08Z")

</div>

A meta-standard should exist for introspection into which contracts provide access to which interfaces.

References from the EVM world:

- [EIP-165: Standard Interface Detection](https://eips.ethereum.org/EIPS/eip-165)
- [ReverseENS Pseudo-Introspection, or standard interface detection · Issue #672 · ethereum/EIPs · GitHub](https://github.com/ethereum/EIPs/issues/672)
- [EIP-1820: Pseudo-introspection Registry Contract](https://eips.ethereum.org/EIPS/eip-1820)

---

<div class="post-metadata">

**Author:** ![furnic](https://avatars.discourse-cdn.com/v4/letter/f/97f17d/32.png) [@furnic](https://forum.fuel.network/u/furnic)\
**Post date:** [December 14, 2022, 1:50pm UTC](https://forum.fuel.network/t/standard-interface-detection/188/2 "2022-12-14T13:50:49Z")

</div>

Hey @david, here’s an open issue where we are currently discussing this topic: [Consider appending data to a contract's bytecode which decribes which `abi`s the contract implements. · Issue #3234 · FuelLabs/sway · GitHub](https://github.com/FuelLabs/sway/issues/3234)

Of course, we could simply adopt a standard from ethereum (ERC-1820 is the most flexible in my opinion), but any standard in this area will need to factor features available to us in Sway and the FuelVM.