Pages:
Author

Topic: Datacasting the blockchain (Read 4313 times)

brand new
Activity: 0
Merit: 0
March 24, 2023, 02:25:40 PM
#44
In case you like long but informative articles, there is a cool https://allbizreviews.com/ which can help you on your way of understanding blockchain. Who knows, maybe it will save your life as it did with mine? Because I was about to close a deal that could make me a bancrotee.
newbie
Activity: 1
Merit: 0
November 14, 2018, 04:20:02 AM
#43
Blockchains are incredibly popular nowadays.
what is a blockchain?

as the name indicates, a blockchain is a chain of blocks that contain information.

this technique was originally described in 1991 by a group of researchers.

then it was originally intended to timestamp digital documents so that it’s not possible to back them or to tamper with them. almost like a notary.

however, it went by mostly unused until it was adapted by Satoshi Nakamoto in 2009 to create the digital cryptocurrency bitcoin.

a blockchain is distributed ledger that is completely open to anyone.

they have an interesting property

once some data has been recorded inside a blockchain, it becomes very difficult to change it.
find step by step knowledge about blockchain here:- http://blogparagon.com/what-is-blockchain/
newbie
Activity: 5
Merit: 0
November 08, 2018, 11:36:52 AM
#42

Hi there Smiley
Emily here....I am a crypto lover. I want to share a post here related to the crypto world.
Top-ranked institutes and courses of the blockchain:
https://medium.com/@sk6140434/in-my-world-the-top-ranked-institutes-and-courses-of-blockchain-79cb256d8719
It is amazing for the crypto lovers. Bit.college is an amazing institute of blockchain technology which is going to launch its first online classes on 1st December. Everybody who wants to learn about the blockchain technology, I invite to come and learn about the blockchain technology. Believe me, u will learn a lot.
Website: www.bit.college
newbie
Activity: 224
Merit: 0
September 13, 2018, 04:04:51 PM
#41
Distributed Ledger technology (DLT) could create $ 1 trillion in trade over the next decade, according to a joint report by Bain & Company and the world economic forum.
newbie
Activity: 224
Merit: 0
September 12, 2018, 03:25:22 PM
#40
The Credits blockchain platform and computer manufacturer Lenovo New Vision Technology will start working together on the development of the Internet of things
full member
Activity: 266
Merit: 100
March 28, 2018, 07:26:00 AM
#39
It would be a high esteem key, yes; nonetheless do not settle for that it's one that will be something however tough to amass. Truly, endorsers would for the foremost half be basic cognitive process the protection model of the organization they contract with, nonetheless within the event that something happens, that trust bites the mud and another data throwing organization takes away their business or the supporters get their own web encourage. it isn't merchandiser latched.
newbie
Activity: 36
Merit: 0
March 14, 2018, 01:54:44 PM
#38
All cranes kriptovalyut obveshany advertising.Many users mistakenly click on the wrong way By thus giving to earn in branded advertising. As a result of this income, payments are made as well as the production of crypto-currency is possible through mining.
member
Activity: 263
Merit: 10
March 01, 2018, 01:18:41 AM
#37
It would be a high esteem key, yes; yet don't accept that it's one that would be anything but difficult to acquire. Truly, endorsers would for the most part be believing the security model of the organization they contract with, yet in the event that anything happens, that trust bites the dust and another information throwing organization takes away their business or the supporters get their own Internet encourage. It's not seller bolted.
full member
Activity: 322
Merit: 100
January 14, 2018, 01:25:21 PM
#36
Blockchain helps companies grow in price. This week, the publicly registered company Ameri Holdings has added Blockchain technology to its business model
legendary
Activity: 2506
Merit: 1010
April 17, 2012, 06:12:07 PM
#35
I check two sources twice using two different connection providers (incase I'm dns hijacked on one).

The check to verify could require only a few bytes if connecting to a trusted service.

The client could even have a special mode where the datacasting source is the only node normally used to get the block data but the rest of the client keeps the same peer discovery and block verification as what everyone else uses.
legendary
Activity: 1904
Merit: 1002
April 16, 2012, 08:35:54 PM
#34
The only way that could possibly work is if the "hostile" connection could generate blocks of the current difficulty and feed them to the clients.

Yes, that's the exact situation he was talking about in our other conversation.
It would become pretty damn obvious what was going on when the client didn't get their current block in the average time of 10 minutes each, but instead was getting them hours or days apart because the hostile connection owner had to generate them himself. After about a week of slow blocks, yes, you would definitely check an external source, but how do you know that the external source isn't being hijacked? dun dun dun...

I think you are putting too much stock in an "zomg every node is controlled by a single attacker" situation. It is implausible at best.

Like I already said twice, this was a situation D&T has brought up in the past, so I'm addressing him.  Yes, it is implausible.

As for the external source being hijacked, that's why I check two sources twice using two different connection providers (incase I'm dns hijacked on one).
rjk
sr. member
Activity: 448
Merit: 250
1ngldh
April 16, 2012, 08:32:42 PM
#33
The only way that could possibly work is if the "hostile" connection could generate blocks of the current difficulty and feed them to the clients.

Yes, that's the exact situation he was talking about in our other conversation.
It would become pretty damn obvious what was going on when the client didn't get their current block in the average time of 10 minutes each, but instead was getting them hours or days apart because the hostile connection owner had to generate them himself. After about a week of slow blocks, yes, you would definitely check an external source, but how do you know that the external source isn't being hijacked? dun dun dun...

I think you are putting too much stock in an "zomg every node is controlled by a single attacker" situation. It is implausible at best.
legendary
Activity: 1904
Merit: 1002
April 16, 2012, 08:26:54 PM
#32
How does the client invalidate the bad blocks unless it has a source of valid blocks?  The whole point here is that this is the only way to get the blockchain to some clients.

All clients have the starting source ... the genesis block.   The only way to validate block #1 is to ensure it meets block requirements and has the block hash from block #0.   As such all full-clients must include the genesis block.  From there every node can validate every tx from block #1 all the way to current block.   As indicated above clients may also include hardcoded checkpoints.

Nodes are NOT secure.  They are inherently insecure.  You have no idea how dishonest your fellow "peer" connections are.  Hell they could all be the same attacker.  As a result Bitcoin DISTRUSTS all blocks received from the network until validated and added to the chain tracing all the way back to the genesis block.

A broadcast system for blocks wouldn't be any different.


Right, but that doesn't help at all with new blocks, which is where any attack would play out Roll Eyes.

New block is simply the tail of the block chain.  Right now a peer node just gave you a block how do you make sure it is valid?

Check blockexplorer and blockchain.info from systems on multiple ISPs.
Why? If you have an existing, valid blockchain, and you want to check all additional blocks that are sent to you, what is wrong with how it is done now? Do you even know how it is done now? I doubt it.

Why the hostility?  I do know how it is done.  I'm just remembering a previous conversation with DeathAndTaxes where he brought up the case of having all your connections controlled by an attacker.  But thanks for butting in your your rudeness.
The only way that could possibly work is if the "hostile" connection could generate blocks of the current difficulty and feed them to the clients.

Yes, that's the exact situation he was talking about in our other conversation.
rjk
sr. member
Activity: 448
Merit: 250
1ngldh
April 16, 2012, 08:23:15 PM
#31
How does the client invalidate the bad blocks unless it has a source of valid blocks?  The whole point here is that this is the only way to get the blockchain to some clients.

All clients have the starting source ... the genesis block.   The only way to validate block #1 is to ensure it meets block requirements and has the block hash from block #0.   As such all full-clients must include the genesis block.  From there every node can validate every tx from block #1 all the way to current block.   As indicated above clients may also include hardcoded checkpoints.

Nodes are NOT secure.  They are inherently insecure.  You have no idea how dishonest your fellow "peer" connections are.  Hell they could all be the same attacker.  As a result Bitcoin DISTRUSTS all blocks received from the network until validated and added to the chain tracing all the way back to the genesis block.

A broadcast system for blocks wouldn't be any different.


Right, but that doesn't help at all with new blocks, which is where any attack would play out Roll Eyes.

New block is simply the tail of the block chain.  Right now a peer node just gave you a block how do you make sure it is valid?

Check blockexplorer and blockchain.info from systems on multiple ISPs.
Why? If you have an existing, valid blockchain, and you want to check all additional blocks that are sent to you, what is wrong with how it is done now? Do you even know how it is done now? I doubt it.

Why the hostility?  I do know how it is done.  I'm just remembering a previous conversation with DeathAndTaxes where he brought up the case of having all your connections controlled by an attacker.  But thanks for butting in your your rudeness.
The only way that could possibly work is if the "hostile" connection could generate blocks of the current difficulty and feed them to the clients. We are assuming that you already have a valid, trusted copy of the blockchain, remember? And even if you re-download it from scratch, you would have to be running a hacked version with no built-in checkpoints or genesis block.
legendary
Activity: 1904
Merit: 1002
April 16, 2012, 08:17:24 PM
#30
How does the client invalidate the bad blocks unless it has a source of valid blocks?  The whole point here is that this is the only way to get the blockchain to some clients.

All clients have the starting source ... the genesis block.   The only way to validate block #1 is to ensure it meets block requirements and has the block hash from block #0.   As such all full-clients must include the genesis block.  From there every node can validate every tx from block #1 all the way to current block.   As indicated above clients may also include hardcoded checkpoints.

Nodes are NOT secure.  They are inherently insecure.  You have no idea how dishonest your fellow "peer" connections are.  Hell they could all be the same attacker.  As a result Bitcoin DISTRUSTS all blocks received from the network until validated and added to the chain tracing all the way back to the genesis block.

A broadcast system for blocks wouldn't be any different.


Right, but that doesn't help at all with new blocks, which is where any attack would play out Roll Eyes.

New block is simply the tail of the block chain.  Right now a peer node just gave you a block how do you make sure it is valid?

Check blockexplorer and blockchain.info from systems on multiple ISPs.
Why? If you have an existing, valid blockchain, and you want to check all additional blocks that are sent to you, what is wrong with how it is done now? Do you even know how it is done now? I doubt it.

Why the hostility?  I do know how it is done.  I'm just remembering a previous conversation with DeathAndTaxes where he brought up the case of having all your connections controlled by an attacker.  But thanks for butting in your your rudeness.
rjk
sr. member
Activity: 448
Merit: 250
1ngldh
April 16, 2012, 08:14:01 PM
#29
How does the client invalidate the bad blocks unless it has a source of valid blocks?  The whole point here is that this is the only way to get the blockchain to some clients.

All clients have the starting source ... the genesis block.   The only way to validate block #1 is to ensure it meets block requirements and has the block hash from block #0.   As such all full-clients must include the genesis block.  From there every node can validate every tx from block #1 all the way to current block.   As indicated above clients may also include hardcoded checkpoints.

Nodes are NOT secure.  They are inherently insecure.  You have no idea how dishonest your fellow "peer" connections are.  Hell they could all be the same attacker.  As a result Bitcoin DISTRUSTS all blocks received from the network until validated and added to the chain tracing all the way back to the genesis block.

A broadcast system for blocks wouldn't be any different.


Right, but that doesn't help at all with new blocks, which is where any attack would play out Roll Eyes.

New block is simply the tail of the block chain.  Right now a peer node just gave you a block how do you make sure it is valid?

Check blockexplorer and blockchain.info from systems on multiple ISPs.
Why? If you have an existing, valid blockchain, and you want to check all additional blocks that are sent to you, what is wrong with how it is done now? Do you even know how it is done now? I doubt it.
legendary
Activity: 1904
Merit: 1002
April 16, 2012, 07:48:59 PM
#28
How does the client invalidate the bad blocks unless it has a source of valid blocks?  The whole point here is that this is the only way to get the blockchain to some clients.

All clients have the starting source ... the genesis block.   The only way to validate block #1 is to ensure it meets block requirements and has the block hash from block #0.   As such all full-clients must include the genesis block.  From there every node can validate every tx from block #1 all the way to current block.   As indicated above clients may also include hardcoded checkpoints.

Nodes are NOT secure.  They are inherently insecure.  You have no idea how dishonest your fellow "peer" connections are.  Hell they could all be the same attacker.  As a result Bitcoin DISTRUSTS all blocks received from the network until validated and added to the chain tracing all the way back to the genesis block.

A broadcast system for blocks wouldn't be any different.


Right, but that doesn't help at all with new blocks, which is where any attack would play out Roll Eyes.

New block is simply the tail of the block chain.  Right now a peer node just gave you a block how do you make sure it is valid?

Check blockexplorer and blockchain.info from systems on multiple ISPs.
donator
Activity: 1218
Merit: 1063
Gerald Davis
April 16, 2012, 07:43:30 PM
#27
How does the client invalidate the bad blocks unless it has a source of valid blocks?  The whole point here is that this is the only way to get the blockchain to some clients.

All clients have the starting source ... the genesis block.   The only way to validate block #1 is to ensure it meets block requirements and has the block hash from block #0.   As such all full-clients must include the genesis block.  From there every node can validate every tx from block #1 all the way to current block.   As indicated above clients may also include hardcoded checkpoints.

Nodes are NOT secure.  They are inherently insecure.  You have no idea how dishonest your fellow "peer" connections are.  Hell they could all be the same attacker.  As a result Bitcoin DISTRUSTS all blocks received from the network until validated and added to the chain tracing all the way back to the genesis block.

A broadcast system for blocks wouldn't be any different.


Right, but that doesn't help at all with new blocks, which is where any attack would play out Roll Eyes.

New block is simply the tail of the block chain.  Right now a peer node just gave you a block how do you make sure it is valid?
legendary
Activity: 1904
Merit: 1002
April 16, 2012, 07:07:38 PM
#26
How does the client invalidate the bad blocks unless it has a source of valid blocks?  The whole point here is that this is the only way to get the blockchain to some clients.

All clients have the starting source ... the genesis block.   The only way to validate block #1 is to ensure it meets block requirements and has the block hash from block #0.   As such all full-clients must include the genesis block.  From there every node can validate every tx from block #1 all the way to current block.   As indicated above clients may also include hardcoded checkpoints.

Nodes are NOT secure.  They are inherently insecure.  You have no idea how dishonest your fellow "peer" connections are.  Hell they could all be the same attacker.  As a result Bitcoin DISTRUSTS all blocks received from the network until validated and added to the chain tracing all the way back to the genesis block.

A broadcast system for blocks wouldn't be any different.


Right, but that doesn't help at all with new blocks, which is where any attack would play out Roll Eyes.
legendary
Activity: 1708
Merit: 1007
April 16, 2012, 06:49:43 PM
#25

A broadcast system for blocks wouldn't be any different.


Excepting that there is only one source for the blockchain, no it wouldn't.  Part of the normal client's security model involves getting blocks from differnet sources, and validating them so that they all fit into the same blockchain.  That's where the trust of a datacasting company would come in, for it's possible that such a company that turned to the dark side, (or a hacker gets ahold of the private keys in order to fake being the company) then it's possible for the attacker to send faked blocks to a high value target that also happens to be a costumer.  In this way, the attacker could theoretically create fake blocks that permits himself to send himself his own bitcoins, and then spend them again at the attacked vendor.  Sort of like a delayed double spend attack.  Actually, this might be possible regardless, so I doubt that anyone selling high value items for bitcoin (say a brand new car) is going to be satisfied with just a couple of block verifications.  Odds are high that such a vendor could justify an Internet downlink of their own right, and that buying in bitcoin is going to both require personal identification (ever tried to buy a car for cash at a dealership?  It's not cash an carry) and at least three verified blocks before you get to leave with the new car.  This datacasting idea is more about the little vendors.  Like the guys who sell hot dogs at the street corner downtown.  He's more likely to use BitcoinSpinner on an Android than a datacasting company, but the concept is similar.  He's not going to be running a full client under his hot dog tray paying 4G data rates to keep up.  Eventually even 4G isn't going to be able to keep up anyway.
Pages:
Jump to: