Bitcoin Forum
December 05, 2016, 12:59:28 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 [4]  All
  Print  
Author Topic: Micropayments?  (Read 11271 times)
Cdecker
Hero Member
*****
Offline Offline

Activity: 487



View Profile WWW
January 03, 2011, 12:51:35 PM
 #61

Is there a convention on which the transactions are ordered in the block? That might allow users to selectively fetch branches in the from other in order to get the same result as the block generator. Simply check if we by chance have the same merkle root, if not ask for the two child hashes, repeat. That might actually get the size down a constant length, but would put strain on the clients in order to check which transactions are in a block.

Edit: might be time to split the thread in order to collect ideas for network improvements?

Want to see what developers are chatting about? http://bitcoinstats.com/irc/bitcoin-dev/logs/
Bitcoin-OTC Rating
There are several different types of Bitcoin clients. Server-assisted clients like blockchain.info rely on centralized servers to do their network verification for them. Although the server can't steal the client's bitcoins directly, it can easily execute double-spending-style attacks against the client.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
FreddyFender
Full Member
***
Offline Offline

Activity: 215


Shamantastic!


View Profile
January 03, 2011, 03:15:20 PM
 #62


Found something that can check SW state of large HPCs.

InstantCheck: Checking the Determinism of Parallel Programs Using On-the-fly Incremental Hashing
http://www.upcrc.illinois.edu/media/publications.html
This could graph changes to SW or running programs by comparing previous hashes of software runs (Deterministic replay).
It might be useful to see who is monkeying with codebase and trying to game the system.
Simple changes to isStandard() would allow reporting to all generators and cartels... but this is future stuff not needed for beta Undecided

"Determinism is generally defined as producing observationally equivalent outputs on
all executions starting from observationally equivalent inputs"
https://researcher.ibm.com/researcher/files/us-mtvechev/SAS%202010%20-%20Determinism.pdf

isStandard() detects scout tx sent from random generator node (hive)
sStandard() creates test tx that watches IO read then creates hash (worker) on the fly that reports to generators nodes (hives)
compares to previous hash for inconsistencies, cool!
Attack drones could flood non-compliant nodes with requests and warn topologically nearby clients that generator "x" is problem.

I would like to see the java on this but I don't think it is FOSS.

Is this useful? These guys at ISU use this software to check for bugs/races/code integrity/network integrity/etc.
It takes a snapshot of specific executions and hashes it, then compares it to previous ones. Any inconsistencies could be graphed and redflag DOSes prior to when they affect the network.

Pages: « 1 2 3 [4]  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!