Refactor Nearlib

[ilblackdragon]

There are few things we want to improve:

Configuration search:

• For Node.js use cases, search for .near/ folder with config and keys. Main uses cases:
  • local to project (so go up to folder with node_modules / package.json and check for .near). This can be official TestNet and custom network.
  • running node connected to official TestNet (~/.near/ for configs). Want to use it, but need to use contract helper for account creation.
  • running custom network with local node (~/.near/ for configs). Want to use local key pair for account creation.
• Create various types of transactions functions that support creating and signing transactions (without having connection).
• ConnectProvider interface that various providers like RPC, RPCv2, Network, WebSockets can implement (e.g. current NearClient is RPC provider). Provides sendTransaction(txBytes, [timeout]) -> Promise<FinalTransactionResult> and query(path, data) -> Promise<QueryResult> interfaces.
• AccountCreatorProvider - interface, that either uses helper or given keys to create accounts.
• connect that is configured / or searches for configuration and uses given ConnectProvider, AccountCreatorProvider and KeyStore.
• Account abstraction, that provides accessors to account state (balance, etc), access keys (with permissions per key), etc. Allows to initialize Contract with it to send Tx from it.
• Wallet API is defined via 2 URLs: "Authorize App" API and "Sign Tx" API.
• Contract handles itself sending to Wallet if currently signed Tx is not allowed by access key or access key is missing.
• KeyStore should have some form of Wallet to provide what are current accounts available for given network, and allow to change accounts and networks. Also this should use Wallet API to "login" to retrieve current account id if unavailable.

[vans163]

setItem for localstorage tokens/secretket is kinda inbetween nearwallet and nearlib. The secretket is set in nearlib and the account id and tokens are set in nearwallet. Should these be all set in nearlib, or shipping to wallet?

[vgrichina]

@vans163 it's perfectly valid use case not not use wallet at all. From our POV wallet is basically a special type of Signer.

[vans163]

Yea I am thinking that thin API in wallet repo should be moved into nearlib

[DanielRX]

Could "Create various types of transactions functions that support creating and signing transactions (without having connection)" be made into an issue alone? I can do it if you want (basically we really need the ability to sign a tx, then send it on a different machine)

[bowenwang1996]

@DanielRX feel free to do it

[DanielRX]

After thinking about it, "Create various types of transactions functions that support creating and signing transactions (without having connection)" is impossible, so I'm not sure what you want to do about that? Do you want to scrap the idea of doing so without a connection?

[ilblackdragon]

This actually have been mostly done back in June/July. Closing this.