Migrating your Tools from Ark Node to Ark Core
This article will guide you through the steps required to migrate your tools and applications from Ark Node to Ark Core so you can be ready in time for the hard-fork in a few months without having to do last minute migrations.
In Ark Node you would post your signed transactions to the P2P API at http://127.0.0.1:4002/peer/transactions and receive a list of transaction IDs.
This endpoint is still available in Ark Core. However, you are now advised to use http://127.0.0.1:4003/api/v2/transactions to post your transactions. It behaves the same way as the P2P API but has no risk of being deprecated in the near future as it is integrated into the new Public API.
This new endpoint will return you 3 lists of transaction IDs:
- Transactions that have been accepted to be processed.
- Transactions that have exceeded the throttle limit.
- Transactions that have been deemed as invalid.
Having those 3 lists allows you to stash excessive or invalid transactions and rebroadcast them at a later time or figure out what is wrong with them.
Note on excessive transactions You can circumvent the transaction throttling that results in excessive transactions by white listing your wallets public key in the configuration.
Paginating the 2.0 API
Ark Core currently supports both the 1.0 API from Ark Node which will be removed in the near future and the new 2.0 API which provides proper pagination of data and indicates how much data is available.
If you interact with the 2.0 API and wish to paginate data you can simply append
?page=4&limit=25 to the URL. The response will contain a
meta field that will contain the total count of records available, where you currently are and URLs to the next, previous, first and last page of items available.
Having those meta fields available will allow you to easily loop over all available pages without doing some wonky client side calculations to figure out how many pages there are. Simply send requests until