You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Provider Context: Minimal Profile for Provider and Applications (#2549)
# Details
[Design
Doc](https://github.com/frequency-chain/frequency/blob/main/designdocs/provider_contexts.md)
Provider Context allows provider to now register a minimal profile
`ProviderRegistryEntry` and `ApplicationContext` for provider's default
profile and various applications providers want to register.
Providers which want to register multiple applications under single
provider delegation but distributed across multiple app. Following
issues were resolved as part of this work with following salient points:
1. Migration existing `ProviderToRegistryEntry` to host new
`ProviderRegistryEntry` payload
2. Introduce new state `ProviderToApplicationRegistry` and
`ApprovedLogos` storage maps.
3. CID's are computed in deterministic way =
`base(cid_v1(sha_256(logo_bytes)))` where logo_bytes are .png image
bytes.
4. ApprovedLogos ensure it matches CID and logoBytes but recomputing and
checking on chain.
Issues complete as part of `Provider Context` work
- [x] #2523
- [x] #2524
- [x] #2525
- [x] #2528
- [x] #2526
- [x] #2577
- [x] #2578Closes#2578Closes#2577
# Discussion items
- [x] Do we feature flag than base filter out extrinsics @JoeCap08055
comment
[here](#2587 (comment))
# Checklist
- [x] Updated Pallet Readme?
- [x] Updated js/api-augment for Custom RPC APIs?
- [x] Design doc(s) updated?
- [x] Unit Tests added?
- [x] e2e Tests added?
- [x] Benchmarks added?
- [x] Spec version incremented?
---------
Co-authored-by: Joe Caputo <[email protected]>
Co-authored-by: Aramik <[email protected]>
Co-authored-by: Matthew Orris <[email protected]>
2. Lookup the Provider via the `publicKey` in the SIWF Signed Request.
328
328
3. If any, fetch the `ApplicationIndex` from Frequency.
329
-
4. If present, fetch the `ProviderToApplicationRegistryEntry` for that (ProviderId, ApplicationId) pair. Otherwise, fetch the default `ProviderToRegistryEntry` for the ProviderId
329
+
4. If present, fetch the `ProviderToApplicationRegistryEntry` for that (ProviderId, ApplicationId) pair. Otherwise, fetch the default `ProviderToRegistryEntryV2` for the ProviderId
330
330
5. Display the information to the user to help them know who they are authorizing.
0 commit comments