HASH

Umpire_State_Bldg

Look at figure 4-1. Public key 'K' is derived from private key 'k' using elliptic curve math. The Bitcoin Address is the HASH of the public key.

v1n1btt

>mining on my gpu making some nice cash Did you mean making some NICE HASH?

igadjeed

This P2Pkh address 1Q2j9rxQcxeE1hSbgp4U7myMkJhqtvPuo5 is this TXO script OP_DUP OP_HASH160 OP_PUSHBYTES_20 fc9e7f11554a3fc6aead003445c57bf08f88d0ee OP_EQUALVERIFY OP_CHECKSIG The address is thebase58 representation of the 20-byte hash in the TXO, with a 4-byte checksum appended and a 1-byte network identifier prepended. That is fc9e7f11554a3fc6aead003445c57bf08f88d0ee is the same as 1Q2j9rxQcxeE1hSbgp4U7myMkJhqtvPuo5 To recover this address from a seed phrase, the recovery wallet needs to know the addresses are P2PKH. That's the first thing a recovery function would try, if it was using trial-and-error. This derivation path is commonly represented as 0 or 44 This P2SH address 34dDKqPSRZQTeyAWMk1TuYGAcwS7YDJqRn is this TXO script OP_HASH160 OP_PUSHBYTES_20 20303b26b2cf52da552c4b7dccd97fa8c5cb83bd OP_EQUAL Simple, right? The address is thebase58 representation of the 20-byte hash in the TXO, with a 4-byte checksum appended and a 1-byte network identifier prepended. That is 20303b26b2cf52da552c4b7dccd97fa8c5cb83bd is the same as 34dDKqPSRZQTeyAWMk1TuYGAcwS7YDJqRn P2PKH prefix is '0'. P2SH prefix is '5' PKH means public key hash. SH means script hash To recover a P2SH wallet, the recovery wallet needs to know the exact script which was hashed to create the TXO address

igadjeed

Reverse is the wrong term The Bitcoin network, because of the reality of physics, has latency. This means that it is possible for 2 different miners to release a block at the same time (near enough to the same time) to the node network. This happens roughly 10 times per year When there is a tied mining race, the node network has a 1-block chain tip fork. But every node is independent, which means that no node is aware that some other nodes are now following a slightly different chain When the next block arrives, it is mined by a miner whose node followed one or other side of the tied mining fork (previous block). Nodes on the other side of the fork are unable to add this new block to their chains because of a mismatch in PREV_BLOCK_HASH, the piece which links the entire chain from most recent block back to genesis The nodes on the "losing" side of the fork resolve this mismatch by requesting their peer nodes to send the previous block which fits the new block. This is called a chain tip reorg. It's common to read that Bitcoin "follows the longest chain" Thus, in the expectation of a 1-block chain tip fork caused by a tied mining race, we should expect to wait 2 confirmations before being certain that a transaction exists on the blockchain Note: there's no reversal. From the blockchain point of view, there is only the longest chain. A block which existed in a temporary 1-block tip fork no longer exists. Its transactions weren't reversed. They just don't exist (even though they obviously existed temporarily) Occasionally, there are 2 tied mining races in a row. The software is not limited to 1-block tip reorgs. In fact there is no limit to the depth of a chain tip reorg So, in anticipation of 2 tied mining races in a row, and a 2-block tip reorg, we should wait 3 confirmations Occasionally, a tip reorg is re-reorged, switching the longest chain back to the chain which had previously been reorged as he shorter chain. The mining conditions which might cause this are fairly simple, but not simple to put into words. These incidents are uncommon So, if you're super-cautious you might anticipate a 2-block reorg followed by a 2-block re-reorg. At this point I've lost my ability to count, but I think it means waiting either 3 confirmations or 4 confirmations I think 6 confirmations is over-cautious. I'm not sure where it originated. I've seen suggestions it was recommended by Satoshi, but a quick read of Satoshi Nov-2008 indicates he recommended 2 confirmations https://www.metzdowd.com/pipermail/cryptography/2008-November/014832.html > The recipient just needs to verify it back to a depth that is sufficiently far back in the block chain, which will often only require a depth of 2 transactions I think this might actually mean tracking transaction backlinks, not block confirmations In the same message ... > Receivers of transactions will normally need to hold transactions for perhaps an hour or more to allow time for this kind of possibility to be resolved It would be reasonable to interpret "an hour" as 6 confirmations

opreturn_net

You would need to know the redeemscript that was used to build your p2sh address. p2sh addresses are structured like this: OP\_HASH160 <redeemscripthash> OP\_EQUAL To spend, your scriptsig might look like this for a p2pkh wrapped in p2sh: <signature> <pubkey> <redeemscript>, but multisig and other complex scripts can be different, so you need the redeemscript to know what to put in your scriptsig.

coinfeeds-bot

tldr; Crypto ETFs have reached a total asset value of $4.5 billion, according to a recent report. The study shows that crypto ETFs account for 9 of the top 25 ETPs, with COINXBT and COINETH being the top crypto ETNs by assets, and HASH11 being the leading crypto ETF. Bitcoin and Ethereum are the most popular cryptocurrencies among traditional finance investors, with almost 80% of ETPs focusing on BTC and ETH. While there are still pending crypto ETF approvals, there are already several existing ones with a significant amount of assets. *This summary is auto generated by a bot and not meant to replace reading the original article. As always, DYOR.

iMHackeRPiratE

> Imagine mining BTC with Minecraft someone tried but 1.11 HASH/SEC : https://www.youtube.com/watch?v=sLClfQdmzPw

igadjeed

"The network" has no knowledge in itself. Each node operator chooses which set of consensus rules apply to the blockchain stored on his own node. There is no guarantee that all the nodes your own node is connected to have the same copy of the blockchain The network converges to consensus (the same history on every node) * because verification of a block is binary. The block is good or bad, never partially good. If a node verifies a block (including all transactions) as valid, it adds the block to its blockchain and propagates the block to its neighbor nodes. If the block is bad, the node does not add it to its blockchain, and does not propagate it * because every block is linked to the previous block. When a node receives a new block, it can not add the block to its chain unless the block's PREV_BLOCK_HASH is identical to the previous block's header hash If a rogue node, or a group of nodes with different consensus rules exists on the network, they're welcome to connect to any node. The network is open, with no authentication requirement. But their different consensus rules cause either of these two conditions * the rogues accept a block which the standard consensus rules reject * the rogues reject a block which the standard consensus rules accept In the first case, the rogue node adds a block to its chain, sends the block to neighbor nodes. The neighbor nodes all reject the block. This makes a fork, in that the block at the tip of the rogue nodes' chain does not exist in the other nodes' chain. A miner creates the next block. This block has a PREV_BLOCK_HASH matching the tip block of the regular nodes. The rogue nodes can not use this block to extend their chain. It follows that the rogue nodes' chain can never be extended. But if the miner is on the rogue side of the network, the rogue nodes' chain tip is now 2 blocks longer. If there are miners on both sides, the rogue miners make blocks which extend the rogue nodes' chains, and the regular miners make blocks which extend the regular nodes' chains. Who decides rogue vs regular. Obviously I do, because I choose those two words prejudicially. In practice, Bitcoin makes no value judgments In the second case, the rogue nodes reject valid blocks and do not extend their chains. Again, if there are some miners following the same consensus rules as the rogue nodes, there is no objective way to choose one chain as regular and the other chain as rogue Important: the longest chain rule applies where a temporary chain tip fork has occurred by chance, among nodes with identical consensus rules. This rule can not be used to resolve a chain fork caused by variant consensus rules Most important is the practical problem of making a transaction - Bitcoin's only purpose. Nodes and miners can fork into separate chains with different consensus rules, and a node only cares that its own chain is consistent with its own consensus rules. Now, I want to send Bitcoin to the company which provides my VPN service. This transaction will work if both my node and the VPN company's node have exactly the same blockchain. If one of us has forked to a separate chain, I can not make the purchase Expand this one transaction to the 40,000 similar transactions every day. It is evident that the merchants and customers have a common interest in their nodes having the same blockchain. So there is no incentive for any node operator to experiment with different consensus rules, either alone or in conspiracy with other nodes and miners The above mechanics, and the social motivations, ensure that Bitcoin nodes converge to the same blockchain, even though every node is operated independently

igadjeed

There's no voting, no majority. The Bitcoin node network is open. There is no way to authenticate a node. Nodes can not be counted. Bitcoin consensus emerges through every node verifying every block independently That is, I know my node has correctly validated every block in my copy of the blockchain, and I don't know whether any other node has the same blockchain If I need to purchase something using Bitcoin, the purchase transaction can only work if my node and the merchant's node have the same transaction history. Extrapolate from this to every transaction sent by anybody, and it follows that Bitcoin can only work if every node has the same blockchain ###The mechanism * Each node relies on its own consensus rules * Each block is locked up by the Merkle tree of transaction hashes, storing the Merkle root hash in the block header * The blockchain is locked up by storing the previous block's header hash in each block's header (that's why it's called a chain) * When a miner wins the race to publish a new block, he sends the new block to one or more nodes. Nodes do not trust miners. Each of those nodes applies the consensus rules. This verification is comprehensive - block header hash, each block header field, every transaction checked for no double spending, every transaction checked for valid signatures. If there are no errors, the node sends the block to his peers (124 nodes he's connected to). Nodes do not trust nodes. Each of the peer nodes applies the consensus rules. If the block or any of the block's transactions have any errors, the block is not added to the node's blockchain, and the block is not propagated to other nodes. This process - a node propagates the new block **only if it has no errors** - is the main reason that nodes converge to the same blockchain even though every node is independent * It follows that nodes with different consensus rules are not participating because their different rules * either prevent them from accepting a valid block * or cause them to send an invalid block to their peer nodes, and those peers do not propagate those blocks Rogue nodes are permitted to participate in the network, but they're unable to extend their chains because each new block has a PREV_BLOCK_HASH which fails to match the rogue node's chain tip block's header hash > Do all full nodes need to confirm that the block and its content is valid or do we need only a majority of them to do so? Only your own node needs to confirm that each block and all transactions are valid

igadjeed

> the transaction that funded your 0.5BTC wallet has a timelock of 0, so there should be no problem spending this UTXO CLTV encumbers the TXO. This TXO is a scripthash ... OP_HASH160 54a1df7be7557e2fd2f65ca45ff541ee363a0085 OP_EQUAL == 39QWbnkbcPFcrJFEB6yvVDc12eX5zqVt3y We don't get to see the script until the TXO gets spent. OP has provided this script in the rejected spending txinput 7140000 OP_CHECKLOCKTIMEVERIFY OP_DROP 045332b5e3bcaeef3a062b49d5129ac21017d369e9c52c2f12c472d8d6236e2f5116b580dd1f99fd9b321d9207c9a512f301c263bd58238dbbebf469675e09a2b2 OP_CHECKSIG Let's assume that script hashes to *54a1df7be7557e2fd2f65ca45ff541ee363a0085* Maybe a more diligent person can check According to https://en.bitcoin.it/wiki/Timelock > When the CLTV opcode is called, it will cause the script to fail unless the nLockTime on the transaction is equal to or greater than the time parameter provided to the CLTV opcode. Since a transaction may only be included in a valid block if its nLockTime is in the past, this ensures the CLTV-based timelock has expired before the transaction may be included in a valid block And you said this > you’ve locked it up until block 7,140,000 Which appears to be the correct answer For completeness If the OP used 714,000, then the tx locktime needs to be less than current block and greater-or-equal 714,000. It shouldn't be 0 The GitHub link applies to transactions which have been rejected for relay because of a future locktime. It describes using a tx to spend one of the timelocked tx's UTXOs. This works because the timelocked TX is waiting in someone's wallet, not yet confirmed on the blockchain But the OP funded a scripthash address on the blockchain. The CLTV op is in the script. The timelocked TXO is already on the blockchain

igadjeed

See chapter 10 in Antonopoulos for a nice diagram and explanation https://github.com/bitcoinbook/bitcoinbook/blob/develop/ch10.asciidoc > What happens if chain A "wins" You node sees that its chain can't be extended because there is a mismatch in PREV_BLOCK_HASH. In your example, this mismatch happens in block 6. The prevhash in block 6 matches the block 5 hash in chain A Now your node knows it needs to get a replacement block 5 from another node. When this arrives, it also has a mismatching prevhash, and so on until your node has collected all 5 blocks from the tip of chain A Your node makes your 5-block chain B tip stale, and performs a tip reorg to follow chain A > My transaction will turn “unsent” and back to the mempool A Core node will add your unconfirmed transaction back into its mempool (but not necessarily). In Chain A nodes, it was always in the mempool, unless it was confirmed in Chain A block 2, 3, 4, 5 or 6 Note that mempool management and anything to do with unconfirmed transactions are not part of Bitcoin consensus. Consensus only applies to transactions which are in confirmed blocks. Your transaction's status changed from confirmed to unconfirmed, even if it's not in any mempool after the tip reorg > back to my address Bitcoin doesn't work that way. An unconfirmed transaction does not leave your wallet. There's nothing to return > Do I have to pay the mining fees again You didn't pay them because your transaction is not in the longest chain > the miners of chain B will still keep their rewards Coinbase transaction outputs (rewards) can not be spent for 100 blocks. If a chain tip reorg was more than 100 blocks long, life would be very interesting

StrawGreeter

> Does your segwit address exist on the blockchain separately from your legacy address? Only transactions exist on the blockchain. An address only exists as part of a transaction output > it lacks segwit support It's not really a wallet then > Are they not stored at the same address on the block chain? Legacy OP_DUP OP_HASH160 OP_PUSHBYTES_20 a95f25d1897e3438d6056f2e0cf1c8153ea94ae7 OP_EQUALVERIFY OP_CHECKSIG SegWit OP_0 OP_PUSHBYTES_20 a95f25d1897e3438d6056f2e0cf1c8153ea94ae7 Same RIPEMD160 hash. Not the same address. Can be spent with the same private key (very carefully)

plxmtreee

Around the same time VeChain reached ATH, I bought some VET along with other blockchain supply chain management tokens like Provenance (HASH) and Morpheus Network (MNW)- made a profit on these but never on my VET tokens. My MNW is still in the green in spite of the bear markets that followed!

pwuille

Can you paste the result of `getchaintips` RPC? It'll tell us whether your node just hasn't learned about more blocks, never received their data, or incorrectly determined a block is invalid. If it's considered invalid, you can try `reconsiderblock HASH`, with HASH equal to the hash of the first block that your node seems to not accept. This will make it re-validate it instead of trusting previously cached validity information. However, it's unlikely this will fix things - the most common cause is due to CPU/memory/disk faults causing corruption of the database, meaning you'll need a full reindex from scratch to recover.

diomediocre

I always shill Cosmos and their SDK/Tendermint/IBC modules but if you like appchains at all Avalanche, Dotsama, and Near/Octopus all seem to have great underlying tech, systems, and documentation. All have minor issues but solid foundations to work from. Chainlink Labs is one of the most important teams in all of crypto even though you wouldn't know it by their token's use or price. The DAG over blockchain discussion doesn't happen much anymore but XNO/IOTA/FTM/HASH have all been plugging away at it and gradually improving their products. New alt in the space KAS which I don't know very well. From what I understand of the documentation, which admittedly isn't much, XMR is god tier in the privacy space. Time after txs seems to be the only vulnerability of their system.

Filipehdbr

script\_code = Script(\['OP\_DUP', 'OP\_HASH160', addrs\_for\_script.to\_hash160(), 'OP\_EQUALVERIFY', 'OP\_CHECKSIG'\])

warpanomaly

Thank you so much for the work! I appreciate it. Your script worked except I still needed add the OP codes in the script_code: ``` script_code = Script(['OP_DUP', 'OP_HASH160', addrs_for_script.to_hash160(), 'OP_EQUALVERIFY', 'OP_CHECKSIG']) ``` If I took out 'OP_DUP', 'OP_HASH160', 'OP_EQUALVERIFY', or 'OP_CHECKSIG' I got this error: Signature must be zero for failed CHECK(MULTI)SIG operation.

Filipehdbr

The code you've provided is quite efficient for creating a Bitcoin native SegWit transaction with an OP\_RETURN message. However, there are a few optimizations and improvements you can make: Remove unnecessary imports: In your code, you've imported addr\_non\_seg, but it's not used anywhere. You can remove this line: addr\_non\_seg = recPrivKey.get\_public\_key().get\_address() Remove the unnecessary script code and signing flags: The 'OP\_DUP', 'OP\_HASH160', 'OP\_EQUALVERIFY', 'OP\_CHECKSIG' opcodes are necessary for P2PKH (Pay-to-Public-Key-Hash) transactions. However, you're creating a P2WPKH (Pay-to-Witness-Public-Key-Hash) transaction, which uses a different script. The script code for signing P2WPKH transactions is the public key hash (PKH) itself. You can simplify the script code as follows: script\_code = addrs\_for\_script.to\_hash160() For SegWit transactions, you don't need to use the SIGHASH\_ANYONECANPAY flag, as it's generally used for non-SegWit transactions when you want to allow others to add inputs to the transaction. You can remove it from your signing process: txsign1 = priv.sign\_segwit\_input(tx, 0, script\_code, to\_satoshis(0.00032557), SIGHASH\_ALL) Use more descriptive variable names: Using more descriptive variable names can make your code easier to understand and maintain. For example, you could replace priv with sender\_priv\_key, pub with sender\_pub\_key, recPrivKey with receiver\_priv\_key, and addr with receiver\_addr. Here's the optimized version of your code with these suggestions: from bitcoinutils.utils import to\_satoshis from bitcoinutils.setup import setup from bitcoinutils.transactions import Transaction, TxInput, TxOutput from bitcoinutils.script import Script from bitcoinutils.keys import PrivateKey as utilPrivKey from bitcoinutils.constants import SIGHASH\_ALL setup('testnet') sender\_priv\_key = utilPrivKey.from\_wif('SENDING ADDRESS PRIVATE KEY') sender\_pub\_key = sender\_priv\_key.get\_public\_key().to\_hex() addrs\_for\_script = sender\_priv\_key.get\_public\_key().get\_address() receiver\_priv\_key = utilPrivKey.from\_wif('RECEIVING ADDRESS PRIVATE KEY') receiver\_addr = receiver\_priv\_key.get\_public\_key().get\_segwit\_address() txin1 = TxInput("947145005bac29a9966403e986b8a36cb225cba504bffbb3f6c1da7dba7197be", 1) txin2 = TxInput("aea283b193f2179cb6a5c2bcea4b9ad7158960696ebfb5c15d22a0411f25dafe", 0) script\_code = addrs\_for\_script.to\_hash160() msg1 = "69eb032167c25784108b9783c9d59ce23608d00238eb9e3c03c73cdd79f74528" op\_return\_script = Script(\["OP\_RETURN", msg1\]) txoutOpR = TxOutput(0, op\_return\_script) txout = TxOutput(to\_satoshis(0.00034416), receiver\_addr.to\_script\_pub\_key()) tx = Transaction(\[txin1, txin2\], \[txoutOpR, txout\], has\_segwit=True) txsign1 = sender\_priv\_key.sign\_segwit\_input(tx, 0, script\_code, to\_satoshis(0.00032557), SIGHASH\_ALL) tx.witnesses = \[Script(\[txsign1, sender\_pub\_key\])\] txsign2 = sender\_priv\_key.sign\_segwit\_input(tx, 1, script\_code, to\_satoshis(0.00006859), SIGHASH\_ALL) tx.witnesses.append(Script(\[txsign2, sender\_pub\_key\])) signed\_tx = tx.serialize() print("raw tx below this line") print(signed\_tx) print("raw tx above this line")

warpanomaly

Oh nice! Good job! I actually got my code to work too. This is my script that takes 2 hard coded outputs and spits out a working transaction: ``` from bitcoinutils.utils import to_satoshis from bitcoinutils.setup import setup from bitcoinutils.transactions import Transaction, TxInput, TxOutput from bitcoinutils.script import Script from bitcoinutils.keys import PrivateKey as utilPrivKey from bitcoinutils.constants import SIGHASH_ALL, SIGHASH_ANYONECANPAY setup('testnet') # private key for tb1qj6zz96g8xgrwpgmdlvmkrjlwzz54sf47086yc9 priv = utilPrivKey.from_wif('PRIVATE KEY FOR SENDING ADDRESS') pub = priv.get_public_key().to_hex() addrs_for_script = priv.get_public_key().get_address() # private key for tb1qxgm8j0cq7tnftef3t563psl56gtmzxanm5c9uy recPrivKey = utilPrivKey.from_wif('PRIVATE KEY FOR RECEIVING ADDRESS') # This UTXO has 0.00009839 btc txin1 = TxInput("102172a062da813c3aa8cc2fb3d523cf2db300e54cd680c2129c23c97db9dd8e", 0) # This UTXO has 0.00026859 btc txin2 = TxInput("b3fcae0b28b387475a123c056298aec0ba3759cd019f9d0975f5af0874f395ff", 1) addr = recPrivKey.get_public_key().get_segwit_address() addr_non_seg = recPrivKey.get_public_key().get_address() # the script code required for signing for p2wpkh is the same as p2pkh script_code = Script(['OP_DUP', 'OP_HASH160', addrs_for_script.to_hash160(), 'OP_EQUALVERIFY', 'OP_CHECKSIG']) # remaining 0.00005 is tx fees txout = TxOutput(to_satoshis(0.00031698), addr.to_script_pub_key()) # create transaction from inputs/outputs -- default locktime is used tx = Transaction([txin1, txin2], [txout], has_segwit=True) txsign1 = priv.sign_segwit_input(tx, 0, script_code, to_satoshis(0.00009839), SIGHASH_ALL | SIGHASH_ANYONECANPAY) tx.witnesses = [ Script([txsign1, pub]) ] txsign2 = priv.sign_segwit_input(tx, 1, script_code, to_satoshis(0.00026859), SIGHASH_ALL) tx.witnesses.append( Script([txsign2, pub]) ) signed_tx = tx.serialize() print("raw tx below this line") print(signed_tx) print("raw tx above this line") ```

BeYourOwnBankzy

THE PUBLIC KEY IS A HASH OF THE PRIVATE KEY. You just contradicted yourself and you didn’t even notice

niddLerzK

You have something that you wanna predict, you go to a SHA-256 Hash algorithm and write it. Example : "Red Notice CZ". The algorithm will provide you with a HASH, Example: abc123. You post abc123 in twitter and wait. If CZ gets a red notice, you say that this abc123 hash equals Red Notice CZ, and people will know that you predicted it.

igadjeed

An output of a Bitcoin transaction contains a script. For a normal payment this script does a bit of hashing, compares hashes, checks a signature. For this there are Bitcoin Script OP codes like OP_DUP, OP_HASH160, OP_EQUALVERIFY, OP_CHECKSIG OP_RETURN is a do-nothing op code. Most Bitcoin nodes allow up to 80 bytes of anything to be appended to this OP code. It's useful for recording a hash on the blockchain as a timestamp, or sending a message https://bitcoin.stackexchange.com/questions/29554/explanation-of-what-an-op-return-transaction-looks-like

igadjeed

There are no "senders" > if 5 people combined sent 7 other 3 BTC People don't send. Each address identifies a single coin, and is tied to the private key which can sign a transaction to spend that coin. The Bitcoin blockchain does not record people A Bitcoin transaction has one or more inputs and one or more outputs. There is no payment flow connection between a transaction's inputs and the same transaction's outputs. This is counter-intuitive, and contradicts the naive "A sends Bitcoin to B" understanding that many people have about Bitcoin The only hard link is that which enables Bitcoin's single spend design. Every transaction input (except coinbase) spends exactly one transaction output from an older transaction In the context of your analysis, this means you need to use the txID+output number stored in a transaction input to find the address and amount of the older transaction output being spent https://developer.bitcoin.org/reference/transactions.html#txin-a-transaction-input-non-coinbase The txoutput does not contain only an address. It has a script, or a SegWit txoutput has a witness version number and a hash of a public key (address, 160bits), or a hash of a script (address, 256 bits) It's easy to find the address in SegWit, legacy P2PKH and legacy P2SH transactions. Non-standard transaction outputs are rare. Block explorers don't attempt to decode the scripts Legacy P2PKH OP_DUP OP_HASH160 OP_PUSHBYTES_20 9f21a07a0c7c3cf65a51f586051395762267cdaf OP_EQUALVERIFY OP_CHECKSIG SegWit P2WPKH OP_0 OP_PUSHBYTES_20 8969651905e64ed58cec41d83bf46082ef49af5c Legacy P2SH OP_HASH160 OP_PUSHBYTES_20 9aea4a41d6e56734a5774520df62ddd362851c26 OP_EQUAL SegWit P2WSH OP_0 OP_PUSHBYTES_32 701a8d401c84fb13e6baf169d59684e17abd9fa216c8cc5b9fc63d622ff8c58d Taproot P2TR OP_PUSHNUM_1 OP_PUSHBYTES_32 d4095b912d88b6ad93468c4c35d9930f4878df43cab1f4432767325d5012d275 I didn't include Multisig. Have fun

igadjeed

For pay-to-public-key-hash (P2PKH / P2WPKH) addresses, yes Example Legacy: 12ksSH9YL6dYy7NVQwnJScRn1nwjp SegWit: bc1q0cfq82zjlxz57hw2vxjtjsrwcc0fqc0ngv9ee7 Those are the copy/paste addresses the recipient shares with the sender On the TXO on the blockchain, the legacy TXO has an unlocking script OP_DUP OP_HASH160 OP_PUSHBYTES_20 7e1203a852f9854f5dca61a4b9406ec61e9061f3 OP_EQUALVERIFY OP_CHECKSIG and a SegWit TXO has a witness version and the 20-byte address OP_0 OP_PUSHBYTES_20 7e1203a852f9854f5dca61a4b9406ec61e9061f3

br_izzy_1993

Let's start with the idea of a function, that is an order u do to a computer to get an input, do something with this and so return an output: function(x) = y. Let's make a function named add\_five(), it does what it says, it sum 5 to the number u put. So add\_five(5) = 10, add\_five(7) = 12, add\_five(x) = x+5, so on so on… It's a reversible function cause if i know the output is 20, so i know the input was 15. If I say add\_five(x) = 20, so i know x = 15 But u can make pretty random and crazy functions that doesnt allow u to know what was the input. Lets so make a crazy\_function(x), where it takes the input x, multiply by 5, divide by 4, sum with the sum of the digits of the results, divide by the last digit, sum 17 and subtract by the first digit. On this case if x = 10 so: crazy\_function(10) = – 10 x 5 = 50 – 50 / 4 = 12,5 – 12,5 + (1+2+5) = 12,5 + 8 = 20,5 – 20,5 / 5 = 4,1 – 4,1 + 17 = 21,1 – 21,1 - 1 = 20,1 We have crazy\_function(10) = 20,1. This is not a reversible function, cause if i say crazy\_function(x) = 20,1 there's no way to u know x = 10 other than guessing number by number. But notice that no matter how many times i put x = 10, the result (or output) will be always 20,1. This kind of function we can call HASH. A hash is a function that by looking at the output u can not know what was the original input, but every time you enter the same input, it will return the same output. This is how facebook, apple, reddit. twitter and the internet in general store your password on their database. They dont save your password, they save the HASH of your password, so whenever u want login and type your password, they make the hash and compare if it match with the hash they have stored, if it's match, okay the password is correct. (This is a very simplified way im describing) Your wallet seed is basically an input and your wallet address is an hash of this input. hope it had clarified a bit your mind,. Pls if im wrong on any aspect, correct me reddit people :3

only_merit

There are two aspects of this. One is how big is the UTXO that you create when you pay to it and this boils down to the size of scriptPubKey. But then it's also interesting what needs to be done for the receiver to spend it and this boils down to the size of scriptSig. In case of P2PK the scriptPubKey looks as follows: ``` <PK> OP_CHECKSIG ``` here `<PK>` is push instruction with argument of public key. P2PK can have both compressed and uncompressed keys. Compressed is shorter, 33 bytes, uncompressed 65 bytes. So one would use compressed. PUSH and CHECKSIG instructions are 1 byte each. So this would give you scriptPubKey which is 1 + 33 + 1 = 35 bytes. To spend that you'd need to produce a scriptSig. In this case it would be simply ``` <SIG> ``` i.e. PUSH instruction with an argument of the signature itself and how big is a signature is a bit complex (https://www.advancingbitcoin.com/blog/evolution-of-the-signature-size-in-bitcoin/) but let's say it's 71 bytes + 1 byte push = 72 bytes. So we would have: - sender creates a transaction with UTXO with 35 bytes scriptPubKey - receiver spends by providing scriptSig with 72 bytes With P2PKH situation is different: scriptPubKey is in form ``` OP_DUP OP_HASH160 <PKHASH> OP_EQUAL OP_CHECKSIG ``` each opcode is 1, PKHASH is push + 160 bits = 1 + 20 bytes = 21, total 25 bytes and scriptSig is in form ``` <SIG> <PK> ``` i.e. 72 + 34 = 106 bytes So from the sender's point of view P2PKH is 25 bytes, which is less than P2PK with 32 bytes. From receiver's point of view P2PK is 72 bytes, which is less than P2PKH with 106 bytes. Overall (system, after UTXO is spent) we have P2PK with 35 + 72 = 107 bytes vs P2PKH with 25 + 106 = 131 bytes.

igadjeed

> wouldn’t most nodes just refuse to enter the double-spend into the mempool The mempool is not relevant to consensus, nor is it relevant to miner double-spending Even in normal mining, a miner can build his candidate block from any source of valid transactions. He doesn't have to use his mempool. The mempool is, for obvious reasons, the best source of **unconfirmed** transactions An attacker will definitely not use a mempool for his double-spend. He will construct his own spending transaction and send it to the node network to be mined via the winning miner's mempool. When replacing the transaction with a send-to-self transaction, he includes the replacement transaction directly in his block directly. This transaction does not need to be seen by other nodes The node network follows the longest chain. A successful 51% attack will produce a longer chain than the regular miners. Every node in the node network will reorg its tip to follow the longer chain. The node network **does not judge** the replacement transaction as a double-spend. During the tip reorg, the original transaction disappears, as if it never existed --- Some extra background ... Chain tip reorgs happen whenever there is a tied mining race. This is not an attack, It is a normal occurrence - about 10 times per year. A node is not aware of a tied mining race until the next block arrives. If the new block does not follow the node's previous block (PREV_BLOCK_HASH does not match), then the node reorgs its tip to follow the longer chain A 51% attack forges a tied mining race, takes advantage of the nodes' consensus rule of always following the longest chain. A node never judges fraud or dishonesty. It prevents double-spending being recorded on the chain by choosing the longest chain https://www.metzdowd.com/pipermail/cryptography/2008-November/014832.html https://www.metzdowd.com/pipermail/cryptography/2008-November/014843.html https://www.metzdowd.com/pipermail/cryptography/2008-November/014858.html > The transaction in whichever branch ends up getting ahead becomes the valid one, the other is invalid. If someone tries to double spend like that, one and only one spend will always become valid, the others invalid > Receivers of transactions will normally need to hold transactions for perhaps an hour or more to allow time for this kind of possibility to be resolved > It is strictly necessary that the longest chain is always considered the valid one > When there are multiple double-spent versions of the same transaction, one and only one will become valid > The guy who received the double-spend that became invalid never thought he had it in the first place > We're not "on the lookout" for double spends to sound the alarm and catch the cheater. We merely adjudicate which one of the spends is valid >

keijyu

To elaborate further: Private keys are 256bit integers whereas P2PKH and P2WPKH scripts use a 160bit hash of public keys to verify ownership. Therefore by the pigeon hole principle, there exists some addresses where there are more than 1 private keys that can generate said address. But who knows how many this number actually is… It’s too large to compute. This is one of the reasons Taproot addresses are considered more secure than legacy and Segwit v0 addresses. TR output scripts don’t hash public keys therefore preserve the 256bit length. But then there is still the issue where ECDSA/secp256k1. These key and curve algorithms are based on modulo arithmetic at its core so there is no guarantee that each public key unique corresponds to a single private key. Again, too large to compute so no one actually knows. So the real answer to OPs post should be that no one knows the likelihood of guessing a private key. Unless someone with an incomprehensible amount of computing power goes and maps all secret keys to public keys, then further all public keys to HASH160 outputs this number will forever remain unknown. [Here’s a good video to wrap your head around just how strong 256bit security is.](https://youtu.be/S9JGmA5_unY)

igadjeed

My understanding differs from the /u/nullc comment, so it could be wrong. This is based on my memory of reading snippets of Core source code about 2 years ago Also, I'm assuming the question is about processing of recently mined blocks, not about the initial block download. I suspect those cases have different answers. The question can be interpreted either way. Please clarify I think the node accepts the block as an orphan and stores it until the missing block is sent, doesn't ask for the missing block In a different case - a chain tip fork caused by a tied mining race - a node recognizes that it might have a stale chain tip when the next block's PREV_BLOCK_HASH doesn't match, preventing the new block from extending the chain. In this case, the node asks another node (or other nodes) to send the block which has a hash matching PREV_BLOCK_HASH of the new block. If that turns out to be the valid longest chain, the previous block becomes stale > signatures They are not directly important for extending the chain. They are important for validating the block at transaction level. SegWit transactions do have signatures, and they are stored in the blockchain

igadjeed

These things tie together * tied mining race * chain tip reorg * 51% attack The reality of network latency creates approximately 10 tied mining races per year. A tied mining race creates forked chain tips. An individual node is unaware of a fork until the next block is mined, and it follows (via PREV_BLOCK_HASH) a chain which is different to the node's current chain. To reorg, the node requests the previous block which matches PREV_BLOCK_HASH and makes the fork block stale In a 51% attack, a miner with sufficient hash power can forge a tied mining race and use the fork to double-spend Any chain tip fork is an opportunity to double-spend. Normally, the opportunity is impossible to exploit because a tied mining race is unpredictable Occasionally, a tip fork (tied mining race) can be two blocks deep. Occasionally, a node might reorg and follow a chain which is then (next block) found to be shorter. Then it needs to re-reorg. To cover these possibilities, safe confirmation advice recommends waiting 6 blocks. In 99% of tied mining races, 2 confirmations is enough. In an extreme 2-block tip which is reorganized and re-reorganized, waiting 4 blocks is sufficient Even though very, very few chain tip reorgs are deeper than 2 blocks, there is no defined limit to the depth of a reorg. Your hypothetical network outage can be handled by an arbitrarily deep chain tip reorg In 51% attacks on Bitcoin-like blockchains, the attacker mined in parallel for 2 hours, and then released 2 hours of blocks to the node network. This method allows an attacker to circumvent the usual 6-block confirmation rule, but the experience also motivated exchanges (the double-spend victims) to dynamically calculate confirmation delays according to each crpyotcurrency's attack risk In your hypothetical, mals who are aware of a chain fork caused by a network outage can try to exploit the outage by double-spending. The risk is mitigated by the fact that their likely victims (coin-to-coin exchanges) should be aware of the chain fork, and wary of double-spend possibility. Also, to double spend, the attacker needs to be on the slow mining side of the outage, which may not mine enough blocks to pull off the heist

CuriousAboutThisNow

Thank you for your help , I think I have bit of a problem here, When I run above script with : getblock = rpc\_connection.getblock(("000000000000000000048596051c9f0554f6d0b477b28eac6a97fc37dde4274d"),2) What is returned looks like not fully completed json load : Results starts with : "HASH160 aaaea37810135e6fd2304fc9345d50e126dd6c3b OP\_EQUAL', 'hex': 'a914aaaea37810135e6fd2304fc9345d50e126dd6c3b87', 'address': " and then after 1000's of lines whole load end with "}\]}" So results doesn't look like proper json load ? Or im doing something wrong ? Im not very fluent with python tbh.

peachyoyo

👑666HASH | Play Here, Win Here👑 Welcome to the Global Blockchain TRC20-USDT Loterry Platform!🤑 Make ur deposit QUICK and SIMPLE💳 ®️REGISTER IT NOW®️ 69.city

seabass9900

👑666HASH | Play Here, Win Here👑 Welcome to the Global Blockchain TRC20-USDT Loterry Platform!🤑 Make ur deposit QUICK and SIMPLE💳 ®️REGISTER IT NOW®️ 69.city

Dear_Yesterday6588

👑666HASH | Play Here, Win Here👑 Welcome to the Global Blockchain TRC20-USDT Loterry Platform!🤑 Make ur deposit QUICK and SIMPLE💳 ®️REGISTER IT NOW®️ 69.city

SmoothGoing

What wallet are you using? Transaction ID is clear on that page next to HASH starts with 842b..

Ok_Juggernaut_3109

👑666HASH | Play Here, Win Here👑 Welcome to the Global Blockchain TRC20-USDT Loterry Platform!🤑 Make ur deposit QUICK and SIMPLE💳 ®️REGISTER IT NOW®️ 69.city

Ok_Juggernaut_3109

👑666HASH | Play Here, Win Here👑 Welcome to the Global Blockchain TRC20-USDT Loterry Platform!🤑 Make ur deposit QUICK and SIMPLE💳 ®️REGISTER IT NOW®️ 69.city

21reasonsto

You are correct the OP_HASH160 is in fact not a simple ripe160 but in fact ripe160(sha256(pub key)) what this extra hash of random hash function adds to 96bit collision security, is something cryptographers like to discuss, when it gets late and all are havy drunk and try to come up with funny puns about NISTcurve, internet and FIAT banking keys security , important is if OP_DUP OP_HASH160 collision OP_EQUALVERIFY OP_CHECKSIG. results in true, for sure i also assume that found collision number will not match to the correct key. But I still find the constructon choosen to sign btc tx quite secure and would not bother much, as long as we improve new signing chemes with softforks always to the payable and feasable capeabilitys of advesarys.

Warm-Replacement-902

👑666HASH | Play Here, Win Here👑 Welcome to the Global Blockchain TRC20-USDT Loterry Platform!🤑 Make ur deposit QUICK and SIMPLE💳 ®️REGISTER IT NOW®️ 69.city

Winter-Valuable6174

👑666HASH | Play Here, Win Here👑 Welcome to the Global Blockchain TRC20-USDT Loterry Platform!🤑 Make ur deposit QUICK and SIMPLE💳 ®️REGISTER IT NOW®️ 69.city

Winter-Valuable6174

👑666HASH | Play Here, Win Here👑 Welcome to the Global Blockchain TRC20-USDT Loterry Platform!🤑 Make ur deposit QUICK and SIMPLE💳 ®️REGISTER IT NOW®️ 69.city

Winter-Valuable6174

👑666HASH | Play Here, Win Here👑 Welcome to the Global Blockchain TRC20-USDT Loterry Platform!🤑 Make ur deposit QUICK and SIMPLE💳 ®️REGISTER IT NOW®️ 69.city

Lostbae_99

👑666HASH | Play Here, Win Here👑 Welcome to the Global Blockchain TRC20-USDT Loterry Platform!🤑 Make ur deposit QUICK and SIMPLE💳 ®️REGISTER IT NOW®️ 69.city

Lostbae_99

👑666HASH | Play Here, Win Here👑 Welcome to the Global Blockchain TRC20-USDT Loterry Platform!🤑 Make ur deposit QUICK and SIMPLE💳 ®️REGISTER IT NOW®️ 69.city

Lostbae_99

👑666HASH | Play Here, Win Here👑 Welcome to the Global Blockchain TRC20-USDT Loterry Platform!🤑 Make ur deposit QUICK and SIMPLE💳 ®️REGISTER IT NOW®️ 69.city

Lostbae_99

👑666HASH | Play Here, Win Here👑 Welcome to the Global Blockchain TRC20-USDT Loterry Platform!🤑 Make ur deposit QUICK and SIMPLE💳 ®️REGISTER IT NOW®️ 69.city

SongLeather1132

👑666HASH | Play Here, Win Here👑 Welcome to the Global Blockchain TRC20-USDT Loterry Platform!🤑 Make ur deposit QUICK and SIMPLE💳 ®️REGISTER IT NOW®️ [69.city](https://69.city)

PassEnvironmental739

👑666HASH | Play Here, Win Here👑 Welcome to the Global Blockchain TRC20-USDT Loterry Platform!🤑 Make ur deposit QUICK and SIMPLE💳 ®️REGISTER IT NOW®️ [69.city](https://69.city)

Cute_Reference5430

👑666HASH | Play Here, Win Here👑 Welcome to the Global Blockchain TRC20-USDT Loterry Platform!🤑 Make ur deposit QUICK and SIMPLE💳 ®️REGISTER IT NOW®️ [69.city](https://69.city)

BeautifulBig9119

👑666HASH | Play Here, Win Here👑 Welcome to the Global Blockchain TRC20-USDT Loterry Platform!🤑 Make ur deposit QUICK and SIMPLE💳 ®️REGISTER IT NOW®️ 69.city

IRightReelGud

You're brainwashed. LOOK AT THE FUCKING CHART!!!! https://bitinfocharts.com/comparison/hashrate-btc-eth.html#alltime There is no comparison. Literally. You have to take BTC off the chart to even see that ETH is the red line at the very bottom of the chart. BTC has 250,000 times the hashing power of ETH. Ethereum is a fucking scam. Try running a full Ethereum node. It's impossible without a data center. The Ethereum Foundation even tells you this. https://ethereum.org/en/run-a-node/ You can run a Bitcoin node on a damn raspberry pi for actual fuck's sake. https://bitcoin.org/en/full-node Ethereum is centralized with a king. Bitcoin has no king and will not tolerate one. I'm warning you all. IGNORE THE ETHEREUM MARKETING. LOOK AT THE HASH RATE CHART. THERE'S NO WAY 1 ETH IS WORTH 7% OF 1 BTC WHILE HAVING ONLY 0.0004% OF THE SECURITY.

coinfeeds-bot

tldr; Hashdex has announced the launch of the Hashdex Nasdaq Crypto Index Europe exchange-traded product (ETP). The ETP will be available on the SIX Swiss Exchange under the ticker symbol HASH SW starting May 2, 2022. The NCIE is an index designed to measure the performance of the overall digital asset market while remaining reflective of the ETP listing standards. *This summary is auto generated by a bot and not meant to replace reading the original article. As always, DYOR.*

brarn9056

I'm unable to add pictures on this apparently but this is a quote from CB: >Upon a careful investigation, I can see that your transaction was performed using the Binance Smart Chain network. You can verify this using the transaction hash here: \[\[\[\[INSERT TX HASH\]\]\]\] Coinbase does not support the Binance Smart Chain network, therefore we do not have access to these funds and are unable to recover the asset you have mistakenly sent using an unsupported network. As expressed on the pop up message under your receiving wallet address, we only support the ERC20 version of the token while the Binance Smart Chain uses the BEP20 protocol, and any transaction sent through a different network might cause the loss of the asset. I understand this is a frustrating experience and I wish there was more we could do, but we don’t have the ability to recover these funds at this time. In the future, I recommend sending a small test amount before sending any large amounts, especially when using an unfamiliar network like the Binance Smart Chain. So they forgot to paste my TxID I provided them in a previous email, and they also state that I used BEP20 which I clearly didn't using the TxID in my post. I think it's just a template email that kind of fits my situation and the lazy CB support member just sent it to get me off the phone.

lerkmore

HTLC's run on Bitcoin nodes which have the ability to evaluate [Bitcoin Scripts](https://en.bitcoin.it/wiki/Script). Here's an example script and [page talking about them](https://arshbot.medium.com/the-indepth-anatomy-of-an-htlc-6d0bca654588): OP_IF [HASHOP] <digest> OP_EQUALVERIFY OP_DUP OP_HASH160 <seller pubkey hash> OP_ELSE <num> [TIMEOUTOP] OP_DROP OP_DUP OP_HASH160 <buyer pubkey hash> OP_ENDIF OP_EQUALVERIFY OP_CHECKSIG

G33ONER

(let me give it a go)... Because L2 will handle and HASH (protect) all transactions along the way before issuing the data back onto L1 to be recorded on chain, thus the tracing data is sheilded from view between merchant and customer... 😒 So much reading and learning to do 😕

blswae

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎100$ worth $BRANCH Token Airdrop! 💎 WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

Feisty_Expression_39

🚨 FIRST 50 ENTRIES IN PRESALE WILL HAVE A CHANCE TO WIN A $250 AIRDROP OF $BRANCH 🚨 MAX BUY PRESALE AND BE ENTERED TO WIN 💎1 $BRANCH NFT Airdrop! 💎100$ worth $BRANCH Token Airdrop! 💎50$ worth $BRANCH Token Airdrop! WINNERS WILL BE PICKED BY TX HASH, POST YOUR TX HASH IN THE COMMUNITY! CONTEST! 🚀 More Entries = More Chances to Win! https://tokenfuel.io/launchpad/0xE0f8FD1D8132e76457e1c3db6E018fA62A70170c TG: https://t.me/branchenvironment

SharkForce_12

$HASH for the Provenance Network. Learned about them why New York Bank Corp started using them for payments. Still not on any exchanges/brokers so you have to buy direct from dlob.io

yeetsfeetsdeletes

How many more of these dumb posts can we get? These aren't "4 MINERS" that control over 50% of the hash power but 4 MINING POOLS, MADE ALL MADE OF VARIOUS MINERS CONTRIBUTING HASHPOWER THAT CAN AT ANY TIME DELEGATE THIER HASH TO ANOTHER MINING POOL IF NEEDED.

Tvmouth

cybersecurity guy doesn't get HASH math.... lol. "snake oil" he says... hash math...wow dude. how do you PHP if you think blockchain is snake oil?

WittyStick

Perhaps a brief intro to point you in the right direction: Start by understanding the structure of a [Transaction](https://en.bitcoin.it/wiki/Transaction). These are the building blocks of bitcoin and the blockchain. Transactions have multiple inputs and outputs. An output contains an amount plus the spending conditions which are valid for it, by means of a [Script](https://en.bitcoin.it/wiki/Script), known as the scriptPubKey. A scriptPubkey usually contains a hash of a public key and is known as a PayToPublicKeyHash (P2PKH) output. To spend a historical unspent transaction output (UTXO), a new transaction is constructed with one of its inputs referring to the output which is to be spent. This input contains the necessary information, known as the *witness* or scriptSig, required to make the script from the output being referred to evaluate to true. Usually this is, at minimum, a public key and a signature. The scriptSig is evaluated - pushing this witness onto an evaluation stack, and then the scriptPubKey is evaluated with this as the initial stack. A scriptPubKey will duplicate the public key (OP_DUP), hash it (OP_HASH160) and then compare it to a hash which was embedded in the scriptPubKey (OP_EQUALVERIFY). Finally, it will determine the signature for this transaction is signing the details of the spending transaction itself, using the corresponding private key to sign it. This is a complex step described in [OP_CHECKSIG](https://en.bitcoin.it/wiki/OP_CHECKSIG). A UTXO always spends the entire amount which was in the output, and once spent it is no longer a UTXO, and cannot be double-spent. It is archived for the purpose of auditing the history of the ledger. If an intended payment is not intended to spend a full amount of an output, the spender must construct an additional output in their new transaction, known as *change*, where they spend the difference back to themselves. There can be many outputs and many inputs to a transaction, and they are not linked to each other. The key requirement is that the sum of amounts in all of the outputs of a transaction is less than the sum of amounts of the UTXOs being spent. Any difference between these amounts is taken as a transaction fee by the miner of a block. A [Block](https://en.bitcoin.it/wiki/Block) is a list of transactions which are to be committed to the ledger by a miner. Similar to how an input references a historical output, a block must reference a historical block. This is typically the most recent block on the network, as each participant on the network will only accept the longest chain of blocks, with the most proof of work as the correct version of the ledger. It is not possible to refer to older blocks as you would need more proof-of-work than the majority of the network in order to have the longest chain of blocks. Every block contains, as it's first transaction, a special [coinbase transaction](https://en.bitcoin.it/wiki/Coinbase), which, unlike a regular transaction, does not spend any existing UTXO. The input amount of a coinbase transaction is calculated from the sum of all fees for transactions included in the block, plus a subsidy which is determined by the block number. The outputs of a coinbase transaction are regular transaction outputs where the miner includes their own public keys. The way people communicate their public keys to receiving payments is via an [Address](https://en.bitcoin.it/wiki/Invoice_address). An address encodes a public key hash and information about the type of the output to be constructed. The spender includes this public key hash in the scriptPubKey of an output, and then once their transaction has been included in a block on the longest chain of blocks, the output may only be spent by the person who has the private key corresponding to this public key hash.

igadjeed

In centralized payment systems, the gateway becomes gatekeeper - decides which transactions and participants are allowed or banned - because the system is centralized The purpose of Bitcoin is a payment system with no gatekeeper. Decentralization excludes gatekeepers Bitcoin is a decentralized node network. Every node has its own copy of the Bitcoin blockchain. Every Bitcoin node checks every new block, and all the transactions in the block **after the block is mined**. This is Bitcoin consensus Does the miner check all the transactions in the block? He doesn't have to. But if his block (or any of the block's transactions) has errors, the node network rejects the block. The sensible miner checks his block, to avoid wasting electricity mining a block which has errors. This is the miner's choice. It is not consensus Before mining, new unconfirmed transactions are propagated around the node network. Most nodes check transactions at this point. They don't have to. This checking is policy, not consensus > Many resources say that the double-spending problem is solved by the fact that the network uses the longest chain But you don't bother to link any of these "resources" in your post. It is a convenient shorthand to conflate these two things, as a cheap explanation of something more complicated. Whoever writes those statements is appeasing their readers' desire for simplicity, assumes all the readers are stupid, willing to accept inaccuracy The double spending problem is solved by the spending mechanism. Bitcoin spends coins. A coin can only be spent once, can only be spent completely. No partial spends. Bitcoin does not have accounts, does not spend from account balances or from wallet balances > couldn't you include two transactions in one block and therefore double spending? A miner could. Then he wins the mining race, sends his winning block to his neighbor nodes. Each node checks all the transactions, discovers two transactions spending the same coin, rejects the entire block. Then those few nodes which received that block from that miner do not propagate the block to their neighbor nodes. The block no longer exists > longest chain The 10-minute block interval is long enough for almost every mining race to have a single winner. Occasionally (less than once per month) two miners win the race at almost the same time. The world-wide nature of the node network, combined with normal network latency, allows those two blocks to propagate into different sets of nodes in the node network. This is a temporary chain fork, one block deep. Both forks are the same length. Each node is independent of all other nodes. So, every node behaves as if it has the correct chain. When the next block is mined, it extends the fork defined by the linking hash (PREV_BLOCK_HASH) in the new block's header. Now, one fork is longer. The nodes on the other fork will detect that PREV_BLOCK_HASH in the new block does not match the tip of their chain. They will ask their neighbors to send the missing previous block, and will reorg their chain tip by discarding the now-stale block You can see that double spending prevention is not directly related to resolving temporary chain forks (following the longest chain). But there is a possibility that the two different chain tip blocks had two different transactions spending the same coin. If a merchant's node receives the shorter-chain tip block, he may believe he has been paid. When that block is replaced and becomes stale, he will discover that he wasn't paid. This is the reason that merchants are advised to wait up to 6 confirmations. The longest chain mechanism chooses which transaction is valid. The consensus validation mechanism prevents double spending To reemphasize ... The consensus mechanism secures the blockchain. Checking block validity and transaction validity **after mining** is the only safe way to ensure that all 50,000 or more nodes have the same transaction history. Nodes do not trust pre-mining transaction verification (policy). Nodes do not trust miners. Also, nodes do not trust nodes. When a node validates a block and propagates the block to its neighbor nodes, every node repeats the consensus validation. Every node operates independently, proving that the new block is valid before adding it to its own blockchain

Big_Turd_Sniffer

Since most people in this sub think people who invest in NFTs are only buying dumbass ape jpegs, check out the projects below. Disclaimer, I own The Red Village champions but am not invested in Zed or BMC. Not trying to shill, just trying to open you guys’ eyes to the possibilities that are already here. [The Red Village](https://theredvillage.com) - Play to Earn gladiator fighting. You purchase a gladiator and fight other people’s gladiators for ETH. You can also “breed” your gladiators to make new NFTs! [Blockchain Miners Club](https://www.blockchainminers.club) - Owning one of these gives you ownership % of 110 (and growing) bitcoin miners owned by the project. This project has staking as well, which gives you their ERC20 token, $HASH. [Zed Run](https://zed.run) - Digital horse racing and breeding!

Big_Turd_Sniffer

I can answer 2 & 3. 2: As of now, creators would get royalties from a Getty Images for the *initial* sale. If, however, the individual who purchased that media turns around and sells it to another individual, the artist sees 0 royalties. NFTs allow for the creator to receive royalties each and every time that media is sold. For example, imagine if Van Gogh had made his paintings into NFTs. Even 100+ years later, his estate would continue receive royalties any time they NFT was sold. 3. The use case for staking NFTs is primarily for p2e gaming right now. I have friends who are, I shit you not, making 10-20k a month right now staking their [Creepz](https://opensea.io/collection/genesis-creepz) to earn the game’s token, [Loomi.](https://coinmarketcap.com/currencies/loomi/) Admittedly, this is a *very* niche use case, but you can imagine where this would go. In my opinion, people miss the ball park with NFTs 99% of the time because they don’t see the value in a media’s *life on the blockchain* in the long term. Obviously you could screenshot all of my NFTs and claim you own them. I, however, couldn’t care less about that, since I see the value in owning that media on chain. Since people see NFTs solely through the scope of dumbass Ape jpegs, let me show you some projects that are already actually using the technology. [The Red Village](https://theredvillage.com) - Play to Earn gladiator fighting. You purchase a gladiator and fight other people’s gladiators for ETH. You can also “breed” your gladiators to make new NFTs! [Blockchain Miners Club](https://www.blockchainminers.club) - Owning one of these gives you ownership % of 110 (and growing) bitcoin miners owned by the project. This project has staking as well, which gives you their ERC20 token, $HASH. [Zed Run](https://zed.run) - Digital horse racing and breeding! Sorry for the wall of text. I like NFTs lol

Big_Turd_Sniffer

I can answer 2 & 3. 2: As of now, creators would get royalties from a Getty Images for the *initial* sale. If, however, the individual who purchased that media turns around and sells it to another individual, the artist sees 0 royalties. NFTs allow for the creator to receive royalties each and every time that media is sold. For example, imagine if Van Gogh had made his paintings into NFTs. Even 100+ years later, his estate would continue receive royalties any time they NFT was sold. 3. The use case for staking NFTs is primarily for p2e gaming right now. I have friends who are, I shit you not, making 10-20k a month right now staking their [Creepz](https://opensea.io/collection/genesis-creepz) to earn the game’s token, [Loomi.](https://coinmarketcap.com/currencies/loomi/) Admittedly, this is a *very* niche use case, but you can imagine where this would go. In my opinion, people miss the ball park with NFTs 99% of the time because they don’t see the value in a media’s *life on the blockchain* in the long term. Obviously you could screenshot all of my NFTs and claim you own them. I, however, couldn’t care less about that, since I see the value in owning that media on chain. Since people see NFTs solely through the scope of dumbass Ape jpegs, let me show you some projects that are already actually using the technology. [The Red Village](https://theredvillage.com) - Play to Earn gladiator fighting. You purchase a gladiator and fight other people’s gladiators for ETH. You can also “breed” your gladiators to make new NFTs! [Blockchain Miners Club](https://www.blockchainminers.club) - Owning one of these gives you ownership % of 110 (and growing) bitcoin miners owned by the project. This project has staking as well, which gives you their ERC20 token, $HASH. [Zed Run](https://zed.run) - Digital horse racing and breeding! Sorry for the wall of text. I like NFTs lol

SharkForce_12

Bullish on $HASH for anxiety.

SharkForce_12

Happy to see this rolling out. Been in $HASH (coin of the Provenance chain) for awhile so I hope to see movement soon.

pepperonimilkjuice5

I’m sold. Where can I buy this $HASH everyone is talking about?

Jacked_1

No ELI5, but is fairly easy to follow. Assuming you're running your own node, as you should, run the bitcoin-cli utility to get the first block's hash: bitcoin-cli getblockhash 0 You may need to use your node's RPC credentials if not locally connected. Once you have the hash run bitcoin-cli getblock [HASH] 2 The 2 is important as it'll increase the level of verbosity of the output, which will give us the hex of the singular transaction in that block. Then, take that hex and slap it onto any HEX to ASCII converter - This can be something like xxd or you'll simple search for a "Hex to ASCII web converter". Once converted, you'll be able to see the message. If you're running a pre-configured Bitocin Node stack like Umbrel and such, bitcoind will be running as a container, so you'll want to use RPC. RPC Switches: -rpcconnect=[ip] -rpcport=[PORT] -rpcuser=[USER] -rpcpassword=[PASSWORD] Getting this information from a pre-configured stack, to not get too technical, can vary based on which stack, so I'd check your stack-specific forums/chats. I'm sure they'll help.

DarthTrader357

I dunno. Most people DO NOT do it. Like 90% of "investors/traders" diversify or even over diversify and funds/institutions are required to crazy over diversify. Something like required to have 5% in every sector and not more than 5% in any one stock. So ask yourself. Follow the crowd? Or follow the billionaires? A market that is $1 trillion going to zero is unheard of. Massive infrastructure exists to work with it etc. It is doubtfully a bubble at this point. It's one thing if people on robinhood buy stock in a virtually non existent company. But at this point entities are building powerplants to mine bitcoin. And what people overlook is all that HASH power is a weapon that the US DOD can use to bruteforce almost anything. The fact that China gave it up shows how fycking stupid China is