v1.7.1 - Add AllAccountBalances API and Fix preprocess-operations URL Naming Consistency

Adding two enhancements to the Rosetta API specification:

• AllAccountBalances API - New POST /account/all-balances endpoint to retrieve all sub-account balances in a single request
• URL Naming Fix - Changed /construction/preprocess_operations to /construction/preprocess-operations for kebab-case consistency

What's Changed

• feat: All account balances by @jacquescaocb in #128

Full Changelog: v1.6.1...v1.7.1

v1.6.1 - Add ConstructionPreprocessOperations API endpoint

This endpoint provides fallback parsing for high-level transaction construction operations when local OperationSelector doesn't support certain construct operations.

Features:

• Input format matches TransactionConstructOpInput from chainstdio
• Output format matches ParseTransactionConstructOp return values
• Optional API (servers can return 501 Not Implemented)
• Full OpenAPI specification with request/response schemas
• Maintains compatibility with existing operation parsing workflows

Endpoint: POST /construction/preprocess_operations
Request: ConstructionPreprocessOperationsRequest
Response: ConstructionPreprocessOperationsResponse

What's Changed

• feat: Add ConstructionPreprocessOperations API endpoint by @jacquescaocb in #127

New Contributors

• @jacquescaocb made their first contribution in #127

Full Changelog: v1.5.1...v1.6.1

v1.5.1 - Update versions to match

api.json
The api.json was not updated earlier. This synchronizes the api.json with the branch release tag.

What's Changed

• Rename to Mesh and upgrade Golang version. by @xiaying-peng in #120
• fix project name by @xiaying-peng in #121
• fix ref by @xiaying-peng in #122
• Bump version to 1.5.1 by @rafalio-cb in #126

New Contributors

• @xiaying-peng made their first contribution in #120
• @rafalio-cb made their first contribution in #126

Full Changelog: v1.4.15...v1.5.1

Support BIP-340 Schnorr curve

What's Changed

• Add Support for BIP-340 Schnorr by @sleepdefic1t in #114

New Contributors

• @sleepdefic1t made their first contribution in #114

Full Changelog: v1.4.14...v1.4.15

remove max_fee and suggested_fee_multiplier in Preprocess Request

What's Changed

• remove public key in metadata by @jingweicb in #106
• [metadata]add public key back by @jingweicb in #109
• [preprocess]remove max_fee and mulltiplier in preprocess request by @jingweicb in #110

New Contributors

• @jingweicb made their first contribution in #106

Full Changelog: v1.4.13...v1.4.14

Remove peers as required field

What's Changed

• [chore] update circleci by @shrimalmadhur in #96
• Update README and CONTRIBUTING files by @racbc in #92
• Update text in Issue Templates by @racbc in #97
• Fix rosetta-cli link to correct repo by @racbc in #98
• replace CircleCI with gh actions by @irisZhangCB in #102
• Remove peers as a required field in NetworkStatusResponse by @racbc in #103
• (chore) Update API version to 1.4.13 by @racbc in #105

Full Changelog: v1.4.12...v1.4.13

Case bug fix for spec

What's Changed

• [chore] fix case issue by @shrimalmadhur in #94

Full Changelog: v1.4.11...v1.4.12

Support for Pallas Curve

This release introduces support for Pallas curve type and hash case sensitivity to the spec

Changelog

• Add support for Pallas Curve ( #93 )
• Add hash case sensitivity to the spec (#83 )

Support for Related Transactions

This release introduces support for related transactions (i.e. transactions that span multiple blocks). This additional annotation makes it much easier for developers to link multi-block/multi-network transactions together to determine success.

Changelog

• Add Support for Related Transactions #74

Support Quiescent Blockchains

This release adds support for "quiescent" blockchains (only produce blocks/transactions when necessary) to the specification. Normally, Rosetta clients use a tip delay to determine if a blockchain is healthy (i.e. is the current block < 60 seconds old) but this doesn't work for blockchains that can become dormant for some period of time. Quiescent blockchains should populate the NetworkStatusResponse.SyncStatus.Synced field with the sync status so that clients can assess the healthiness of the implementation without relying on the current block timestamp.

Changelog

• Return Synced Status #71
• [indexer] Add total_count field #70