Investigate lbrycrd mode without storing claimtrie data in memory #264

Closed
opened 2019-03-28 15:57:22 +01:00 by tzarebczan · 2 comments
tzarebczan commented 2019-03-28 15:57:22 +01:00 (Migrated from github.com)

Some services, like exchanges and pools, will not care about claim trie data. Is it possible to have a mode or separate binary that's only for transactional data?

Some services, like exchanges and pools, will not care about claim trie data. Is it possible to have a mode or separate binary that's only for transactional data?
BrannonKing commented 2019-03-28 16:35:27 +01:00 (Migrated from github.com)

I like this idea, but the root hash of the trie is included in the block. I can't think of a way to compute that without the data being there, and transferring it from somewhere else could be risky. The memory improvements are coming very soon and should buy us a lot of breathing room.

I like this idea, but the root hash of the trie is included in the block. I can't think of a way to compute that without the data being there, and transferring it from somewhere else could be risky. The memory improvements are coming very soon and should buy us a lot of breathing room.
BrannonKing commented 2019-05-08 16:48:43 +02:00 (Migrated from github.com)

Closing as a duplicate of #166

Closing as a duplicate of #166
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbrycrd#264
No description provided.