RE: Subchains and Multi-Chain Matrices for Massive Blockchain Data Propagation by krnel

View this thread on: hive.blog | peakd.com | ecency.com

Viewing a response to: @dantheman/re-krnel-subchains-and-multi-chain-matrices-for-massive-blockchain-data-propagation-20161201t165337732z

blockchain · @krnel · Dec 1 '16

Thanks for the clarification.

Steem may be able to handle unlimited read requests, but the nodes that host the data and have to deliver those requests, is the issue when you are talking about huge data files like movies, or the size of the blockchain itself. I still see that as an issue, when talking about nodes hosting all the data on one chain. A million terrabyte ledger is not viable. That proves how size is an issue, and why subchains are required. You break it up into different databases, which is how the whole internet is structures, networks of networks. I was just making the case that a blockchain can't stay one blockchain for all data, as it's not possible in the long term.

👍 ivanvan

`author`	krnel
`permlink`	re-dantheman-re-krnel-subchains-and-multi-chain-matrices-for-massive-blockchain-data-propagation-20161201t172551903z
`category`	blockchain
`json_metadata`	{"tags":["blockchain"]}
`created`	2016-12-01 17:25:51
`last_update`	2016-12-01 17:25:51
`depth`	2
`children`	2
`last_payout`	2017-01-01 16:38:27
`cashout_time`	1969-12-31 23:59:59
`total_payout_value`	0.000 HBD
`curator_payout_value`	0.000 HBD
`pending_payout_value`	0.000 HBD
`promoted`	0.000 HBD
`body_length`	692
`author_reputation`	1,343,547,270,297,082
`root_title`	"Subchains and Multi-Chain Matrices for Massive Blockchain Data Propagation"
`beneficiaries`	`[]`
`max_accepted_payout`	1,000,000.000 HBD
`percent_hbd`	10,000
`post_id`	1,890,808
`net_rshares`	520,883,986
`author_curate_reward`	""

properties (23)vote details (1)

voter	weight	wgt%	rshares	pct	time
ivanvan	0 B		520,883,986	100%

@dantheman · Dec 1 '16

Large datasets are best stored in a DHT.  The business logic is hard to compress or divide once you get down to sequence dependent operations. 

A large ledger can be distributed via DHT,  but the interpretation of the ledger requires the active state. 

The structure you describe for a block chain database records is different than how we organize it.

👍 ivanvan, johnathanhenry

`author`	dantheman
`permlink`	re-krnel-re-dantheman-re-krnel-subchains-and-multi-chain-matrices-for-massive-blockchain-data-propagation-20161201t173624045z
`category`	blockchain
`json_metadata`	{"tags":["blockchain"]}
`created`	2016-12-01 17:36:24
`last_update`	2016-12-01 17:36:24
`depth`	3
`children`	1
`last_payout`	2017-01-01 16:38:27
`cashout_time`	1969-12-31 23:59:59
`total_payout_value`	0.000 HBD
`curator_payout_value`	0.000 HBD
`pending_payout_value`	0.000 HBD
`promoted`	0.000 HBD
`body_length`	354
`author_reputation`	240,292,002,602,347
`root_title`	"Subchains and Multi-Chain Matrices for Massive Blockchain Data Propagation"
`beneficiaries`	`[]`
`max_accepted_payout`	1,000,000.000 HBD
`percent_hbd`	10,000
`post_id`	1,890,883
`net_rshares`	571,009,316
`author_curate_reward`	""

properties (23)vote details (2)

voter	weight	wgt%	rshares	pct	time
johnathanhenry	0 B		50,125,330	76%
ivanvan	0 B		520,883,986	100%

@krnel · Dec 1 '16

Alright, I'm more talking about the node itself that has to download the blockchain ledger. It's not manageable as one single blockchain ledger when it gets too big. That was my main issue. Thanks for the feedback and clarity.

properties (22)