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
This is concerning as "Soon" is not defined nor is there a reference to when soon will be, a blog post would be helpful.
Also, I heavily use near-cli (https://github.com/near/near-cli) to execute near login which opens wallet.near.org or wallet.testnet.near.org to add a FAK locally for development purposes. What is the expectation or direction on how to handle this? Especially if I move my account to another wallet interface.
The url seems to be hard coded to wallet.near.org or wallet.testnet.near.org depending on NEAR_ENV environment setting.
The text was updated successfully, but these errors were encountered:
Great feedback @agileurbanite - we'll incorporate this feedback in regards to messaging before launching this on wallet.near.org/mainnet.
@janewang can you please shed some light on what the long-term strategy for CLI and wallet interactions will look like? The CLI is currently dependent on the NEAR wallet to allow CLI login. I can see the potential for wallet.near.org still serving as the 'hub' for CLI login, but allow any other supported wallet to add the FAK needed for CLI to execute transactions on the users behalf.
Today I saw this message on my wallet:
This is concerning as "Soon" is not defined nor is there a reference to when soon will be, a blog post would be helpful.
Also, I heavily use near-cli (https://github.com/near/near-cli) to execute
near login
which opens wallet.near.org or wallet.testnet.near.org to add a FAK locally for development purposes. What is the expectation or direction on how to handle this? Especially if I move my account to another wallet interface.The url seems to be hard coded to wallet.near.org or wallet.testnet.near.org depending on NEAR_ENV environment setting.
The text was updated successfully, but these errors were encountered: