[ul][li]I started exploring the source code.[/li]
[li]Tried to compile with Qt5, doesn’t work.[/li]
[li]Found out that Bitcoin already ported to Qt5.[/li]
[li]Investigated if it would be easy to merge from the bitcoin repo.[/li]
[li]Found out that the branches and tags are a mess! it’s not clear which are the peershares branches/tags, which are the peercoin branches/tags and if there is a bitcoin branch.[/li][/ul]
This complete mess, especially the branching and tagging mess, makes me feel that I’m completely on my own when starting a peershares project.
That I’ll be fully responsible to keep up to date with upstream bitcoin and peercoin changes.
Peershares was developed as a platform to create DAOs/DACs. Jordan Lee received funding to build NuBits, but before that could be done, he first needed to build Peershares. Nu was built off of the Peershares platform. It is however not the responsibility of Jordan Lee or his team to keep the Peershares repo up to date. His ultimate goal was to build Nu, not to provide this platform free of charge, therefore all further development by his team has been spent on Nu itself, rather than Peershares.
A new Peershares based DAO is also currently being built by Jordan, which is called B&C Exchange. Rather than pull from the outdated Peershares repo though, they used the NuBits repo, which was more up to date. I’m not sure they will be updating Peershares unless there is a good reason. Good developers are limited in number and they’ve been put to work on the DAOs we already have and are currently building.
Maybe in the future it can be updated as more developers are attracted to Peershares because of the success of Nu and B&C and other DAOs we build. For now though, the most updated Peershares repo is Nu, except for the fact that it has things built into the protocol which are specific to Nu and wouldn’t apply to other DAOs. For example, it has code which Peershares lacks like motion voting, custodial grants to print more shares, but it also has things that don’t apply to other DAOs like parking interest rates. You would need to take the extra stuff out that you didn’t need.
pro: Actively maintained
con: More modifications to get a pure PoS system[/li]
pro: Almost ready to start implementing my business logic on
con: I need to maintain the peershares code (that I did not write)[/li]
pro: A stable credit system and a shareholders system in one go
con: steeper and higher learning curve[/li][/ul]
Forking peershares seems to get me started the quickest.
But NuShares/NuBits might give me a better and product.
So I guess I’ll start investigating that option for a while.
There is one possibility where I could see the Nu/B&C team updating the Peershares code. B&C Exchange will be split into two trading categories, cryptocurrencies and cryptoequities. Peershares are in the cryptoequities category. I have made the case that updating Peershares and providing a platform for people to start their own cryptoequities could help B&C Exchange by profiting from the trading fees. Essentially, we would provide a platform for cryptoequities and also a place to trade them. Even if that did happen though, I wouldn’t count on it happening anytime soon, at least until after B&C is released.
Fork Nu and start from there. Disable the things you don’t need. Nu has had far more security improvements than Peershares. The 2.1 codebase is still being polished and there are some issues, but by the time you’ve familiarized yourself with the code base we should have it all fixed. Just disable anything you don’t need. Motion voting is a huge positive to have and Peershares doesn’t have it. Even if it takes a bit longer to figure things out your project with be safer starting from Nu.