Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add new property nextExchangeRate in the receipt #2122

Open
agadzhalov opened this issue Dec 4, 2024 · 0 comments
Open

Add new property nextExchangeRate in the receipt #2122

agadzhalov opened this issue Dec 4, 2024 · 0 comments
Assignees
Milestone

Comments

@agadzhalov
Copy link
Contributor

Description

Currently when you get the receipt of a transaction there's a property exchangeRate, but if you look at exchange_rate.proto you will see there is an ExchangeSetRate that contains two properties - currentRate and nextRate which is not returned on receipt. The exchangeRate returned to the client from the SDK displays only currentRate instead of both.

Current receipt

TransactionReceipt {
  transactionId = [email protected],
  status = SUCCESS,
  exchangeRate = ExchangeRate {
    hbars = 1,
    cents = 12,
    expirationTime = 2100-01-01T00:00:00Z,
    exchangeRateInCents = 12.0
  },
  accountId = 0.0.5162,
  fileId = null,
  contractId = null,
  topicId = null,
  tokenId = null,
  topicSequenceNumber = null,
  topicRunningHash = null,
  totalSupply = 0,
  scheduleId = null,
  scheduledTransactionId = null,
  serials = [],
  duplicates = [],
  children = []
}

Solution

Add new property nextExchangeRate to the receipt

@agadzhalov agadzhalov changed the title Add new propertynextExchangeRate in the receipt Add new property nextExchangeRate in the receipt Dec 4, 2024
@0xivanov 0xivanov assigned 0xivanov and naydenovn and unassigned 0xivanov Dec 5, 2024
@agadzhalov agadzhalov added this to the v2.47.0 milestone Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants