Shulou(Shulou.com)06/01 Report--

This article focuses on "what is the method of creating Stellar/XLM transactions". Interested friends may wish to have a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn "what is the method of creating Stellar/XLM transactions?"

Stellar transactions are commands that can change the status of the account, including payment, creating a proxy, modifying account configuration, and so on. Each transaction has a source account that pays the transaction fee and occupies a transaction serial number. An Stellar transaction contains one or more operations, each with a source account, which defaults to the source account of the transaction.

1. Stellar transaction constructor

The TransactionBuilder class of JS Stellar SDK is used to build new transactions, and its constructor needs to specify an account as the source account for the transaction. When the build () method of TransactionBuilder is called, the transaction sequence number of the source account is incremented.

You can use the addOperatioins () method to add an action to a Stellar transaction object. You can check the available operations listed in operation.js, which returns the current TransactionBuilder object, so you can chain the method multiple times.

After the desired action is added, the build () method is called to generate the Stellar transaction, which will contain the transaction serial number of the specified source account. The transaction is unsigned and must be signed before it can be sent to the Stellar network.

/ / StellarBase.Network.usePublicNetwork (); use Stellar main chain / / create Stellar account object var account=new StellarBase.Account ("GD6WU64OEP5C4LRBH6NK3MHYIA2ADN6K6II6EXPNVUR3ERBXT4AN4ACD", "2319149195853854") with the specified address and serial number Var transaction = new StellarBase.TransactionBuilder (account, {fee: StellarBase.BASE_FEE, networkPassphrase: Networks.TESTNET}) / / add payment operation .addOperation StellarBase.Operation.payment ({destination: "GASOCNHNNLYFNMDJYQ3XFMI7BYHIOCFW3GJEOWRPEGK2TDPGTG2E5EDW", asset: StellarBase.Asset.native () Amount: "100.50" / / 100.50 XLM}) / / add option configuration operation .addOperation (StellarBase.Operation.setOptions ({signer: {ed25519PublicKey: secondAccountAddress, weight: 1}})) / / set transaction timeout .setTimeout (30) .build () 2. Stellar transaction serial number

The serial number in the Stellar transaction must be the same as the serial number in the source account of the transaction, otherwise the transaction is considered invalid. After the transaction is submitted and applied to the account book, the serial number of the source account will be increased by 1.

There are two ways to ensure that you get the correct serial number:

The serial number of the reader's account before submitting the transaction

Local administrative serial number

When transaction throughput is high, extracting the serial number of the source account from the network may not return the correct value. Therefore, if you submit a large number of transactions at high frequency, you should track the serial number locally.

3. Add remarks to the Stellar transaction

A memo field can be included in a Stellar transaction to attach additional remarks. You can pass in a comment object when you create a TransactionBuilder. There are five types of comment objects:

Memo.none: empty comment

Memo.text:28 byte ascii encoded string remarks

Numeric remarks for Memo.id:64 bytes

Memo.hash:32 byte hash, such as the hash of an entry on a content server

Memo.returnHash:32 byte hash for rejected transactions

Var memo = Memo.text ('Happy daylight'); var transaction = new StellarBase.TransactionBuilder (account, {memo: memo, fee: StellarBase.BASE_FEE, networkPassphrase: Networks.TESTNET}) .addOperation (StellarBase.Operation.payment ({destination: "GASOCNHNNLYFNMDJYQ3XFMI7BYHIOCFW3GJEOWRPEGK2TDPGTG2E5EDW", asset: StellarBase.Asset.native (), amount: "2000"}) .setTimeout (30) .build () 4. Convert base64 code stream to Stellar transaction object

You may not want to instantiate trading objects directly, because TransactionBuilder is usually used to create Stellar trading objects. However, you can also use base64-encoded transaction packets to create a new transaction object.

Var transaction = new Transaction (envelope)

Once the transaction is created from the packet, its properties and operations should no longer be changed. You should only add signatures to the transaction object before submitting the transaction to the Stellar network.

Most importantly, you can use the sign () method to sign a transaction object, as described below.

5. Signature of Stellar transaction

Stellar transactions require signatures for authentication purposes, and usually only one signature is required in a Stellar transaction. But you can achieve more complex verification controls by adding the signatures required for transactions, and we will introduce the multi-signature mechanism in subsequent articles.

You can use the sign () method of the transaction object to add a signature to the Stellar transaction, just as you can call the sign () method chained multiple times.

The Keypair class is used to represent the key pair used to sign a transaction in an Stellar network. A Keypair object can contain a public key and a private key, or only a public key.

If the Keypair object does not contain a private key, you cannot use it to sign the transaction. The most convenient way to create a new key pair is to pass in the account's ciphertext seed:

Var keypair = Keypair.fromSecret ('SBK2VIYYSVG76E7VC3QHYARNFLY2EAQXDHRC7BMXBBGIFG74ARPRMNQM'); var address = keypair.publicKey (); / / GDHMW6QZOL73SHKG2JA3YHXFDHM46SS5ZRWEYF5BCYHX2C5TVO6KZBYLvar canSign = keypair.canSign (); / / true

You can use the original byte stream of the ciphertext seed to create a Keypair object:

Var keypair = Keypair.fromRawSeed ([0xdc, 0x9c, 0xbf, 0xb5, 0xd7, 0x12, 0x83, 0x6a, 0xbf, 0x7d, 0x5d, 0xd8, 0xc4, 0xc4, 0x3e, 0x9d, 0xc7, 0x81, 0x85, 0xf1, 0x4b, 0x12, 0x0e, 0x9b, 0x59, 0x5d, 0x62, 0x65, 0x52, 0xa8, 0xcb, 0xcc]); var address = keypair.publicKey (); / / GADMPH2LB7VDK4UHNGKMJIJBXC5WTWTQMXYWSPVWPMNVVR4MGWLI2IXNvar canSign = GADMPH2LB7VDK4UHNGKMJIJBXC5WTWTQMXYWSPVWPMNVVR4MGWLI2IXNvar canSign (); / / GADMPH2LB7VDK4UHNGKMJIJBXC5WTWTQMXYWSPVWPMNVVR4MGWLI2IXNvar canSign

You can also create a randomly generated key pair:

Var keypair = Keypair.random ()

With the key pair containing the private key, you can sign the transaction:

Var key1 = Keypair.fromSecret ('SBK2VIYYSVG76E7VC3QHYARNFLY2EAQXDHRC7BMXBBGIFG74ARPRMNQM'); var key2 = Keypair.fromSecret (' SAMZUAAPLRUH62HH3XE7NVD6ZSMTWPWGM6DS4X47HLVRHEBKP4U2H5E7'); / / create the Account object var account=new StellarBase.Account ("GD6WU64OEP5C4LRBH6NK3MHYIA2ADN6K6II6EXPNVUR3ERBXT4AN4ACD", "2319149195853854") with the specified address and serial number Var transaction = new StellarBase.TransactionBuilder (account, {fee: StellarBase.BASE_FEE, networkPassphrase: Networks.TESTNET}) .addOperation (StellarBase.Operation.payment ({destination: "GASOCNHNNLYFNMDJYQ3XFMI7BYHIOCFW3GJEOWRPEGK2TDPGTG2E5EDW", asset: StellarBase.Asset.native (), amount: "2000" / / 2000 XLM}) .setTimeout (30) .build (); transaction.sign (key1); transaction.sign (key2) / / submit the transaction object to the Horizon API service here. I believe you have a better understanding of "what is the method of creating Stellar/XLM transaction". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.