we can’t sign for the new F1 address

[TOPPOOL-LEE]

TOPPOOL-LEE/Allocator-Pathway-TOP-POOL#104 meet some problems. I have signed 256TiB. the amount of the f1 address is 0. Unable to query on the chain. Clients can'ot use.

The bot on LDN shows that 75% of the 256T has been used.

https://allocator.tech/ shows that 256T has not been used yet

[TOPPOOL-LEE]

The client can't use the DC with f1 address

[TOPPOOL-LEE]

TOPPOOL-LEE/Allocator-Pathway-TOP-POOL#110

The client give the f1 address from lotus and has recharged the fil , but can‘t sign

[TOPPOOL-LEE]

TOPPOOL-LEE/Allocator-Pathway-TOP-POOL#108

The client give the f1 address from imtoken, but can‘t sign

Then changed it to lotus f1, can't sign.

[TOPPOOL-LEE]

TOPPOOL-LEE/Allocator-Pathway-TOP-POOL#104

The client give the f1 address from imtoken, after recharging fil, the signature is successful, but DC can‘t be used: the chain can't be verified

[TOPPOOL-LEE]

Then, we tested it for an old ldn and successfully signed 1TiB.
TOPPOOL-LEE/Allocator-Pathway-TOP-POOL#91

[TOPPOOL-LEE]

So, we can’t sign for the new F1 address, but we can sign for the old F1 address.
Requesting help from the governance team, thanks @willscott @kacperzuk-neti @Filip-L @kevzak

[TOPPOOL-LEE]

[TOPPOOL-LEE]

There may be a problem with the ledger. request the governance team for help.

[TOPPOOL-LEE]

TOPPOOL-LEE/Allocator-Pathway-TOP-POOL#114

[TOPPOOL-LEE]

After testing, the f3 address unable to signed

[TOPPOOL-LEE]

The address can't be recognized for new applications