When using publish BNS, we need to recurse certain client types that are actually contracts:
1) Diode app identity contracts
These contracts contain sometimes many end client devices - if an address to an identity contract is included in the BNS address list, publish BNS should read the client IDs in the identity contract and also add those to allow list
e.g. 0xd4f6e95cd56db9eb6ffe5ddd65c6031364a364d6 contains client ID 0xd28671694fab1f55e0b83a519adfb70053c0018f
2) Fleet contracts
These contracts contain arbitrary additional lists of devices that can be used in their own right as protected perimeters. We should parse these and get the client IDs associated.
e.g. https://diode.io/prenet/#/address/0x5a628aad89fcd9f926270c52ea3d741e26764498 contains client IDs 0xb6a70432a8bbbcb9ce019c9a9c82fd0f651be121 and 0x70114a27f3d1b549012498c69a4120ca4ea11e21
3) The mother of all: Zone contracts
These will mostly contain Diode app identity contracts.
e.g. 0xc1f4190c757b781acc01cee55de40b289e4c0dd9 contains identity 0xd4f6e95cd56db9eb6ffe5ddd65c6031364a364d6
tuhalf
commented
2 months ago
When using publish BNS, we need to recurse certain client types that are actually contracts:
1) Diode app identity contracts These contracts contain sometimes many end client devices - if an address to an identity contract is included in the BNS address list, publish BNS should read the client IDs in the identity contract and also add those to allow list e.g. 0xd4f6e95cd56db9eb6ffe5ddd65c6031364a364d6 contains client ID 0xd28671694fab1f55e0b83a519adfb70053c0018f
2) Fleet contracts These contracts contain arbitrary additional lists of devices that can be used in their own right as protected perimeters. We should parse these and get the client IDs associated. e.g. https://diode.io/prenet/#/address/0x5a628aad89fcd9f926270c52ea3d741e26764498 contains client IDs 0xb6a70432a8bbbcb9ce019c9a9c82fd0f651be121 and 0x70114a27f3d1b549012498c69a4120ca4ea11e21
3) The mother of all: Zone contracts These will mostly contain Diode app identity contracts.
e.g. 0xc1f4190c757b781acc01cee55de40b289e4c0dd9 contains identity 0xd4f6e95cd56db9eb6ffe5ddd65c6031364a364d6