Bitcoin As A State Transition System From a technical standpoint, the ledger of a cryptocurrency | Address 0xa291aCAf4a8fE16A5b1F15c6d6004fa3aB7f58ca Details - Ethereum

Bitcoin As A State Transition System From a technical standpoint, the ledger of a cryptocurrency

Contract Overview

Balance:

0 ETH

ETH Value:

$0.00(@ $3,487.41/ETH)

Token:

More Info

Tag:

Not Available. Update?

Contract Creator:

0x6dC08...D64811at txn0xa80f6...40f863

Token Tracker:

Bitcoin As A State Transition System \n \n From a technical standpoint, the ledger of a cryptocurrency such as Bitcoin can be thought of as a state transition system, where there is a *state* consisting of the ownership status of all existing bitcoins and a *state transition function* that takes a state and a transaction and outputs a new state which is the result. In a standard banking system, for example, the state is a balance sheet, a transaction is a request to move $X from A to B, and the state transition function reduces the value in A's account by $X and increases the value in B's account by $X. If A's account has less than $X in the first place, the state transition function returns an error. Hence, one can formally define: \n The *state* in Bitcoin is the collection of all coins (technically, *unspent transaction outputs* or UTXO) that have been minted and not yet spent, with each UTXO having a denomination and an owner (defined by a 20-byte address which is essentially a cryptographic public keyfn1). A transaction contains one or more inputs, with each input containing a reference to an existing UTXO and a cryptographic signature produced by the private key associated with the owner's address, and one or more outputs, with each output containing a new UTXO to be added to the state. The state transition function APPLY(S,TX) -> S' can be defined roughly as follows: For each input in TX: If the referenced UTXO is not in S, return an error. If the provided signature does not match the owner of the UTXO, return an error. If the sum of the denominations of all input UTXO is less than the sum of the denominations of all output UTXO, return an error. Return S with all input UTXO removed and all output UTXO added The first half of the first step prevents transaction senders from spending coins that do not exist, the second half of the first step prevents transaction senders from spending other people's coins, and the second step enforces conservation of value. In order to use this for payment, the protocol is as follows. Suppose Alice wants to send 11.7 BTC to Bob. First, Alice will look for a set of available UTXO that she owns that totals up to at least 11.7 BTC. Realistically, Alice will not be able to get exactly 11.7 BTC; say that the smallest she can get is 6+4+2=12. She then creates a transaction with those three inputs and two outputs. The first output will be 11.7 BTC with Bob's address as its owner, and the second output will be the remaining 0.3 BTC *change*, with the owner being Alice herself. \n \n Mining \n \n If we had access to a trustworthy centralized service, this system would be trivial to implement; it could simply be coded exactly as described, using a centralized server's hard drive to keep track of the state. However, with Bitcoin we are trying to build a decentralized currency system, so we will need to combine the state transaction system with a consensus system in order to ensure that everyone agrees on the order of transactions. Bitcoin's decentralized consensus process requires nodes in the network to continuously attempt to produce packages of transactions called *blocks*. The network is intended to produce roughly one block every ten minutes, with each block containing a timestamp, a nonce, a reference to (ie. hash of) the previous block and a list of all of the transactions that have taken place since the previous block. Over time, this creates a persistent, ever-growing, *blockchain* that constantly updates to represent the latest state of the Bitcoin ledger. The algorithm for checking if a block is valid, expressed in this paradigm, is as follows: Check if the previous block referenced by the block exists and is valid. Check that the timestamp of the block is greater than that of the previous blockfn2 and less than 2 hours into the future Check that the proof-of-work on the block is valid. Let S[0] be the state at the end of the previous block. Suppose TX is the block's transaction list with n transactions. For all i in 0...n-1, set S[i+1] = APPLY(S[i],TX[i]) If any application returns an error, exit and return false. Return true, and register S[n] as the state at the end of this block. Essentially, each transaction in the block must provide a valid state transition from what was the canonical state before the transaction was executed to some new state. Note that the state is not encoded in the block in any way; it is purely an abstraction to be remembered by the validating node and can only be (securely) computed for any block by starting from the genesis state and sequentially applying every transaction in every block. Additionally, note that the order in which the miner includes transactions into the block matters; if there are two transactions A and B in a block such that B spends a UTXO created by A, then the block will be valid if A comes before B but not otherwise. The one validity condition present in the above list that is not found in other systems is the requirement for *proof-of-work*. The precise condition is that the double-SHA256 hash of every block, treated as a 256-bit number, must be less than a dynamically adjusted target, which as of the time of this writing is approximately 2187. The purpose of this is to make block creation computationally *hard*, thereby preventing sybil attackers from remaking the entire blockchain in their favor. Because SHA256 is designed to be a completely unpredictable pseudorandom function, the only way to create a valid block is simply trial and error, repeatedly incrementing the nonce and seeing if the new hash matches. At the current target of ~2187, the network must make an average of ~269 tries before a valid block is found; in general, the target is recalibrated by the network every 2016 blocks so that on average a new block is produced by some node in the network every ten minutes. In order to compensate miners for this computational work, the miner of every block is entitled to include a transaction giving themselves 25 BTC out of nowhere. Additionally, if any transaction has a higher total denomination in its inputs than in its outputs, the difference also goes to the miner as a *transaction fee*. Incidentally, this is also the only mechanism by which BTC are issued; the genesis state contained no coins at all. In order to better understand the purpose of mining, let us examine what happens in the event of a malicious attacker. Since Bitcoin's underlying cryptography is known to be secure, the attacker will target the one part of the Bitcoin system that is not protected by cryptography directly: the order of transactions. The attacker's strategy is simple: Send 100 BTC to a merchant in exchange for some product (preferably a rapid-delivery digital good) ait for the delivery of the product Produce another transaction sending the same 100 BTC to himself Try to convince the network that his transaction to himself was the one that came first. Once step (1) has taken place, after a few minutes some miner will include the transaction in a block, say block number 270000. After about one hour, five more blocks will have been added to the chain after that block, with each of those blocks indirectly pointing to the transaction and thus *confirming* it. At this point, the merchant will accept the payment as finalized and deliver the product; since we are assuming this is a digital good, delivery is instant. Now, the attacker creates another transaction sending the 100 BTC to himself. If the attacker simply releases it into the wild, the transaction will not be processed; miners will attempt to run APPLY(S,TX) and notice that TX consumes a UTXO which is no longer in the state. So instead, the attacker creates a *fork* of the blockchain, starting by mining another version of block 270000 pointing to the same block 269999 as a parent but with the new transaction in place of the old one. Because the block data is different, this requires redoing the proof-of-work. Furthermore, the attacker's new version of block 270000 has a different hash, so the original blocks 270001 to 270005 do not *point* to it; thus, the original chain and the attacker's new chain are completely separate. The rule is that in a fork the longest blockchain is taken to be the truth, and so legitimate miners will work on the 270005 chain while the attacker alone is working on the 270000 chain. In order for the attacker to make his blockchain the longest, he would need to have more computational power than the rest of the network combined in order to catch up (hence, *51% attack*). (GENESIS) (@ $0.000023)

Parent Txn Hash

Block

From

To

Value

Age

0x16328...95eae5

0xa547c...B51Ac7

0xa291a...7f58ca

0 ETH

414 days 14 hrs ago

0x5749a...084d14

0xa547c...B51Ac7

0xa291a...7f58ca

0 ETH

464 days 10 hrs ago

0x759b5...ccb11b

0x7a250...F2488D

0xa291a...7f58ca

0 ETH

464 days 10 hrs ago

0x759b5...ccb11b

0x7a250...F2488D

0xa291a...7f58ca

0 ETH

464 days 10 hrs ago

0x759b5...ccb11b

0xa291a...7f58ca

0x7a250...F2488D

0 ETH

464 days 10 hrs ago

0x759b5...ccb11b

0xa291a...7f58ca

0x7a250...F2488D

0 ETH

464 days 10 hrs ago

0x759b5...ccb11b

0x7a250...F2488D

0xa291a...7f58ca

0 ETH

464 days 10 hrs ago

0x91dfb...bf35f2

0x7a250...F2488D

0xa291a...7f58ca

0 ETH

464 days 10 hrs ago

0x91dfb...bf35f2

0x7a250...F2488D

0xa291a...7f58ca

0 ETH

464 days 10 hrs ago

0x91dfb...bf35f2

0xa291a...7f58ca

0x7a250...F2488D

0 ETH

464 days 10 hrs ago

0x91dfb...bf35f2

0xa291a...7f58ca

0x7a250...F2488D

0 ETH

464 days 10 hrs ago

0x91dfb...bf35f2

0x7a250...F2488D

0xa291a...7f58ca

0 ETH

464 days 10 hrs ago

0xd458e...9170c9

0x7a250...F2488D

0xa291a...7f58ca

0 ETH

464 days 10 hrs ago

0xd458e...9170c9

0x7a250...F2488D

0xa291a...7f58ca

0 ETH

464 days 10 hrs ago

0xd458e...9170c9

0xcF04d...8a7608

0xa291a...7f58ca

0 ETH

464 days 10 hrs ago

0xd458e...9170c9

0xcF04d...8a7608

0xa291a...7f58ca

0 ETH

464 days 10 hrs ago

0xd458e...9170c9

0xcF04d...8a7608

0xa291a...7f58ca

0 ETH

464 days 10 hrs ago

0x89f53...3890dc

0xcF04d...8a7608

0xa291a...7f58ca

0 ETH

464 days 10 hrs ago

0x89f53...3890dc

0xC6265...3ba277

0xa291a...7f58ca

0 ETH

464 days 10 hrs ago

0x89f53...3890dc

0xa291a...7f58ca

0x6dC08...D64811

0.02139838563390344 ETH

464 days 10 hrs ago

0x89f53...3890dc

0x7a250...F2488D

0xa291a...7f58ca

0.02139838563390344 ETH

464 days 10 hrs ago

0x89f53...3890dc

0xcF04d...8a7608

0xa291a...7f58ca

0 ETH

464 days 10 hrs ago

0x89f53...3890dc

0x7a250...F2488D

0xa291a...7f58ca

0 ETH

464 days 10 hrs ago

0x89f53...3890dc

0x7a250...F2488D

0xa291a...7f58ca

0 ETH

464 days 10 hrs ago

0x89f53...3890dc

0xa291a...7f58ca

0x7a250...F2488D

0 ETH

464 days 10 hrs ago

0x89f53...3890dc

0xa291a...7f58ca

0x7a250...F2488D

0 ETH

464 days 10 hrs ago

0x89f53...3890dc

0x5200a...e1847a

0xa291a...7f58ca

0 ETH

464 days 10 hrs ago

0x89f53...3890dc

0xdB588...D23216

0xa291a...7f58ca

0 ETH

464 days 10 hrs ago

0x7c005...99dc69

0xcF04d...8a7608

0xa291a...7f58ca

0 ETH

464 days 11 hrs ago

0x7c005...99dc69

0x3fC91...2b7FAD

0xa291a...7f58ca

0 ETH

464 days 11 hrs ago

0x7c005...99dc69

0xa291a...7f58ca

0x6dC08...D64811

0.02319841189659827 ETH

464 days 11 hrs ago

0x7c005...99dc69

0x7a250...F2488D

0xa291a...7f58ca

0.02319841189659827 ETH

464 days 11 hrs ago

0x7c005...99dc69

0xcF04d...8a7608

0xa291a...7f58ca

0 ETH

464 days 11 hrs ago

0x7c005...99dc69

0x7a250...F2488D

0xa291a...7f58ca

0 ETH

464 days 11 hrs ago

0x7c005...99dc69

0x7a250...F2488D

0xa291a...7f58ca

0 ETH

464 days 11 hrs ago

0x7c005...99dc69

0xa291a...7f58ca

0x7a250...F2488D

0 ETH

464 days 11 hrs ago

0x7c005...99dc69

0xa291a...7f58ca

0x7a250...F2488D

0 ETH

464 days 11 hrs ago

0x7c005...99dc69

0x00000...C78BA3

0xa291a...7f58ca

0 ETH

464 days 11 hrs ago

0x2462d...2b30a2

0xc5bab...325DE4

0xa291a...7f58ca

0 ETH

464 days 11 hrs ago

0x59a6e...edd081

0x3fC91...2b7FAD

0xa291a...7f58ca

0 ETH

464 days 11 hrs ago

0x59a6e...edd081

0xcF04d...8a7608

0xa291a...7f58ca

0 ETH

464 days 11 hrs ago

0x59a6e...edd081

0xcF04d...8a7608

0xa291a...7f58ca

0 ETH

464 days 11 hrs ago

0x59a6e...edd081

0x3fC91...2b7FAD

0xa291a...7f58ca

0 ETH

464 days 11 hrs ago

0x26b41...e57d52

0x3fC91...2b7FAD

0xa291a...7f58ca

0 ETH

464 days 11 hrs ago

0x26b41...e57d52

0xcF04d...8a7608

0xa291a...7f58ca

0 ETH

464 days 11 hrs ago

0x26b41...e57d52

0xcF04d...8a7608

0xa291a...7f58ca

0 ETH

464 days 11 hrs ago

0x26b41...e57d52

0x3fC91...2b7FAD

0xa291a...7f58ca

0 ETH

464 days 11 hrs ago

0xf77dc...e6b3bc

0x3fC91...2b7FAD

0xa291a...7f58ca

0 ETH

464 days 11 hrs ago

0xf77dc...e6b3bc

0xcF04d...8a7608

0xa291a...7f58ca

0 ETH

464 days 11 hrs ago

0xf77dc...e6b3bc

0xcF04d...8a7608

0xa291a...7f58ca

0 ETH

464 days 11 hrs ago

Loading