[BUG] Correct hosted Factory Manager & Filter implementations on Testnet

Question

[BUG] Correct hosted Factory Manager & Filter implementations on Testnet

sisyphusSmiling opened this issue a year ago · 0 comments

Current Behavior

Currently, the AllowAllFilter at 0x30c672282cfa3adf is an implementation of a former deployment of CapabilityFilter.

Additionally, the NFT+FT Factory Manager at 0x4b69a89e2b97c93a contains Managers of current and former versions of CapabilityFactory, which can be confusing for devs looking to these accounts as development models.

Also, both the NFT+FT and FT Managers are lacking the new FTReceiverBalanceFactory (#152)

Expected Behavior

The AllowAllFilter should be an implementation of CapabilityFilter at 0x294e44e1ec6993c6.

The NFT+FT Factory Manager should only contain the current Manager implementation - the one currently stored at the path /storage/CapabilityFactory_0x294e44e1ec6993c6

Lastly, the NFT+FT and the FT Managers should have the new FTReceiverBalance.Factory added.

Steps To Reproduce

Look at the AllowAllFilter host account and the NFT+FT Factory Manager host account and compare against the current Testnet deployment.

Next Steps

All of the following are steps on Testnet:

Replace the AllowAllFilter at 0x30c672282cfa3adf with a current version
Remove the Manager at /storage/CapabilityFactory0x96b15ff6dfde11fe in account 0x4b69a89e2b97c93a
Add FTReceiverBalanceFactory.Factory to NFT+FT (at 0x5617ff347e16bd72) and FT Managers (at 0x4b69a89e2b97c93a)
e.g. manager.updateFactory(Type<&{FungibleToken.Receiver, FungibleToken.Balance}>(), FTReceiverBalanceFactory.Factory())