Bitcoin Forum
April 30, 2024, 01:28:36 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Can somebody help me understand SPECTRE by daglabs  (Read 145 times)
lizardbtc (OP)
Full Member
***
Offline Offline

Activity: 448
Merit: 109



View Profile
February 20, 2018, 04:17:01 PM
 #1

I've heard about this way back but only recently started to read more about it.

For those who do n't know what I am talking about check these links: https://www.daglabs.com/ , https://eprint.iacr.org/2016/1159.pdf

Tho one thing is not clear to me. I get it in this protocols miners are like going rouge and simply mine as many blocks as they can and thus creating this graph of blocks. The problem that I see is that it is not neccessery to mine blocks which will contain the same transactions in them. As I see this it is just puting more weight on the network in terms of how large this DAG can actually be. Yes it can scale but then to run a node you will have to have good internet speed and a lot of space on your hard drive with some of these blocks being totaly unnecessary added to the network.

Can somebody shed some light and explain me why is this proposal good or you belive it is bad, why so?
1714483716
Hero Member
*
Offline Offline

Posts: 1714483716

View Profile Personal Message (Offline)

Ignore
1714483716
Reply with quote  #2

1714483716
Report to moderator
1714483716
Hero Member
*
Offline Offline

Posts: 1714483716

View Profile Personal Message (Offline)

Ignore
1714483716
Reply with quote  #2

1714483716
Report to moderator
1714483716
Hero Member
*
Offline Offline

Posts: 1714483716

View Profile Personal Message (Offline)

Ignore
1714483716
Reply with quote  #2

1714483716
Report to moderator
Each block is stacked on top of the previous one. Adding another block to the top makes all lower blocks more difficult to remove: there is more "weight" above each block. A transaction in a block 6 blocks deep (6 confirmations) will be very difficult to remove.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714483716
Hero Member
*
Offline Offline

Posts: 1714483716

View Profile Personal Message (Offline)

Ignore
1714483716
Reply with quote  #2

1714483716
Report to moderator
1714483716
Hero Member
*
Offline Offline

Posts: 1714483716

View Profile Personal Message (Offline)

Ignore
1714483716
Reply with quote  #2

1714483716
Report to moderator
1714483716
Hero Member
*
Offline Offline

Posts: 1714483716

View Profile Personal Message (Offline)

Ignore
1714483716
Reply with quote  #2

1714483716
Report to moderator
Random Seller
Newbie
*
Offline Offline

Activity: 42
Merit: 0


View Profile
February 20, 2018, 05:49:48 PM
 #2

I've heard about this way back but only recently started to read more about it.

For those who do n't know what I am talking about check these links: https://www.daglabs.com/ , https://eprint.iacr.org/2016/1159.pdf

Tho one thing is not clear to me. I get it in this protocols miners are like going rouge and simply mine as many blocks as they can and thus creating this graph of blocks. The problem that I see is that it is not neccessery to mine blocks which will contain the same transactions in them. As I see this it is just puting more weight on the network in terms of how large this DAG can actually be. Yes it can scale but then to run a node you will have to have good internet speed and a lot of space on your hard drive with some of these blocks being totaly unnecessary added to the network.

Can somebody shed some light and explain me why is this proposal good or you belive it is bad, why so?

This proposal changes the trade off needed to achieve faster confirmation times.

Assuming we don’t have lightning or any off chain solutions the classic trade off is between security and scalability. This is because as you lower blocktime or increase block size there comes a point where security is significantly reduced.

The proposal changes the trade offs to a trade off between (network & storage) and security. This proposal would allow significantly lower block times which in turn would significantly reduce confirmation time but the cost is larger storage capacity and more bandwidth.

In my opinion, this change would significantly increase confirmation speed but lower the amount of nodes due to the higher requirements. But I digress, it really depends on the rate of growth of storage capacity and network bandwidth.
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!