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
We need a standardized way for dApps to identify specific Cardano test networks they're connected to. While CIP-0030's getNetworkId() can distinguish between mainnet and testnet, it cannot differentiate between various test networks (preview, preprod, etc.).
Current Problem
getNetworkId() only returns 0 (testnet) or 1 (mainnet)
dApps cannot programmatically determine which specific test network they're connected to
Makes automated testing and network-specific configurations more difficult
Forces developers to use workarounds or manual network selection
Proposed Solution
Add a new CIP that extends CIP-0030 with a getNetworkMagic() function that returns the network's magic number:
Overview
We need a standardized way for dApps to identify specific Cardano test networks they're connected to. While CIP-0030's
getNetworkId()
can distinguish between mainnet and testnet, it cannot differentiate between various test networks (preview, preprod, etc.).Current Problem
getNetworkId()
only returns 0 (testnet) or 1 (mainnet)Proposed Solution
Add a new CIP that extends CIP-0030 with a
getNetworkMagic()
function that returns the network's magic number:Benefits
Related Links
CIP-0142? | Web-Wallet Bridge - Network Determination #960
The text was updated successfully, but these errors were encountered: