[$5000 worth in PTS] BitShares Blockchain Technical Specification [PENDING]

[bytemaster]

Hijack!

I have ported what naturalog has written so far to markdown and put it on github ("spec" branch). I'm gonna be working on this / BTS explorer tonight and didn't have access to the repo. Also I added naturalog as a contributor (both "naturalog" and "ohadasor").

https://github.com/nmushegian/BitShares/blob/spec/doc/spec.md

bitshare explorer bounty thread
https://bitsharestalk.org/index.php?topic=1829.0;topicseen


edit: bytemaster, since this is a separate branch, want to just pull it into the II/BitShares repo right now?
edit 2: nvm then you need to grant repo permissions

I am going to make this my priority task once I get Keyhotee ID registration done.

[toast]

Hijack!

I have ported what naturalog has written so far to markdown and put it on github ("spec" branch). I'm gonna be working on this / BTS explorer tonight and didn't have access to the repo. Also I added naturalog as a contributor (both "naturalog" and "ohadasor").

https://github.com/nmushegian/BitShares/blob/spec/doc/spec.md

bitshare explorer bounty thread
https://bitsharestalk.org/index.php?topic=1829.0;topicseen


edit: bytemaster, since this is a separate branch, want to just pull it into the II/BitShares repo right now?
edit 2: nvm then you need to grant repo permissions

[bytemaster]

Ack. May I suggest using markdown instead of HTML? There are plenty render-md-as-html tools, and in the meantime we can have a readable format which github will render nicely for us.

Sounds like a great idea, admits all requirements as can be seen here https://help.github.com/articles/github-flavored-markdown

I would expect there to be regular questions and a place where you are publishing your work?

[naturalog]

Ack. May I suggest using markdown instead of HTML? There are plenty render-md-as-html tools, and in the meantime we can have a readable format which github will render nicely for us.

Sounds like a great idea, admits all requirements as can be seen here https://help.github.com/articles/github-flavored-markdown

[bytemaster]

The more professional the look the better.  The easier to maintain the better.  Must work well with version control and images.


Sent from my iPhone using Tapatalk

[toast]

Interesting job. I'm starting to work on it.
How do you imagine the document?
Explaining in fluent English the classes and their relations, or more a reference-type document giving details on every class?
Initial version can be found here https://github.com/naturalog/BitShares/blob/master/doc/BitSharesBlockchainDesign.html

Ack. May I suggest using markdown instead of HTML? There are plenty render-md-as-html tools, and in the meantime we can have a readable format which github will render nicely for us.

[bytemaster]

I would like the spec to be language independent.    Talk about the data format and meaning rather than class names. 




Sent from my iPhone using Tapatalk

[naturalog]

Interesting job. I'm starting to work on it.
How do you imagine the document?
Explaining in fluent English the classes and their relations, or more a reference-type document giving details on every class?
Initial version can be found here https://github.com/naturalog/BitShares/blob/master/doc/BitSharesBlockchainDesign.html

[bytemaster]

I referred forum member naturalog to this bounty.

[bytemaster]

So far BitShares has been developed with a cowboy coding mentality.  I would design, document, and implement as I went.  We are now looking to grow this into something that can be maintained by the community and understood by all.  To this end I would like to produce a professional quality design document that is maintained as a website that can be updated by accepting pull requests via Github.    This document should be content focused and built for clarity.   Someone should be able to take this specification and implement a working BitShares blockchain with a high degree of compatibility with other independent implementations.

I have already defined the blockchain and many unit tests and there exists documentation embedded in the code right now.  I would like to capture the ideas expressed in the code and make them available and accessible to everyone.   I will be available to answer questions here in the forum about anything that is unclear.

Because BitShares has not been finalized at this point, the process of documenting the current design should help us explore undiscovered corner cases.   

This is a cooperative bounty and all submissions must be developed publicly.  I want to encourage cooperation so if you copy contributions from other members be sure to agree on how to split the bounty. If the accepted design document has any disputes about how the bounty is to be divided then Invictus will decide and take a 25% cut.  In other words, it is in everyones interest to fairly access their own contribution and resolve disputes.

This bounty is PENDING until all questions regarding the scope and requirements of this bounty can be settled.  At that point we will lock in the terms and begin the bounty.  Of course, getting a head start will benefit all.

There is also a referral bounty paid to the individual who refers anyone who wins the bounty. 

https://github.com/InvictusInnovations/BitShares/blob/master/include/bts/blockchain/block.hpp
https://github.com/InvictusInnovations/BitShares/blob/master/include/bts/blockchain/outputs.hpp