Are you a graphic designer?
Are you a graphic designer?[/quote]
Not by trade though I am capable.
You’ve done great work for the community. Are you able to join the effort for this project?
[quote=“saeveritt, post:52, topic:3913”]Not by trade though I am capable.
You’ve done great work for the community. Are you able to join the effort for this project?[/quote]
Forgot to reply to this. I am not a graphic designer. I have somebody though that does work for me. He created all of Peercoin’s logos.
[size=14pt]Update 28th of July 2016[/size]
No demo update but an announcement:
Key derivation pattern will change in next demo to follow the recommendations in:
Just to keep you guys informed.
PeerKeeper developement has become less visible, because I’ve been working on PARS and am now investigating some script possibilities.
I’m going to bring some smart contracts to Peercoin!
Just like with PARS, the chain is ready for this, I just need to prove it’s working.
PeerKeeper development will definitely continue as I need PeerKeeper to solidly demonstrate all of this.
So please keep supporting, the development didn’t stop, it just got a bit less visible.
Just another HEADs up.
I’ve implemented BIP44 & SLIP44 compliant key derivation https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki & https://github.com/satoshilabs/slips/blob/master/slip-0044.md
Now working on the unit tests, so everyone can test browser compatibility.
I’ll be on vacation next week, but you can expect another demo update before the end of the month!
From that version you can start using the keys, as a JSON export option is implemented already.
Interesting, but how is this relevant to this thread?
[size=14pt]Update 28th of August 2016[/size]
[ul][li]You can now export your private keys, which means that you can start using the generated addresses in other clients.
Keep in mind that PeerKeeper still doesn’t fetch real balance data, that’s for next iteration.
[li]Firefox compatibility is fixed. (it was caused by this issue: https://github.com/feross/buffer/issues/131)[/li]
[li]BIP44 & SLIP44 key generation is implemented and tested. Meaning that from now on, the addresses generated using a rootkey and password combination will never change.[/li][/ul]
[ul][li]Fetching address balances from block explorer[/li]
[li]Implementing send transactions[/li][/ul]
In short, we’re getting close to a functional wallet.
Looking forward to your feedback and
please keep supporting this project.
I posted an update in the following places…
Twitter - https://twitter.com/PeercoinPPC/status/770663436397142017
Facebook - https://www.facebook.com/Peercoin/photos/a.552204974871951.1073741830.532627103496405/1117184255040684/?type=3&theater
Bitcointalk thread - https://bitcointalk.org/index.php?topic=793142.msg16090727#msg16090727
Interesting, but how is this relevant to this thread?[/quote]
Can we use browser plugin to block ads?
Just an idea. I think you should use the thread title as a news dispersal mechanism. For example, cut the title short where it only says [ANN] PeerKeeper - and then after the dash include a short summary of the latest news and constantly change it when there is something new to report. For example…
[ANN] PeerKeeper: BIP44/SLIP44 & Key Export Implemented - Testers Needed
Thanks, changed the title.
Please guys, any feedback helps the project!
A small update
I’m working on a sub project called “PeerScript Labs”, it serves as a testground for Smart Contract support in PeerKeeper.
PeerScript Labs will be published in the near future.
Please note that this is all part of the “PeerKeeper - PeerAssets” ecosystem, meaning that these projects are still in progress!
A key BIP32 compatibility issue is found in bitcore-lib https://medium.com/@alexberegszaszi/why-do-my-bip32-wallets-disagree-6f3254cc5846
PeerKeeper shouldn’t be affected by this, but I’ll make sure to double check it.
Is this still in development?
Yes it is.
I’ve been working on peerscript-labs and peerassets lately, as these transaction types will be integrated in PeerKeeper.
And don’t forget that PeerKeeper is a crucial component to PeerAssets, so it is still going on!
Why PeerKeeper does not use brainwallet passphrases!
PeerKeeper status update.
My focus is shifting back to PeerKeeper.
However, since there is no decent block explorer on testnet, I started building a minimal block explorer that indexes only the bare minimum for PeerKeeper operation.
So this won’t be a full featured block explorer, but one that can be run locally (or centralized remotely) next to a ppcoin node and that is light on resources.
It’ll eventually also provide the functionality needed to allow in browser minting.
This project will be modular, so that it’ll later also serve as a PA node and that the PeerKeeper and PA modules can be switched on and off independently.
I’ll keep you guys posted!
<3 workin’ like crazy