Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://reference.wolfram.com/language/workflow/AddASecondPrivateKeyToAnAddressInARK.html below:

Add a Second Private Key to an Address in ARK—Wolfram Documentation

We deliver solutions for the AI era—combining symbolic computation, data-driven insights and deep technical expertise

• Data & Computational Intelligence
• Model-Based Design
• Algorithm Development
• Wolfram|Alpha for Business
• Blockchain Technology
• Education Technology
• Quantum Computation

WolframConsulting.com

• On Desktop

Generate a second key pair for an address in ARK.

Use GenerateAsymmetricKeyPair to create an ARK key pair to be used for sending and receiving ark:

• The workflow uses the devnet blockchain for these examples. To use the mainnet blockchain, specify .

Use Export to save the private keys to a .wl file for later use:

• After this transaction is accepted, both keys must be used when signing.

Use BlockchainData to view the estimated transaction fee:

Using the preceding statistics, use Quantity to set an appropriate fee for the transaction:

Use BlockchainTransaction to build the transaction object with the chosen fee and the new public key:

• The transaction exists locally until it is submitted to the ARK blockchain.
• The sender is not part of the transaction until the transaction is signed.

Use BlockchainAddressData to determine if your address both has enough balance to add a second private key and does not already have a second one:

Since the “SecondPublicKey” field is empty, this address can be used.

Use BlockchainTransactionSign to sign the transaction with the private key:

• The transaction is now signed but not yet submitted to the blockchain. It only exists locally.
• Signing the transaction with the private key associated with the given address will also add the corresponding public key to the transaction.

Use BlockchainTransactionSubmit to send the transaction to the blockchain:

• After the transaction is submitted, you must wait for it to be included in a block.

Use BlockchainAddressData again to view the updated information for the address:

The “SecondPublicKey” is no longer empty and contains a PublicKey object.

• After the transaction is submitted, you must wait for it to be included in a block. The block can then be forged and added to the blockchain.

From now on, all of the transactions signed by this address should use a list of the main and second private keys in that order:

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4