You are viewing a single comment's thread from:
RE: Blockchain as a Backend Part Two: Lateral Forking Following Content Types, Agnostic Rewards
Great write!
I guess I will add another category to my collection - Steem blockchain explained :)
What about golos? How does golos fit into your diagram?
And any future spinoffs ... ?
Golos is an almost identical clone of Steemit, just a copy / paste, the main differentiator being the language. There are a few economical differencies but not much. As I understand, they're still on the hyper-inflationist model Steemit had until hardfork 16, but they're working towards implementing the new one too.
Golos could use the publishing side chain, just like Steemit, in the new architecture.
That's what I assumed - sidechain instead of clone.
What about independence from the main chain? Is the sidechain independent? Or is it just piggybacking on the main chain? With independence you gain freedom of act and choice. And take on the burden of administration :)
Where do sidechains store data? Sorry if I overlooked this one ...
The sidechains will process - in my approach - only specific data. For instance, in the case of the publishing sidechain, it will be responsible only for articles and blog posts. So that's what it will store, with a reference to the owner account.
Account management and rewards processing should be done on the main blockchain to preserve the monolithic aspect of the operations.
Please be aware that this is just my own view of how things should be, after just a few months of studying the processes here, and with a minimal knowledge of the code base. The creators of Steem/Steemit know much better than me if this will work out or not, what I wrote is just a bunch of suggestions. They may, or may not function in the current setup.
Of course, there can be various and different approaches.
So, specific sidechain data would be stored in the json-metadata field?
And sidechain logic would search, filter and act on this specific data? And create / modify it, of course.
Because ... you wouldn't want and won't be allowed to change the block / transaction structure itself.
For example - #steemgnome coordinates :)
@dragosroua
OK, add-on data fields and logic upon them. I got it, TNX.
Back to real work now :) Write you ...
Nope, the json metadata field will be just for metadata and it will remain as it is.
Each sidechain should host only data type specific operations. Right now you have in the main blockchain operations for posting a specific article, a comment, for retrieving comments and tags, etc. These should be transferred in the sidechain completely, and the sidechain should only sync with the main blockchain a specific data type:
{id:unique_id, data_type: publishing, account: acct_id}. Or something like that.The task management sidechain should have native functions for adding tasks, projects, retrieving tasks and projects based on various metadata (due date, context, etc) and it should synchronize with the main blockchain, again, just a specific data type:
{id:unique_id, data_type: task_management, account: acct_id}.The account management and rewards processing should be somehow centralized (although I don't like the word, it just means they shouldn't be part of the sidechains to avoid bloating).