SHA-256 Algorithm – Encryption – BitcoinWiki

We need a standard for Bitcoin blockchain timestamps! Proposal Inside! Feedback please!

Dear Bitcoiners and Bitcoinerettes
I have recently found great interest in using the Bitcoin blockchain for secure and trustless timestamping. This interest was mainly raised as I would have loved to have proof of certain data I and others produced in the past. I am not in the situation to need the proof now, but It could have come in handy one day. I previously asked on reddit about advice regarding creation of an email plugin which would keep timestamps for all my emails. I imagined this plugin to timestamp based on certain filter criteria.
The reactions on reddit were quite negative: Too expensive, too much bloat, blockchain spam. At the time I was discouraged and let it slip away as it seemed unfeasible.
I started to study the current implementations and services and created this overview:
Bitcoin Blockchain Timestamping Overview
I have no affiliation with any of these and I have also not tried all of these services!
After studying these concepts which I found, I came to several conclusions:
I think we are in need of a standard which will be used more often. Only if we have a standard which lots of users follow, Bitcoin timestamps can be widely used and accepted. Just imagine a court case where someone claims to have such a timestamp. Technical experts will have to be called in to state that this is in fact as close to proof as it gets that the timestamp was in fact made prior to date X. Now if everyone does it differently, everyone will have to pay for their own experts and it will take much longer until these timestamps are accepted plus it will overall be more expensive to get them accepted, if there are several predominant types. If we follow a standard these timestamps could get a certain credibility amongst non-technical people and would be accepted much faster.
So what would be ideal requirements for such a standard?
From these requirements I figured the following concept would be best:
To verify A timestamp one needs the following:
Actually it was sipa who pointed me to ChronoBit (in the list linked above) and making use of of Merkle trees to reduce bloat. My proposal as pointed out above derives from the concept of CronoBit in that it still creates a transaction. However, it borrows the concept of the hash tree from CronoBit and I guess from Bitcoin itself too ;-)
While ChronoBit is fully p2p and decentralized it bears the problem that you either need to be mining on p2p-pool yourself, or rely on others to be mining for you. The timestamps are somewhat limited to blocks found by p2p-pool. It is elegant as you have a direct connection to the block hash and no additional transactions are needed.
I am look at using a one Satoshi transaction for x timestamps is like forging a little unspendable colored coin which serves as anchor point for many timestamp participants.
A single stamper (private or service) can literally create thousands of timestamps in a daily transaction. The client must store a little bit more data compared to single timestamp models. That is not an awful lot of data even for thousands of documents; e.g. 1500 digits proof per document (including some identifiers) would suffice to join forces and have 250’000 timestamps in one transaction.
I guess the standard needs to be as flexible as possible. The format must be similar to PGP signatures or so. Something like: {document’s hash; transaction hash, Merkle tree branch depth, Merkle tree branch hashes, claimed blocktime of verified block}
I like the concept because it would enable a fully dynamic level of self crated Merkle tree and service created Merkle tree. Can either be done on top of own full Bitcoin node, or with a service. If a service is used the hash tree can still be continued. The service can do nothing but fool you for some minutes. There are no privacy issues as only hashes are sent in the first place. After the service created and sent the proof, it can vanish without the timestamp being lost for the user; 3rd party trust will not be a critical thing for most users.
I also want to discuss the way the address is created in my proposal above. Some current implementations create a private key first and then derive the address from it. This makes the transacted Satoshi potentially prunable. Someone could spend it with the private key which is commonly known. I want that Satoshi stuck forever.
With this scheme I think it would be feasible to timestamp as many emails and documents as I want without having huge costs and the bloat is somewhat justifiable...
After your valued feedback I would like to try to put together a paper and some kind of demo implementation.
Best regards and thanks for reading.
Things which are not entirely clear to me:
submitted by SimonBelmond to Bitcoin [link] [comments]

WariHash  Cryptocurrency Mining  Buying and Selling Hash Power BFL BitForce SHA256 Single what is SHA-256 Algorithm  mining Algorithm BITCOIN MINING trailer AntMiner S9 Bitcon Asic SHA256 Miner BITMAIN

It turns out BIP-39 uses 128 bits of randomness and then uses SHA-256 to generate a 4-bit checksum that is appended to the end of the original 128-bits to get you the required 132 bits for 12 words. Get the best deals on ASIC Miner Virtual Currency Miners for Bitcoin SHA-256 Hash Algorithm when you shop the largest online selection at Free shipping on many items 4 ASIC Miner Bitcoin Miner USB Block Erupter SHA-256 333 with USB HUB. $100.00 +$10.89 shipping. Bitcoin Stack Exchange is a question and answer site for Bitcoin crypto-currency enthusiasts. Won't ASIC miners eventually break SHA-256 encryption? 3. How to generate a Bitcoin Private Key Checksum. 3. Understanding what is being run through Sha256. 2. Do pools distribute “jobs” to miners based on “failed” solutions which have In Bitcoin core you’ll find something called release signatures or in other words they are also called release hashes. They are ASC file which usually contains SHA256 hash and a PGP signature. The checksum string is a random hash value that is created from scanning the contents of the program. Developers often create and distribute these SHA-256 is a member of the SHA-2 cryptographic hash functions designed by the NSA. SHA stands for Secure Hash Algorithm. Cryptographic hash functions are mathematical operations run on digital data; by comparing the computed "hash" (the output from execution of the algorithm) to a known and expected hash value, a person can determine the data's integrity.

[index] [23274] [17268] [630] [2833] [2265] [3692] [30869] [20529] [25143] [22270]

WariHash Cryptocurrency Mining Buying and Selling Hash Power

Review Used Asic miner Ebit E10 18T SHA256 Bitecoin BCH BTC Miner Better than antminer S9 S11 S15 WhatsMiner M3X M10 Innosilicon T2T T3 Price: $399 Discount: 5% Check Sale Price Price HERE ... Bitcoin mining a block is difficult because the SHA-256 hash of a block's header must be lower than or equal to the target in order for the block to be accepted by the network. Best USED OLD Innosilicon T2T 30T sha256 asic miner T2 Turbo 30Th/s bitcoin BTC Mining machine with psu Better Than Antminer S9 z9 b7 Price: $328 Discount: 6% Obtain the Special Price HERE ... *** THIS WAS ONLY A JOKE - PLAYING AROUND WITH A VIDEO EDITOR *** From BitForce SHA256 Single - Technical Specifications Raw performance: 832 Mega Hash / second (+/- 10% ... The SHA-256 algorithm is used to mine bitcoin, It is worth noting SHA-256 is part of the SHA-2 cryptographic hash(SHA-2 (Secure Hash Algorithm 2) is a set of cryptographic hash functions designed ...

Flag Counter