Bitcoin Protocol Rules
"Rules" yang digunakan oleh Bitcoin Client dalam memproses "message" dan mencegah dari adanya potensi "Unauthorized spending" dan "Double spending"
-snip-
*Reference Source https://en.bitcoin.it/wiki/Protocol_rulesPada bagian Catatan kaki yang berikut ini mungkin bisa diterjemahkan dan ditambahkan sekalian pada thread terjemahan agan sebagai catatan pelengkap dari beberapa poin yang tertera pada tulisan utama
Bitcoin Protocol Rules (seperti contoh pada ● "TX" Messages nomor 6 sedikitnya disana saya lihat ada 6 catatan kaki tambahan):
References
- nLockTime must not exceed 31 bits, as some clients will interpret it incorrectly
- A valid transaction requires at least 100 bytes. If it's any less, the transaction is not valid
- The number of signature operands in the signature (no, that is not redundant) for standard transactions will never exceed two
- Note that this is not a hard requirement on clients.
- Note that this is not a hard requirement on clients. The network-enforced rule is that only one transaction spending a particular output can be in the blockchain, thus preventing double-spending. Technically miners can choose which one they want to put into the block they're working on as long as no other transaction has spent that output either previously in the blockchain, or in the same block. The in-memory transaction pool can technically be managed in whatever way the miner is willing to implement.
- This is the protection against double-spending
- Note that when the transaction is accepted into the memory pool, an additional check is made to ensure that the coinbase value does not exceed the transaction fees plus the expected BTC value (25BTC as of this writing).
Oh ya, bagi teman-teman yang ingin berkontribusi pada Bitcoin Wiki bisa coba ikut gabung diskusi kesini:
-
https://bitcointalk.org/index.php?topic=5135411.0-
#bitcoin-wiki channel on freenode IRC