Bitcoin Forum
May 04, 2024, 06:08:14 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: so.. why do verification's have to occur exclusively in blocks?  (Read 714 times)
meebs (OP)
Hero Member
*****
Offline Offline

Activity: 616
Merit: 500



View Profile
January 20, 2013, 04:51:30 AM
 #1

I was thinking... Why is a block being found the ONLY way a transaction can be verified?


Why cant a message just be sent out to the nodes/clients with a simple query of "hey... so it is cool if address X sends Y BTC to address Z... would you approve that in a future block?"

Randomly pick a dozen or so nodes to send it to and if all responses come back affirmative at least then there is substantially greater evidence of the transaction being legit verses completely unsafe.

MAkes sense to me at least.. but i'm not to intimately familiar with the technical side of transaction verification.

Thanks!

              ▄▄▄█████████████▄▄▄
           ▄████████▀▀▀▀▀▀▀████████▄
        ▄██████▀▀             ▀▀██████▄
      ▄█████▀▀                    ▀▀█████▄
     █████▀                          ▀█████
    ████▀          ▄▄███████▄▄         ▀████
   ████▌        ▄██▀▀▀    ▀▀▀██▄        ▐████
  ████▌       ▄██▀            ▀██▄       ▐████
 ▐████       ██▀   ▄▄█▀▀▀█▄▄    ▀██       ████▌
 ████▌      ▐█▌   █▀  ▄▄   ▀▀             ▐████
▐████       ██  █▌  █▌ █████████████      ████▌
▐████       ██  ▐█  ▐█                     ████▌
▐████       ██  █▌  █▌ █████████████      ████▌
 ████▌      ▐█▌   █▄  ▀▀   ▄▄    ██▀      ▐████
 ▐████       ██▄   ▀▀█▄▄▄█▀▀    ██▌       ████▌
  █████       ▀██▄            ▄██▀       █████
   █████        ▀██▄▄▄    ▄▄▄██▀        █████
    █████          ▀▀███████▀▀         █████
     █████▄                          ▄█████
      ▀█████▄▄                    ▄▄█████▀
        ▀██████▄▄             ▄▄██████▀
           ▀████████▄▄▄▄▄▄▄████████▀
              ▀▀▀█████████████▀▀▀
Global Cryptocurrency
          ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬

  DECENTRALISING PRODUCTION, LOGISTICS AND PAYMENT 
                ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬   3D SERVICE      32 BAY     GCC WEBWALLET
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬

1714846094
Hero Member
*
Offline Offline

Posts: 1714846094

View Profile Personal Message (Offline)

Ignore
1714846094
Reply with quote  #2

1714846094
Report to moderator
TalkImg was created especially for hosting images on bitcointalk.org: try it next time you want to post an image
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714846094
Hero Member
*
Offline Offline

Posts: 1714846094

View Profile Personal Message (Offline)

Ignore
1714846094
Reply with quote  #2

1714846094
Report to moderator
1714846094
Hero Member
*
Offline Offline

Posts: 1714846094

View Profile Personal Message (Offline)

Ignore
1714846094
Reply with quote  #2

1714846094
Report to moderator
FreeMoney
Legendary
*
Offline Offline

Activity: 1246
Merit: 1014


Strength in numbers


View Profile WWW
January 20, 2013, 05:35:21 AM
 #2

Some miners saying "yeah, I'll do that latter" doesn't mean a different miner won't include a tx that makes the first one invalid (uses the same coin to pay someone else). The miner's intent or even promise means nothing because when they build the block it will be ignored because it has an impossible tx in it.

Play Bitcoin Poker at sealswithclubs.eu. We're active and open to everyone.
meebs (OP)
Hero Member
*****
Offline Offline

Activity: 616
Merit: 500



View Profile
January 20, 2013, 05:49:45 AM
 #3

Good point. I didnt think of it that way.

              ▄▄▄█████████████▄▄▄
           ▄████████▀▀▀▀▀▀▀████████▄
        ▄██████▀▀             ▀▀██████▄
      ▄█████▀▀                    ▀▀█████▄
     █████▀                          ▀█████
    ████▀          ▄▄███████▄▄         ▀████
   ████▌        ▄██▀▀▀    ▀▀▀██▄        ▐████
  ████▌       ▄██▀            ▀██▄       ▐████
 ▐████       ██▀   ▄▄█▀▀▀█▄▄    ▀██       ████▌
 ████▌      ▐█▌   █▀  ▄▄   ▀▀             ▐████
▐████       ██  █▌  █▌ █████████████      ████▌
▐████       ██  ▐█  ▐█                     ████▌
▐████       ██  █▌  █▌ █████████████      ████▌
 ████▌      ▐█▌   █▄  ▀▀   ▄▄    ██▀      ▐████
 ▐████       ██▄   ▀▀█▄▄▄█▀▀    ██▌       ████▌
  █████       ▀██▄            ▄██▀       █████
   █████        ▀██▄▄▄    ▄▄▄██▀        █████
    █████          ▀▀███████▀▀         █████
     █████▄                          ▄█████
      ▀█████▄▄                    ▄▄█████▀
        ▀██████▄▄             ▄▄██████▀
           ▀████████▄▄▄▄▄▄▄████████▀
              ▀▀▀█████████████▀▀▀
Global Cryptocurrency
          ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬

  DECENTRALISING PRODUCTION, LOGISTICS AND PAYMENT 
                ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬   3D SERVICE      32 BAY     GCC WEBWALLET
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬

jl2012
Legendary
*
Offline Offline

Activity: 1792
Merit: 1093


View Profile
January 20, 2013, 06:03:42 AM
 #4

I was thinking... Why is a block being found the ONLY way a transaction can be verified?


Why cant a message just be sent out to the nodes/clients with a simple query of "hey... so it is cool if address X sends Y BTC to address Z... would you approve that in a future block?"

Randomly pick a dozen or so nodes to send it to and if all responses come back affirmative at least then there is substantially greater evidence of the transaction being legit verses completely unsafe.

MAkes sense to me at least.. but i'm not to intimately familiar with the technical side of transaction verification.

Thanks!

It works if:

1. A miner (or a group of miners) controls >50% total network hashing power;

2. This miner (or group) is honest (it always includes transactions in a future block as promised); and

3. This miner (or group) always rejects any block containing conflicting transactions

Donation address: 374iXxS4BuqFHsEwwxUuH3nvJ69Y7Hqur3 (Bitcoin ONLY)
LRDGENPLYrcTRssGoZrsCT1hngaH3BVkM4 (LTC)
PGP: D3CC 1772 8600 5BB8 FF67 3294 C524 2A1A B393 6517
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!