Or visit a node on the Jungle testnet:
3. Access the wallet serverThe new version of Keosd no longer provides RPC API documentation, which may mean that it has begun to slide to the edge in the EOS software stack. However, you can access the old version of the documentation at this address:
https://developers.eos.io/eosio-nodeos/v1.1.0/reference
Use the WalletClient class to access Keosd's rpc interface. For example, the following code accesses the list_wallets interface of Keosd that runs natively:
Since Keosd's API is no longer grouped, the RPC corresponding method is directly hung on the WalletClient object, which is a difference. Like NodeClient, the call to WalletClient returns an RpcOutput object.
Keosd version 1.4 uses UNIX sockets instead of HTTP to provide RPC interfaces by default, which may be considered safer to use IPC considering that in most cases Keosd runs natively. Therefore, this is also the default instantiation option for WalletClient, and in most cases, no additional parameters need to be passed in to instantiate the WalletClient.
4. Private and public keys
EOS's key algorithm is similar to Bitcoin, but with some tweaks and defining its own format.
Use the static method of the PrivateKey class new() to generate a random private key. For example:
toEos() method is used to convert private key objects into a custom format for EOS.
4.1 Public Key Derivation
The public key can be derived from the private key, such as:
Similarly, use the toEos() method to convert the public key to a custom format for EOS.
4.2 Import EOS Private Keys
You can convert an EOS-formatted private key into an EosTool PrivateKey object, for example, the code below imports the specified EOS private key and displays its corresponding EOS public key: