<p>No. ASICs do only hash calculation. All data in block (except nonce) is defined by pool/node software</p>

CC BY-SA 3.0
2017-01-27T17:55:38.857Z
Hi @amaclin, then if I parse the transaction history using `bitcoin-abe`, what variable (or variables) in the generated database shall contain "pool/node"-specific information? Information at the pool/node level would still be valuable observable. Thank you!
llinfeng
CC BY-SA 3.0
2017-01-27T18:00:01.520Z
scriptSig of coinbase transaction
amaclin
CC BY-SA 3.0
2017-01-28T20:43:58.023Z
Or other things, like the type of payout transactions, or values in the coinbase nSequence. In general, you can only find out what pools/miners choose to reveal.
Pieter Wuille
CC BY-SA 3.0
2017-01-27T15:37:53.943Z
2017-01-27T16:50:08.033Z
2017-01-27T16:50:08.033Z
amaclin
<p>I have a research interest in understanding the spread of innovation, and the adoption of ASIC machines in the Bitcoin mining community is particularly relevant.</p>

<p>Does ASIC machines typically leave a trace in the blocks that they mined? Would a particular type of machine leave such trace/record/identifier in the transaction record?</p>

<transactions><blockchain><blockchain.info>
Does ASIC miners leave a trace in the mining history of bitcoin?
llinfeng
# Does ASIC miners leave a trace in the mining history of bitcoin?

(Asked by: username_0 on 2017-01-27)

I have a research interest in understanding the spread of innovation, and the adoption of ASIC machines in the Bitcoin mining community is particularly relevant.

Does ASIC machines typically leave a trace in the blocks that they mined? Would a particular type of machine leave such trace/record/identifier in the transaction record?

**Tags:** transactions, blockchain, blockchain.info


---

## 1 answers

### Answer by username_1 on 2017-01-27. Score: 2

No. ASICs do only hash calculation. All data in block (except nonce) is defined by pool/node software

> **Comments:**
> **username_0**: Hi @username_1, then if I parse the transaction history using `bitcoin-abe`, what variable (or variables) in the generated database shall contain "pool/node"-specific information? Information at the pool/node level would still be valuable observable. Thank you!  
> **username_1**: scriptSig of coinbase transaction  
> **username_2**: Or other things, like the type of payout transactions, or values in the coinbase nSequence. In general, you can only find out what pools/miners choose to reveal.  

---

