-
Notifications
You must be signed in to change notification settings - Fork 24
Open
Labels
Description
Add support of batch txs
https://xrpl.org/es-es/docs/references/protocol/transactions/types/batch
example
https://dev.bithomp.com/en/tx/0C5956CF40BD544278D72697FF3FAC00571A52196252E006A2EDB8381D96E252
/v3/transaction/:hash
support for batch txs:
specification.transactions[]
each transaction will have formatted specification data
transaction:
id - generated on our side from RawTransaction data
address - from RawTransaction
sequence - from RawTransaction
type - from RawTransaction
specification - generated on our side from RawTransaction data
specification.flags -- all transactions will have its own type depended flags, including Global ones
Note: global flags are diffrrent for XRP/XAH networks
example: https://dev.bithomp.com/api/cors/v3/transaction/0C5956CF40BD544278D72697FF3FAC00571A52196252E006A2EDB8381D96E252
/v3/transaction/:hash
tx creadted by batch will have hash from original transactions
outcome.parentBatchID
example: https://dev.bithomp.com/api/cors/v3/transaction/C8D02BA16B50C5BD12126F6864EB14AF1A33B31DE9053CAC5C5667BD77A37719
The difference with "normal" transactions: it will have a new key in specification with batch basic transactions data
To recognise if its a batch: flags, and transaction flags
The support on devnet is needed.
Example:
https://github.com/Bithomp/xrpl-api/blob/3851db65bd6c9c2767e7b54a7ec722171df117e6/test/examples/responses/Batch.json
To find more examples:
https://github.com/Bithomp/xrpl-api/blob/master/test/models/transaction.test.ts#L7033