[Ethereum] How to create wallet with web3j and web3swift like with web3js web3.eth.accounts.create(); function

iosweb3jweb3js

With web3js v1.0.0 you can create accounts with web3.eth.accounts.create(); and access the public address and private key with newWallet.address and newWallet.privateKey.

How can you do this with web3j or web3Swift.

The documentation is difficult to find this in.

Thanks for any help.

Best Answer

Here we go, by using web3swift library:

Create Account

    // Create keystore and account with password.    
    let keystore = try! EthereumKeystoreV3(password: "changeme"); // generates a private key internally if node "privateKey" parameter supplied
    let account = keystore!.addresses![0]
    print(account)

We are also working on unification of the API format. I already open issue to cover your need in the quesiton: https://github.com/matterinc/web3swift/issues/40

Here a usage example for the next major update of the library:

newWallet = web3.eth.accounts.create() 
// access the public address 
newWallet.address
//private key:
newWallet.privateKey

Related Solutions

[Ethereum] Web3j test accounts and Credentials object

Here is a more complete program than the one you provided. The only undefined part is Contract_sol_Contract, which you did not define. Notice how privateKey and publicKey are computed.

import org.web3j.crypto.Credentials;
import org.web3j.crypto.ECKeyPair;
import org.web3j.protocol.Web3j;
import org.web3j.protocol.http.HttpService;

import java.io.IOException;
import java.math.BigInteger;

public class SO3 {
    public SO3() throws IOException {
        Web3j web3 = Web3j.build(new HttpService("http://localhost:8545"));
        String account = web3.ethAccounts().send().getAccounts().get(0);
        Credentials credentials = Credentials.create(account);
        ECKeyPair keyPair = credentials.getEcKeyPair();
        BigInteger privateKey = keyPair.getPrivateKey();
        BigInteger publicKey = keyPair.getPublicKey();
        Contract_sol_Contract contract = Contract_sol_Contract.deploy(web3, credentials, new BigInteger("240000"), new BigInteger("2400000"), props).send();
    }
}

I think that the reason that web3j deviated from web3 in requiring just the public or private key is because providing less information is a better security practice. The web3 accounts docs has this warning: The accounts private key. This should never be shared or stored unencrypted in localstorage! Also make sure to null the memory after usage. This means passing around the entire accounts object is discouraged.

Seems the web3 authors knew they created a security issue because earlier on that same page they give this big fat warning: This package has NOT been audited and might potentially be unsafe. Take precautions to clear memory properly, store the private keys safely, and test transaction receiving and sending functionality properly before using in production!.

[Ethereum] I am using web3j and geth. How to create default accounts with some ether allocation to it

This tutorial cover the complete set of steps needed to develop your first smart contract in a private Ethereum node using web3j Java framework.

You can also use ganache instead of geth for development of DAPP. ganache pre-allocates 100 ethers to 10 accounts by default.

Best Answer

Create Account

Related Solutions

[Ethereum] Web3j test accounts and Credentials object

[Ethereum] I am using web3j and geth. How to create default accounts with some ether allocation to it

Related Topic