This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
dido:public:ra:xapend:xapend.a_glossary:m:miner [2021/08/11 10:47] murphy |
dido:public:ra:xapend:xapend.a_glossary:m:miner [2021/10/04 13:40] (current) 50.19.247.197 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Miner Node ===== | ===== Miner Node ===== | ||
| - | [[dido:public:ra:xapend:xapend.a_glossary| Return to Glossary ]] | + | [[dido:public:ra:xapend:xapend.a_glossary:start| Return to Glossary ]] |
| A **Miner Node** on creates blocks in the [[dido:public:ra:xapend:xapend.a_glossary:b:blockchain|blockchain]] which the [[dido:public:ra:xapend:xapend.a_glossary:n:node|nodes]] keep. Basically, the miner works on transactions by coming up with the best combination (hash) to store that information. In [[dido:public:ra:xapend:xapend.a_glossary:b:bitcoin|Bitcoin]], Miners spend about 10 minutes working on a problem, but nodes keep that result forever after in the database and verify it with others. Miners don't need to know about prior blocks (except for the prior one) with very few exceptions. | A **Miner Node** on creates blocks in the [[dido:public:ra:xapend:xapend.a_glossary:b:blockchain|blockchain]] which the [[dido:public:ra:xapend:xapend.a_glossary:n:node|nodes]] keep. Basically, the miner works on transactions by coming up with the best combination (hash) to store that information. In [[dido:public:ra:xapend:xapend.a_glossary:b:bitcoin|Bitcoin]], Miners spend about 10 minutes working on a problem, but nodes keep that result forever after in the database and verify it with others. Miners don't need to know about prior blocks (except for the prior one) with very few exceptions. | ||