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
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently, NAJ has multiple objects to simplify using a wallet and interacting with a contract.
In the following weeks the Wallet Selector (WS) will become the default way to connect to NEAR.
My question is: after WS becomes mainstream, what will be the role of NAJ in interacting with contracts?
WalletConnection
object disappear? Makes sense to deprecate it since wallet selector will be the way to create a wallet object.Contract
object disappear? This one could be modified to take a Wallet Selector instead of an Account.Discussion around point 2: The
Contract
Object.Using the wallet selector, the current flow to interact with a contract is:
For calling methods (which is what most of the people is doing from a frontend) this is kind of annoying, since you need to sign a
FunctionCall
forchange
methods, but still need to usenear-api-js
for callingview
methods.However, I like sticking to the simple concept of "a wallet is an object to sign transactions", with no
Contract
object involved.So maybe we just remove
Contract
and only use the wallet selector?.Beta Was this translation helpful? Give feedback.
All reactions