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
villanuevawill commented 2 hours ago @thelostone-mc - 485 and 487 show up. This is a pretty extreme edge case where 486 does not exist on the rinkeby testnet. Most ids will exist from the mainnet that exist on rinkeby. We should def. update this, but I think there are only 3 ids that don't exist in rinkeby that exist in mainnet.
Basically the way the Bounties Network operates is that we use whichever Ethereum network gets injected by MetaMask, whether it's MainNet or Rinkeby. A fix for this could entail us embedding the network type directly in the URL, but this would likely break our existing URL structure.
I will push a fix which changes the error message depending on the current network.
Issue
Mainnet bounty shows wrong text when logged on rinkerby network via metmask
Steps to Reproduce
Login into the test net (rinkerby) via metamask and open a bounty funded on the mainnet like
https://beta.bounties.network/bounty/v1/486
Fix
Update the content to use the current active network rather than hardcoding the message
The text was updated successfully, but these errors were encountered: