Specific Filter whitelist application

Description of the issue:
Crust Apps (a Dapp of Crust Network, you can check this: https://apps.crust.network) basically provides decentralized IPFS Pin services.
But when we used Brave to explore Crust Apps, we found that Brave Shield would intercept the connection request of 127.0.0.1 from our Apps, and users need to manually close Brave Shield for normal use.
we hope Brave could add ‘apps.crust.network’ to the white-list.

Steps to Reproduce (add as many as necessary):
Go to: https://apps.crust.network/#/storage/files, the page will failed to connect to local IPFS API, due to the Specific Filter config.

Actual Result (gifs and screenshots are welcome!):
The IPFS connection from apps.crust.network has been blocked.

Expected result:
We expect to connect to IPFS API directly through Brave Explorer (with out brave shields up)

Reproduces how often:
Each time accessing apps.crust.network via Brave Browser
Operating System and Brave Version(See the About Brave page in the main menu):
All the OS and Brave versions.

Additional Information:
Crust is a Web3 Foundation Grant Project, which provides a decentralized cloud for Web 3.0 ecosystem.
Currently, Crust is running a preview network “Maxwell” and has got 1000+ nodes joined in to provide IPFS storage (https://telemetry.polkadot.io/#list/Crust%20Maxwell). Besides, Crust is open source (https://github.com/crustio/crust). We would appreciate it very much if you could approve our application.

Can you paste the blocked url requests from shields? (advanced view)

This link http://127.0.0.1:5001/api/v0/stats/bw

If you add the following into brave://adblock, does it help? @yyd106

@@||127.0.0.1^$domain=crust.network

Yes, add @@||127.0.0.1^$domain=crust.network into brave://adblock helps for one user.
In order to improve the experience of our common users, we hope Brave could kindly add us to the white-list.

Hi, Is there any update on the demand?

Opened a ticket for it.