Support subscan api
WoeOm opened this issue · comments
The subscan api already supports the multisig pallet, and multisig.subscan.io uses the subscan api to quickly access the network already deployed in subscan, reducing the deployment of subquery nodes as a parallel data indexing method. Of course, the way of subquery access is still optional.
I don't think it's a good idea, this will make dapp more depend on specific api, instead of 100% open source and trust free, currently users will be able to use alternative subquery if they do want to use the embed indexing rpc.
I don't think it's a good idea, this will make dapp more depend on specific api, instead of 100% open source and trust free, currently users will be able to use alternative subquery if they do want to use the embed indexing rpc.
Subscan API is just one way to provide historical transaction data, and subquery is still retained and will not be removed.
Non-open source APIs are at risk of fake transaction history. For example, api source modifying the ‘to’ parameter in the call data of a tx to a malicious address, but it will eventually be decoded in the multisig transaction preview dialog, Multisig members will still not sign this tx if they see the malicious ‘to’ address, so the risk is still low.