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
On startup, the sentinel logs a list of SuperTokens.
First, there's an info log of all SuperTokens it's aware of (?), followed by a debug log of the same with 3Ps info attached.
This list seems to not be in sync with the list of tokens configured for the sentinel.
There's currently 3 ways to affect the list of tokens taken into consideration (lets call it "watched SuperTokens") by a sentinel instance:
If none of those are set - which is the default - all SuperToken are in the set of watched SuperTokens.
2 issues to be investigated:
Currently, the report outputs a set of SuperTokens which doesn't reflect the set of watched SuperTokens.
It doesn't reflect the set of all SuperTokens either. E.g. on some instances running for Polygon I see the SuperToken EURSx (0x02ef6868d69707b6093a2962bb5fe5661fcc0deb) missing, despite it not being included, despite it being a listed token. (may be related to the handling of the listed flag in previous sentinel versions)(this is likely a snapshot creation issue, to be dealt with separately) it's because no CFA event happened yet, keeping the token invisible for the sentinel
Goal:
going forward, the report item protocol.supertokens should reflect the current list of watched SuperTokens, such that sentinel operators can easily verify it's reflecting the intended configuration.
The text was updated successfully, but these errors were encountered:
On startup, the sentinel logs a list of SuperTokens.
First, there's an info log of all SuperTokens it's aware of (?), followed by a debug log of the same with 3Ps info attached.
This list seems to not be in sync with the list of tokens configured for the sentinel.
There's currently 3 ways to affect the list of tokens taken into consideration (lets call it "watched SuperTokens") by a sentinel instance:
If none of those are set - which is the default - all SuperToken are in the set of watched SuperTokens.
2 issues to be investigated:
It doesn't reflect the set of all SuperTokens either. E.g. on some instances running for Polygon I see the SuperToken EURSx (0x02ef6868d69707b6093a2962bb5fe5661fcc0deb) missing, despite it not being included, despite it being a listed token. (may be related to the handling of the listed flag in previous sentinel versions)(this is likely a snapshot creation issue, to be dealt with separately)it's because no CFA event happened yet, keeping the token invisible for the sentinelGoal:
going forward, the report item
protocol.supertokens
should reflect the current list of watched SuperTokens, such that sentinel operators can easily verify it's reflecting the intended configuration.The text was updated successfully, but these errors were encountered: