Transaction limit on blockchain.info's sendmany api call

[wetsuit]

Does anybody know if blockchain.info imposes some kind of hourly limit on its wallets, on the number of payments you can make ?

For example, today I sent 75 payments in a single transaction and after that trying to send 75 more gave me the following error :

{"error":"com.google.bitcoin.core.AddressFormatException: Illegal character O at 28"}

However I could send 50 in the next try. Then after 50 I tried to send another 50 but again got the above error. The same thing kept hapenning again and again and eventually I got the error when trying to send 10 payments. I waited a couple of hours and tried again and the 10 payments went through.

This made me feel like blockchain imposes some limit on the number of payments you can send per hour, even if they are combined in a single transaction.

No transaction was above 2 kb at any point and I sent more than enough transaction fees with each.

[1713933157]

1713933157

[1713933157]

1713933157

[michagogo]

{"error":"com.google.bitcoin.core.AddressFormatException: Illegal character O at 28"}

Why would you think that that error has anything to do with ratelimiting or anything like that? The error spells out clearly what the problem is. "com.google.bitcoin.core.AddressFormatException", meaning that it's a problem with the format of an address, and then it tells you explicitly that the address is invalid because it contains an illegal character, namely the capital letter O. If you haven't already, I strongly suggest you read https://en.bitcoin.it/wiki/Base58Check_encoding and https://en.bitcoin.it/wiki/Technical_background_of_version_1_Bitcoin_addresses .

[wetsuit]

{"error":"com.google.bitcoin.core.AddressFormatException: Illegal character O at 28"}

Why would you think that that error has anything to do with ratelimiting or anything like that? The error spells out clearly what the problem is. "com.google.bitcoin.core.AddressFormatException", meaning that it's a problem with the format of an address, and then it tells you explicitly that the address is invalid because it contains an illegal character, namely the capital letter O. If you haven't already, I strongly suggest you read https://en.bitcoin.it/wiki/Base58Check_encoding and https://en.bitcoin.it/wiki/Technical_background_of_version_1_Bitcoin_addresses .

Oh wow, you are absolutely right. Thank you very much!

[michagogo]

{"error":"com.google.bitcoin.core.AddressFormatException: Illegal character O at 28"}

Why would you think that that error has anything to do with ratelimiting or anything like that? The error spells out clearly what the problem is. "com.google.bitcoin.core.AddressFormatException", meaning that it's a problem with the format of an address, and then it tells you explicitly that the address is invalid because it contains an illegal character, namely the capital letter O. If you haven't already, I strongly suggest you read https://en.bitcoin.it/wiki/Base58Check_encoding and https://en.bitcoin.it/wiki/Technical_background_of_version_1_Bitcoin_addresses .

Oh wow, you are absolutely right. Thank you very much!

You're welcome 

[kjj]

Wait...  Are you typing addresses by hand?

[wetsuit]

Wait...  Are you typing addresses by hand?

No, user provided addresses. Some like to input their address in all caps I have noticed which screws things up.

[MPOE-PR]

Why would you think that that error has anything to do with ratelimiting or anything like that? The error spells out clearly what the problem is. "com.google.bitcoin.core.AddressFormatException", meaning that it's a problem with the format of an address, and then it tells you explicitly that the address is invalid because it contains an illegal character, namely the capital letter O. If you haven't already, I strongly suggest you read https://en.bitcoin.it/wiki/Base58Check_encoding and https://en.bitcoin.it/wiki/Technical_background_of_version_1_Bitcoin_addresses .

Oh wow, you are absolutely right. Thank you very much!

You're welcome 

This exchange kinda made my forumday. Well done.