=======Block Header=======
00000020 version
a15e218f5f158a31053ea101b917a6113c807f6bcdc85a000000000000000000 previous block header hash
cc7cf9eab23c2eae050377375666cd7862c1dfeb81abd3198c3a3f8e045d9148 merkle root hash
4a39225a time = 1512192330 = Saturday, December 2, 2017 5:25:30 AM
f6d00018 nBits = 402706678
659e5e8a nonce = 2321456741
=====================

01 tx count = 1 (aka Coinbase transaction)

=======Transactions in the block=======
01000000 version
01 tx_in count
0000000000000000000000000000000000000000000000000000000000000000 previous_output
ffffffff index for coinbase tx is 0xffffffff
64 script bytes = 100
03009607 op_3 (bytes in height) + height 497152
2cfabe6d6d08d1c2f6d904f4e1cd10c6558f8e5aed5d6a89c43bb22862464ebb819dd8813404000 000f09f909f104d696e6564206279206a6f73656d73720000000000000000000000000000000000 0000000000000000000000000000000000 arbitrary coinbase script
7f060000 sequence = 1663
01 tx_out count
807c814a00000000 amount = 1250000000
19 76 a9 14 c825a1ecf2a6830c4401620c3a16f1995057c2ab 88 ac P2PKH script
efebcf38 Lock time = 953150447 = Wednesday, March 15, 2000 8:00:47 PM

Note: The hashes are in internal byte order; the other values are all in little-endian order.
Read more: https://bitcoin.org/en/developer-reference#block-chain

Yes, this is just source code. You need to use a compiler to do the rest.
I can add binaries to the Releases part of the repository if there were enough interest. Although I prefer not to...

Never seen this one before
https://bitcointalk.org/index.php?action=profile;u=1323162

Only 100,000 possibilities if we assume it is only numbers (coordinate) or 1,048,576 if not! Only if I knew how ethereum key pairs work and weren't too lazy to learn it would have been 5 seconds of brute force


hmmm! It is a hexadecimal string, all the characters seem valid to me.

Just a little correction
Oct 3, 2015

2 weeks, still not changed.

Aww man, why ethereum...

47-----b5acf3d595e--6b39fb1daeaae091ac50d9d3d1b03273228c84d3de6f

It is open source so you can just check it out. I am no expert in Java but it seems like it only takes a file containing addresses each in 1 line so you can not import .csv file.

Also it seems like it is using blockr.io, and that website/API no longer exists.

I'm not sure how these Ethereum APIs work and how they are different, but these block explorers usually have an actual API service that you can use. Blockdozer for example is based on Insight API, which as you guessed is powered by the same open source project. They just didn't make a documentation page.
Blocktrail: https://www.blocktrail.com/api/docs has both BTC and BCH

And you will have a better luck finding them for bitcoin:
Blockchain.info: https://blockchain.info/api
BlockCypher: https://www.blockcypher.com/dev/bitcoin/
smartbit: https://www.smartbit.com.au/api
and lots more.

Look closely, usually at the bottom of the page. You can always use your browser search function (Ctrl+F) to search for the word "API", you will find the link. Most of the block explorers do have an API.

If you still couldn't find it, say for what coin and which block explorer so I can post the direct link here for you!

In case you missed it, I am talking about these new forks that are coming out these days like bitcoin gold for example. And as they are creating a new fork, a new coin with a new client and new way of transactions, that client knows this.

As for that "flag", you can change the place of it. Put it at the end, after Sequence if you think it can cause any issues (not yet 100% familiar with SegWit )

I've been reading more about "Replay Protection" and how these forks are having trouble with it, some claiming the Sighash_forkID is hard to implement and is complicated to implement, so I was thinking there can be a much simpler way of implementing such protection.

Idea:
Add a new variable to transaction to indicate this is a transaction belonging to chain_x (bitcoin whatever chain).
For example it can be a 1 byte variable before version. Let's call it Fork_Flag

Example:
bitcoin transaction: bitcoin fork transaction:
Since when a transaction is being signed, everything is signed, the signature of said transaction will be different. So an attacker can't just remove the first byte and "replay" that tx on bitcoin network, the signature will be invalid then.

Benefit:
- Easy to implement
- Also if a bitcoin node receives this transaction it does not have to verify the signature to know it is invalid which means not wasting CPU power. A quick look tells the node that this transaction is invalid.

---

So, will this work, or am I missing something here? Is there any downside to it?

Technically you can automate the google spreadsheet too. Check out how you can parse JSON into a sheet.

For bittrex: https://bittrex.com/api/v1.1/public/getcurrencies use your browser search function (Ctrl+F) to find MinConfirmation.

For Polonix: https://poloniex.com/public?command=returnCurrencies same but search for minConf

FunFact #1
You can use http://www.convertcsv.com/json-to-csv.htm to export the JSON result in .CSV or excel file and have it more like a "list"

FunFact #2
You can visit the links above with latest version of Firefox. It has a JSON parser which will make it pretty (more human readable) and you can also filter the results.

No, your mistake is treating the public key (the hex above starting with 0450...) as a String. But it is a hex.
If you perform SHA256 on it as a string you get the different result which is wrong (3251...). But when you treat it as a Hex, you get the correct result.

Here is an online tool which you can use:
http://www.fileformat.info/tool/hash.htm?hex=0450863AD64A87AE8A2FE83C1AF1A8403CB53F53E486D8511DAD8A04887E5B23522CD470243453A299FA9E77237716103ABC11A1DF38855ED6F2EE187E9C582BA6

If you type the public key hex in the string text box on the top of that page you get the wrong result.

I did not know this. I have always used the API

I am using https://www.blockr.io/ API a lot but recently I noticed when I make a call I get an error and visiting the site redirects me to coinbase.com!

Does anyone know what happened to them?

Same here, that's why I created my Watch-Only wallet

I am not familiar with JavaScript and your code seems to not be formatted properly and it lacks documentation also. But the only http API call that I could find belonged to "blockdozer" which you are using for bitcoin and bitcoin cash. You can use any of these: https://bitcoin.stackexchange.com/a/57449

I do understand the possible risks/vulnerabilities and the reason for removal of that alert system, but I still feel a void.

I was talking about a "replacement", a new alert system if you will that sends alerts with codes not texts. A set of predefined codes can be set, each meaning something different. I don't know, something like Code_1 = Hard Fork is going on, or Code_2 = A critical Bug were found Check trusted sources for more info.

I just said that name because that was the one off the top of my mind. Not sure where the FUD comes in!

My point is if you think X & Y & Z having alert keys of possibly a modified/improved alert system like what i said above (which in practice alerts people using their code of critical issues in their code) makes it centralized, then you should also think X & Y & Z having commit access to bitcoin core GitHub repo also makes it centralized!