A desktop node running on a Mac has added 123 routes compatible with indexers from both the v3 and v4 generations to its local HTTP service. They’re disabled by default. The compatibility is in the request format, not the data source: legacy tools can point to the local machine and read the index stored there, with little or no need to change the querying code. Keeping the service disabled by default isn’t just a matter of convenience, either. Once enabled on a local network, it could be accessed by other devices on the same network, so it’s safer to leave the switch in the user’s hands. The value of this kind of compatibility layer lies in reducing migration costs: changing an interface means rewriting clients, which is far more costly than having an index that’s a few days behind. The 123 routes must now be enabled manually; whether to enable them is up to the user. This article discusses design trade-offs only and does not constitute investment advice.
#Dogecoin #Web3 $DOGE
#Dogecoin #Web3 $DOGE