Currently the TACo app authorization shown on tacoscan is obteined through mainnet-staking-subgraph, that get the authorization amounts from the staking contract.
Due to changes on threshold-network/solidity-contracts#171, this amount is not correctly calculated by the subgraph: the authorization amount shown for beta stakers is 0 if you ask the staking contract. For example, for this beta staker:
https://tacoscan.com/?staker=0x331f6346c4c1bdb4ef7467056c66250f0eb8a44f
Total authorized is 0 in tacoscan. But this is not true.
A new subgraph listening for authorization events on TACoApplication contract would work better.
Another option could be calling the function authorizedStake(address) on TACoApplication contract or TACoChildApplication (the latter updates faster).
Currently the TACo app authorization shown on tacoscan is obteined through mainnet-staking-subgraph, that get the authorization amounts from the staking contract.
Due to changes on threshold-network/solidity-contracts#171, this amount is not correctly calculated by the subgraph: the authorization amount shown for beta stakers is 0 if you ask the staking contract. For example, for this beta staker:
https://tacoscan.com/?staker=0x331f6346c4c1bdb4ef7467056c66250f0eb8a44f
Total authorized is 0 in tacoscan. But this is not true.
A new subgraph listening for authorization events on TACoApplication contract would work better.
Another option could be calling the function
authorizedStake(address)on TACoApplication contract or TACoChildApplication (the latter updates faster).