Upload process must support many broadcast URLs

[derekm]

The upload tool currently only uses BitIndex to broadcast transactions.

If BitIndex gets overwhelmed and experiences a denial of service outage, other block explorers will need to be leveraged to continue broadcasting transactions.

[Kakifrucht]

Currently, this script is coupled with the BitIndex API on multiple fronts, not just to broadcast transactions, which is why I don't really see alot of value in allowing the user to select a broadcasting endpoint (if BitIndex is down, the script doesn't work at all).

I guess we could kind of decouple by choosing a suitable Planaria node to monitor our outputs, as these endpoints are easier to swap out due to a standardized API (and discovery of endpoints via routes, even though that seems out of scope for a little script like this one). However that would involve a little more work, as BitIndex does make some things easier for us.

That makes me think, we might need a Bitcom protocol that allows people to discover HTTP transaction broadcasting endpoints via the blockchain.

[amritabithi]

You can do this in IPv6 if the endpoints support it.