Bitcoin Forum
October 19, 2018, 12:20:23 PM *
News: Make sure you are not using versions of Bitcoin Core other than 0.17.0 [Torrent], 0.16.3, 0.15.2, or 0.14.3. More info.
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 [4]  All
Author Topic: Micropayments?  (Read 12528 times)
Hero Member
Offline Offline

Activity: 490
Merit: 503

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

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?
Bitcoin-OTC Rating
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
Hero Member
Offline Offline

Posts: 1539951623

View Profile Personal Message (Offline)

Reply with quote  #2

Report to moderator
Full Member
Offline Offline

Activity: 215
Merit: 100


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

Found something that can check SW state of large HPCs.

InstantCheck: Checking the Determinism of Parallel Programs Using On-the-fly Incremental Hashing
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"

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