0

Using blockfrost I have pulled a list of addresses of owners of a specific fungible token. Some of the addresses are significantly smaller than the others (about 2/3 the length).

When querying blockfrost for stake keys (or pool.pm) with those addresses i get an error 504 after a long timeout, while all the others work smoothly.

An example of the syntax and function used with python is the following api.address(addr_str)

Here is the address causing me trouble addr1w999n67e86jn6xal07pzxtrmqynspgx0fwmcmpua4wc6yzsxpljz3

How should I handle those, what are they?

1 Answer 1

4

Those are called Enterprise addresses, originally intended for exchanges but everyday users have started to adopt them for various reasons. Unfortunately, I can't speak to why Blockfrost API chokes when it encounters one, but there are other APIs that support these. Try Koios for example.

https://api.koios.rest/#get-/address_assets

EDIT: Ah! Just noticed an important part of your message.. The reason you're getting the timeout error is because enterprise addresses do not have stake addresses as they were never meant to stake (again they are intended for exchanges). That's why this is timing out.

2
  • Wow, thanks for the great answer !! That makes perfect sense. Do you have any specific way to spot those addresses (length of the address?)
    – Lokinou
    Mar 4, 2022 at 9:01
  • 1
    Yes, length of address would be a great way to go. As far as I know the enterprise addresses are all the same length. The reason they are shorter is because they lack the stake key hash.
    – Tygar Pool
    Mar 4, 2022 at 12:15

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.