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.

Sign up for GitHub

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

Jump to bottom

'amounts-as-strings': 'true' for Maestro provider endpoints #235

Open
Vardominator opened this issue Nov 13, 2023 · 0 comments · Fixed by Anastasia-Labs/lucid#2
Open

'amounts-as-strings': 'true' for Maestro provider endpoints #235

Vardominator opened this issue Nov 13, 2023 · 0 comments · Fixed by Anastasia-Labs/lucid#2

Comments

@Vardominator
Copy link
Contributor

Vardominator commented Nov 13, 2023 •
edited
Loading

Use the 'amounts-as-string': 'true' request header to prevent overflow or rounding errors for large numbers. The following endpoints take this header into account:

  • GET /accounts/{stake_addr}/assets
  • GET /addresses/{address}/utxos
  • POST /addresses/utxos
  • GET /addresses/cred/{credential}/utxos
  • POST /addresses/cred/utxos (NEW ENDPOINT)
  • GET /pools/{pool_id}/info
  • POST /transactions/outputs
    We'll need to update any Maestro provider functions that can utilize this feature.
@Vardominator Vardominator changed the title 'amounts-as-string': 'true' for Maestro provider endpoints 'amounts-as-strings': 'true' for Maestro provider endpoints Nov 14, 2023
@sourabhxyz sourabhxyz mentioned this issue Nov 16, 2023
Closed
sourabhxyz added a commit to sourabhxyz/lucid that referenced this issue Nov 25, 2023
@sourabhxyz
Feat spacebudz#235: Update in Maestro provider to allow for correctly…
8e39e48 
… parsing 64 bit signed integer values
@sourabhxyz sourabhxyz mentioned this issue Nov 25, 2023
Merged
colll78 added a commit to Anastasia-Labs/lucid that referenced this issue Nov 25, 2023
@colll78
Merge pull request #2 from sourabhxyz/235-handle-upto-int64
03a9499 
Fix spacebudz#235: Update in Maestro provider to correctly parse for large integers in response
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@Vardominator