blockcypher / explorer Goto Github PK

Right now, "server side" API calls are made using the API key @matthieu gave me and are not visible to the client. Client-side calls do not use an API key and are not tracked. If you want to give me a different key to attach to those (it will be publicly visible in the source code), I'm happy to add.

This also might help with running up against limits, but I'm not sure.

@matthieu please either close this if you think it's not worth doing or assign back to me to add throughout (and give me a key please). Thanks!

http://blockcypher.herokuapp.com/btc/address/1LuckyR1fFHEsXYyx5QK4UFzv3PEAepPMK/

Also make tx API calls to get summary data for the transactions.

All uses of satoshis_to_btc must be checked for compatibility:
https://github.com/blockcypher/pyblockcypher/blob/more_methods/blockcypher/utils.py

Related to #32

With a separate API call I can get rid of the jittery-ness as it loads.

Doh, I didn't realize these were excluded with txrefs!

@matthieu I think a better name for txrefs would be confirmed_txrefs, that way it isn't ambiguous and you immediately know that txrefs excludes unconfirmed_txrefs

This will be on both the transaction and address page.

It could be done with JS polling too, though I don't see a reason to do that.

From @michliga:

I noticed that the sent and received are both wrapped in {% if %}s with the condition of 'has_more'. I'm not sure what this variable means. Could you explain?

It's an ugly hack, I'll fix this up before launch. For now don't worry about the logic and just assume the data is good (I'll make that true).

Doing some mobile testing and noticing it is a little hard to get around the site quickly. I think we could use that header real estate a little better. Do you agree @mflaxman ?

"600 seconds ago" should be "10 mins ago"

From @matthieu:

Do you think it'd be appropriate to provide specific information about people's webhooks in the explorer as well? Like which webhooks have been created, be able to create, list and delete them. I could add information like the last errors returned or last message sent. Of course in this case people would have to enter their api key someplace.

Some observations:

• I think "Home" is redundant (only visible when you're not on the homepage) as live.blockcypher.com is already on the far left of the header and is the home button
• Should live.blockcypher.com have some sort of a logo (like on blockcypher.com)?
• @matthieu should there be a "contact us" button? It's just a placeholder.
• @matthieu do you like the footer? It uses the main blockcypher facebook/twitter social media links. "Powered by the BlockCypher Bitcoin API" links to the blockcypher homepage (not pyblockcypher), but I think that's the right decision.

Assigning to @matthieu first for decisions. Please handover to Amelia once we know what we're doing here.

http://cl.ly/image/1W2t3y100C3y

Maybe we could kill the second "330 Transactions" and incorporate the results with pagination? Maybe Page 1 (transactions 1-5) of 66. IDK, that doesn't sound great either :(

Try typing ins something like "asdf" to see. It's worse if you do something that's real enough you were expecting it to work (say a tx hash with an accidental trailing slash)

Waiting on @matthieu to implement this in the API this weekend. See email thread "unconfirmed_txrefs have no received attribute" for details.

1. Find an unconfirmed transaction here: https://live.blockcypher.com/btc/
2. Try to select the span in your console and get nothing: $('#receive-cnt')
3. This breaks this line:

   explorer/templates/transaction_overview.html

   Line 295 in e677575

   $('#receive-cnt').text(data['receive_cnt']);

Any ideas? I'd like to stick with everything as-is and just find a way to make the selector work. I need access to that data via jQuery so if we can't find a way we'll have to move away from popover.js. I can spend some time digging into the internals, but I figured you might've seen this before.

Related to #9.

Not a high priority for now, addresses with a ton of transactions are an edge case.

Related to #5.

@michliga already designed this, just need to make it work on the websocket.

Also, confirm it's working on static pages.

From email thread "Stealth Address?"

@matthieu would it be hard to add next_block (the hash) to this API call?

https://api.blockcypher.com/v1/btc/main/blocks/300000

If not I can do something hackey (height+1), but this will fail on the latest block. To solve that, I can either:

1. Make a separate API call to determine if this is the latest block (slow). Another solution here would be if you returned is_latest_block with the API call above.
2. Just always show it and then if you click it and it's more recent than we have, you get an error message "this is the latest block hash. Sorry we can't see into the future.". Kind of a bad UX.

Even for for coins like doge or lite.

Waiting on @matthieu to implement tx_hash filtering this weekend. See email thread "Websocket for updates on a transaction require an address?"

As-is, it's too skinny for even an address to fit the whole thing in it visibly.

Also, what about putting the cursor in there by default on every page (except for mobile users where that's going to annoyingly popout the keyboard)?

Not sure where the problem is occurring.

See: https://blockcypher.herokuapp.com/bcy/

No websocket, JS, or anything like that.

I prefer blockcypher.info because it's shorter and clear what it does (because of blockchain.info). live.blockcypher.com or explore.blockcypher.com are also good. @matthieu, time to pick a name! Would you please decide and assign back to me?

I've setup SSL certs a bunch so happy to take that part. We'll have to coordinate the domain purchase and/or access.

http://blockcypher.herokuapp.com/doge/tx/e4cf710d6887d06b0ef53185462a9c32bd77603482eb606af6614fa25a6b4311/

Much prettier with the new design on local:
http://cl.ly/image/2h3f363e1g0b

It could be even cooler if it was the logo and then when you click on that you get the full list.

http://cl.ly/image/053i0U2i1A1N

http://cl.ly/image/3m062n2u3S1I

Related to #64

Only if you agree.

I think this is the one I've used before:
http://www.himpfen.com/xl-button/

Sorry to push this without a logo, but since it's not "released" yet I figured no need to hold up the whole PR for the logo.

Related to #17.

https://live.blockcypher.com/doge/address/D7Y55r6Yoc1G8EECxkQ6SuSjTgGJJ7M6yD/

Related to #31

Here it is:

http://api.blockcypher.com/v1/doge/main

Assigning to @mflaxman for now, then @michliga can add a cute doggy coin.