You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some dapps might want to optimize the Protocl params fetching to avoid calling the provider endpoints each time you instantiate Translucent.
Translucent.new could be modified to new(provider, network, protocolParams) to allow passing the protocol parameters and that would avoid calling provider.getProtocolParamateres
The text was updated successfully, but these errors were encountered:
yep. Maybe a cooler way to do this would be making providers composable so you can layer a provider that you build for your dApp over others. Lots of dApps need very specific fetching of data so I think this would be an important pattern that solves the same issue.
Some dapps might want to optimize the Protocl params fetching to avoid calling the provider endpoints each time you instantiate Translucent.
Translucent.new
could be modified tonew(provider, network, protocolParams)
to allow passing the protocol parameters and that would avoid calling provider.getProtocolParamateresThe text was updated successfully, but these errors were encountered: