What if you copy your wallet to a usb then open it on another computer and have two wallets going at once...

the transaction transfers at difirent speeds throught each computer into the chain, there is no way to do this, this is why magical internet money its magical.

Assuming this isn't bait, proof of work is the reason. The consensus protocol will only accept one unless you are able to hijack the consensus which would require enough processing power to contribute 51% of the chain.

do they reject all transactions from that wallet address in the block ? or do they only consider the most recent transaction as valid?

I'm afraid though... science always progresses and beats the naysayers. Someone will surely be able to perfect nonsecond-scale transaction batching within the next year.

you can publish a transaction on both computers, however since the node can only process one at a time, only the first one counts and the second one will just fail since its invalid.

Even if you manage to get them on the exact same time, they probably either do a random one of those 2 first or go by something else to determine which to do first.

OH NO CRYPTO BOYS BTFO

Attached: 1540237269637.jpg (250x236, 5K)

No, there is no *recent transaction* you can only do one ,the others dont happen.

>probably
so you're saying there's a chance? AAAAAAAAAAAAAAAAAAAAAAAAAAAHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH why didn't I listen to Peter Schiff

Attached: 208467204867.jpg (450x450, 32K)

FPBP
OP you a dumb, the transaction only counts when you send from your address. If you send a transaction from one the balance will change on both copies.

Attached: 1537036475296.jpg (399x385, 29K)

propably as in how they decide which transaction to do first if they really get 2 at once. They could also do something like do it alphabetically by tx id

>They could also do something like do it alphabetically by tx id
>propably

Attached: 1536848457045.jpg (949x1024, 63K)

Attached: 6-4aQ-Qp_400x400.jpg (400x400, 28K)

Because transactions are organized on blocks, and blocks can't have contradictory transactions or they becomes invalid.
A 51% attack lets you make two valid blocks, that's how you double spend.

There are people on this board who literally don't even understand what a blockchain is in its most basic sense.

GR8 B8 M8, 8/8

>he figored that out
>domp it

Attached: 1522913015159.jpg (1440x1383, 383K)

never ever copy your wallet

you wat? you can doubles spend with a single wallet, you just clear the tx cache and rescan the chain, voila you got your coins ready to spend even tho they are waiting for confirmation in a tx.

the one with the highest fee most likely or earliest if they have the same fee

>if you were able to send a transaction at EXACTLY the same time from 2 computers, then you would successfully double spend and break crypto forever.
eheheheheh i wonder if there are stupid cucks out there that truly believe this...

It's the same as copy your USD in a copy machine. yes it's possible but the government will fuck you for counterfeiting

>A 51% attack lets you make two valid blocks, that's how you double spend.
no it actually allows you to shadow mine a longer chain and spend your coins differently on your shadow chain and publish it once you say sent your coins to an exchange and switched to an other crpyto and then managed to withdraw that other crypt you finally publish your longer shadow chain.

Attached: 1505779487439.jpg (2000x1335, 484K)

The only 51% I've seen involves the same node on two different wallets. You may have to split it up, but in theory it's the same node.

nigga i have double spent with the same client.
my transaction didn't confirm after 3 days i got bored. so i just used the rescan command on the core client
bitcoin-qt.exe --zapwallettxes=1
bitcoin-qt.exe --rescan (if you still can't see your coins as spendable for some reason)

What are you doing to appease the basilisk?

listen the double spend attack works on unconfirmed transactions only that's the normal double spend when you sign 2 transactions with the same inputs and publish them. both of them are valid but only one gets incorporated into the chain. anyone can do this and everyone will see what you did but it's inconsequential to btc. a successful 51% reorg attack allows you to double spend confirmed transactions even. but you got to be top dog miner to pull it.

>babies first fork
underage faggot detected

Or use NiceHash on a shitcoin

Whichever one gets consensus faster is the transaction and the rest bomb out as you don't have enough funds.