You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 6, 2024. It is now read-only.
Main purpose of this function is to get an array of transfer objects as input, and then prepare the transfer by **generating the correct bundle**, as well as **choosing and signing the inputs** if necessary (if it's a value transfer). The output of this function is an array of the raw transaction data (trytes).
304
304
305
-
You can provide multiple transfer objects, which means that your prepared bundle will have multiple outputs to the same, or different recipients. As single transfer object takes the values of: `address`, `value`, `message`, `tag`. The message and tag values are required to be tryte-encoded.
305
+
You can provide multiple transfer objects, which means that your prepared bundle will have multiple outputs to the same, or different recipients. As single transfer object takes the values of: `address`, `value`, `message`, `tag`. The message and tag values are required to be tryte-encoded. If you do not supply a message or a tag, the library will automatically enter empty ones for you. As such the only required fields in each transfers object are `address` and `value`.
306
+
307
+
If you provide an address with a checksum, this function will automatically validate the address for you with the Utils function `isValidChecksum`.
306
308
307
309
For the options, you can provide a list of `inputs`, that will be used for signing the transfer's inputs. It should be noted that these inputs (an array of objects) should have the provided 'security', `keyIndex` and `address` values:
308
310
```
@@ -469,7 +471,7 @@ If you want to have your transfers split into received / sent, you can use the u
469
471
470
472
#### Input
471
473
```
472
-
getTransfers(seed [, options], callback)
474
+
iota.api.getTransfers(seed [, options], callback)
473
475
```
474
476
475
477
1.**`seed`**: `String` tryte-encoded seed. It should be noted that this seed is not transferred
@@ -491,7 +493,23 @@ Similar to `getTransfers`, just a bit more comprehensive in the sense that it al
491
493
492
494
#### Input
493
495
```
494
-
getAccountData(seed [, options], callback)
496
+
iota.api.getAccountData(inputAddress)
497
+
```
498
+
499
+
1.**`inputAddress`**: `String` address used as input in a transaction
500
+
501
+
#### Returns
502
+
`Bool` - true / false
503
+
504
+
---
505
+
506
+
### `shouldYouReplay`
507
+
508
+
This API function helps you to determine whether you should replay a transaction or make a completely new transaction with a different seed. What this function does, is it takes an input address (i.e. from a spent transaction) as input and then checks whether any transactions with a value transferred are confirmed. If yes, it means that this input address has already been successfully used in a different transaction and as such you should no longer replay the transaction.
0 commit comments