This thread will serve as “sidechain” to main Fazon thread, with purpose of holding discussions while providing more information about details. All of this is to keep the main thread clean and readable.
Main thread: http://www.peercointalk.org/index.php?topic=3247.0
Example of submission using template 1.0:
Name
Descriptive and unique.
Lightweight Multi-platform Peercoin Wallet
Summary
Max 3 sentences.
Develop and deploy a secure Peercoin wallet that can be used on multiple platforms. The purpose is to provide the means to safely spend and receive peercoins with focus on ease of use.
Full description
Concise explanation or url with documentation.
Develop and make available, a wallet that programmed in HTML5. Keys should be generated (from seed) and stored locally. The application should be lightweight and not communicate directly with the network. Instead the application should use trusted nodes to do the heavy lifting. The idea is to create a wallet that is very easy to start using even for the novice user, unfamiliar to crypto currencies.
Benefit for community
Max one paragraph.
By making it easier and more available for new and existing users to transact in peercoins, we think this could help drive adoption.
Usage example
If not applicable leave empty.
User hears about Peercoin for the first time, is provided a link and a few seconds later has a wallet ready to be used.
Known blockers
If unknown leave empty.
Need a port of Pycoin (http://www.peercointalk.org/index.php?topic=3219.msg30462#msg30462)
Requirements and dependencies
Provide links when appropriate.
Requires access to a trusted Peercoin node API. Depends on Pycoin (http://www.peercointalk.org/index.php?topic=3201.msg30379#msg30379).
Prior work
What differentiates this from similar things? Provide links when appropriate.
To our knowledge, there are no other multi-platform wallets for Peercoin. There are many such wallets for Bitcoin, which could be used for inspiration. Electrum and Hive in particular, because they provide solutions for light-weight wallets and locally secured data.
Estimated cost or man hours
If unknown or not applicable leave empty.
Additional comment
Please make sure it doesn’t fit under the headers above first.
If possible, add support for Peershares.
I know the following is already mentioned as goal of Project Fazon but to me this really lacks and would be easy to achieve, or even a dependency to Fazon.
Name
Compile a list of libraries, software products(if possible with github links), etc etc which are already there to support new developers get what they need.
Summary
A neat collection on libs/gems/tools software engineers could use to check if the libraries they might need for a project is already there. Or better, give them inspiration what can be done with the libraries at hand.
Full description
Allright, I’ve got quite extensive programming experience and some cool idea’s, though I’ve got no clue what libraries are allready around which I could use. This holds me back, and makes projects more like pipedreams instead of real projects.
What would help is a list, or a wiki page, or something which locates all the free/open libraries the dev could use.
Benefit for community
More projects which support peercoin, or are even exclusively for peercoin!
Usage example
See above.
Requirements and dependencies
A topic to locate what we’ve already got?
What you described is exactly what Fazon is about, to map the ecosystem.
You will get it when I draw first draft of map.
For now, you can help with submitting the already completed libraries to main thread, so I can map them.
Please notice that Fazon is not just about new stuff, but about mapping the old stuff too.
I would love to see a python library not to say a python wallet for Peercoin. With it a lot of applications can be made by developers who don’t need to understand exactly how POS works. However I don’t think you could get the lib implemented for 1-2k USD for a pro developer. The bottle neck is that there are only a few developers who understand Peercoin well enough to do the ground work. All we have are part-time devs who probably have already committed their time on existing projects.
That is why documentation on core protocol would come handy, so developers don’t need to go through the code to understand it.
With it development is cheaper too.
I don’t think that lib will be implemented with 1-2k USD, but realistically that is how much we can offer.
Please test, I’m experimenting with hosting the map on Google drive.
https://drive.google.com/file/d/0B36ZFaw9XvLiMDhjeElvVUthdWM/edit?usp=sharing
If it is not automatic, please open with “Mindmup”.
edit:
Due to Google Drive API limitations, even files that are made completely public require a Google ID (so people won't be able to access them without logging into Google and authorising MindMup). If you want to share something with the whole world, we suggest saving to Drive while you are working on it, but then switching to our public storage before sharing (select MindMup from the save options menu).
yes it works, manually, downloading and opening it , not automatic (for me)
I guess the Mindmup needs to have access to google account. I’ll try hosting it on github.
Yeah, this needs to be made to work automatically. I don’t expects lots of people to be downloading files just to view this. Is there any way to do that?
@Sentinel
It is going to be automatic. Just let me try all the different solutions for it. Github way seems promising.
Template 1.5 proposal:
removed:
[Requirements and dependencies]
added:
[i]
[home url/git]
[Needed skills]
[Dependencies]
[Optional dependencies]
[/i]
[Name]
Descriptive and unique.
[url]
[Status]
Work in progress/Completed/Not Completed
[Summary]
Max 3 sentences.
[Full description]
Concise explanation or see url.
[Benefit for community]
Max one paragraph, be imaginative.
[Usage example]
If not applicable leave empty.
[Known blockers]
This applies to non existing libraries that are direct dependencies, or bugs that need fixing.
If unknown leave empty.
[Needed skills]
Skill needed to complete the project.
[Dependencies]
Hard dependencies which are essential to this project.
[Optional dependencies]
Optional dependencies that would help/ease the development if available.
Example for this would be documentation of Peercoin protocol which would help a lot of projects.
[Estimated cost or man hours]
If unknown or not applicable leave empty.
[Additional comment]
Please make sure it doesn’t fit under the headers above first.
I’ve been experimenting with this sharing of the map.
However:
Due to Google Drive API limitations, even files that are made completely public require a Google ID (so people won't be able to access them without logging into Google and authorising MindMup). If you want to share something with the whole world, we suggest saving to Drive while you are working on it, but then switching to our public storage before sharing (select MindMup from the save options menu).
So, if this platform is to be used in future (Mindmup) best is to pay for Gold. Gold costs 25$/year and it enables exporting as PDF, embedding in website (like peercoin.net) and enabling one-link viewing of the map.
If the map is to be hosted on Google drive, one needs log in to Google and allow access for MindMap app. This sounds complicated to me.
What functionality would we expect of libraries in arbitrary languages? I was thinking, maybe start with wrappers of ppcoind or so and later extent it? Therefor creating an extra ‘node’ in the graph.
And yeah, please start with protocol documentation etc.
I have official hit a wall with this mapping thing.
I can not find decent service to host the map, with all feature’s I need.
Best I could find is mindmup.com, but it is not tailored to needs of this project. Then I find my self tailoring project to fit mindmup.com instead other way around.
Also, I’m frequently frustrated by bugs and integration with say github or google-drive.
Not their fault I guess, it is just my expectations. Their product is probably superb for someone else with different needs.
Thus I propose implementation of custom mind mapping software, to scratch our itches or giving up/pausing project.
To improve visibility of this message, I will cross post it in /General and explain what exactly do I need.
edit:
more detailed thread: