You’d have to contact XinFin to ask that.. easier solution to test is just deploy an archive node locally in your office. Then set your local NAT to forward the public-facing RPC port of the NAT to the RPC port on your local archive node machine. That will let you test it. If it works on your own archive node then it means everything is working on your app fine. And then you know that the issue is purely the CORS issue.
Another option is to reach out to blockscan and/or ankr and ask them directly via their support if they have a CORS-permissive archive node you can use for your app. If they say yes then I imagine access would be quite affordable
Also plugin.global have an RPC service available as well but I think at present it was aiming for full nodes…. You could ask them if they have archive nodes as well, and if so how to access and whether you can test on it or how much access will cost. I imagine they’ll be competitive with the other commercial RPC providers..
For further actions, you may consider blocking this person and/or reporting abuse
You’d have to contact XinFin to ask that.. easier solution to test is just deploy an archive node locally in your office. Then set your local NAT to forward the public-facing RPC port of the NAT to the RPC port on your local archive node machine. That will let you test it. If it works on your own archive node then it means everything is working on your app fine. And then you know that the issue is purely the CORS issue.
Another option is to reach out to blockscan and/or ankr and ask them directly via their support if they have a CORS-permissive archive node you can use for your app. If they say yes then I imagine access would be quite affordable
Also plugin.global have an RPC service available as well but I think at present it was aiming for full nodes…. You could ask them if they have archive nodes as well, and if so how to access and whether you can test on it or how much access will cost. I imagine they’ll be competitive with the other commercial RPC providers..