[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]
2023-11: Warosu is now out of extended maintenance.

/biz/ - Business & Finance

View post   
File: 110 KB, 969x1000, 04862087.jpg [View same] [iqdb] [saucenao] [google]
11985434 No.11985434 [Reply] [Original]

what if you copy your wallet to a usb then open it on another computer and have two wallets going at once? wouldn't you be able to spend both? or however many instances you wanted? have people been doing this to crash the price?

>> No.11985446

>>11985434
Pls be bait pls be bait pls be bait

>> No.11985451

>he doesnt know about triple spending

>> No.11985457
File: 237 KB, 640x604, 1543682674136.png [View same] [iqdb] [saucenao] [google]
11985457

>>11985434
ssshhhhh don't tell them OP

quick delete this thread fast

fuckfuckfuckfuck

>> No.11985465

>>11985434

No, not unless you control 51% of the chain. This is how a double spend attack works in theory.

>> No.11985473

>>11985465
>set up 10 bitcoin clients
>sign 10 transactions simultaneously
why not work?

>> No.11985478

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. fortunately, no one has been able to do this at exactly the same time, down to the nanosecond. it's proven impossible...so far.

>> No.11985491
File: 9 KB, 223x226, 1543214280265.jpg [View same] [iqdb] [saucenao] [google]
11985491

>>11985473
someone please refute this

>> No.11985495
File: 43 KB, 499x498, 1542839005965.jpg [View same] [iqdb] [saucenao] [google]
11985495

try it see what happens. You might find that the AI living within Bitcoin won't appreciate it.

>> No.11985505

>>11985478
Lmao

>> No.11985506

>>11985478
>>11985473
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.

>> No.11985508

>>11985473
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.

>> No.11985512

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

>> No.11985518

>>11985478
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.

>> No.11985519

>>11985434
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.

>> No.11985522
File: 5 KB, 250x236, 1540237269637.jpg [View same] [iqdb] [saucenao] [google]
11985522

>>11985434
OH NO CRYPTO BOYS BTFO

>> No.11985526

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

>> No.11985532
File: 32 KB, 450x450, 208467204867.jpg [View same] [iqdb] [saucenao] [google]
11985532

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

>> No.11985537
File: 29 KB, 399x385, 1537036475296.jpg [View same] [iqdb] [saucenao] [google]
11985537

>>11985446
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.

>> No.11985557

>>11985532
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

>> No.11985570
File: 63 KB, 949x1024, 1536848457045.jpg [View same] [iqdb] [saucenao] [google]
11985570

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

>> No.11985575
File: 28 KB, 400x400, 6-4aQ-Qp_400x400.jpg [View same] [iqdb] [saucenao] [google]
11985575

>>11985570

>> No.11985618

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

>> No.11985662

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

>> No.11985678

>>11985434
GR8 B8 M8, 8/8

>> No.11985738
File: 383 KB, 1440x1383, 1522913015159.jpg [View same] [iqdb] [saucenao] [google]
11985738

>he figored that out
>domp it

>> No.11985745

never ever copy your wallet

>> No.11985789

>>11985465
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.

>> No.11985802

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

>> No.11985820

>>11985478
>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...

>> No.11985826

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

>> No.11985890

>>11985618
>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.

>> No.11985922
File: 484 KB, 2000x1335, 1505779487439.jpg [View same] [iqdb] [saucenao] [google]
11985922

>>11985826

>> No.11986044

>>11985789

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.

>> No.11986218

>>11986044
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)

>> No.11986246

>>11985495
What are you doing to appease the basilisk?

>> No.11986270

>>11986044
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.

>> No.11986282

>babies first fork
underage faggot detected

>> No.11986794

>>11986270

Or use NiceHash on a shitcoin

>> No.11987169

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