Re: [ANN] [BEE2] [BEECOIN V2] POW X11/POS Hybrid - Now With CLIENT CHAT Feature!
what the notion of official is doing, hanging around the neck of a p2p app, I really don't know.
I now see I was correct, it is a nonsensical notion. There is no such thing as official, merely a community consensus. Distributed binaries can be signed using cryptography to prevent tampering. End-users, as always, must decide for themselves how much confidence they are prepared to place in the integrity of the signer. (And there are virus-checking apps).
It's now quite clear that the US financial authorities have a firm grip of the fundamentals of different approaches to cryptocurrency. A couple of years ago FinCEN made it plain (http://www.fincen.gov/statutes_regs/guidance/html/FIN-2013-G001.html) ...
Quote
A final type of convertible virtual currency activity involves a de-centralized convertible virtual currency (1) that has no central repository and no single administrator, and (2) that persons may obtain by their own computing or manufacturing effort.
I'm currently researching the state of play with BeecoinV2 in order to put some concrete suggestions before the community (or rather, the remnants of). I shall restart the block explorer and try and find out whether the blockchain has become forked or not.
Once the state of the blockchain is determined (and, if required, adjusted) to the community's satisfaction, one of the next tasks should be to refurbish the coin and in the process, re-generate the public-private keypair that authorises the sending of broadcast CAlert messages. The original privkey is probably still held by the original dev, that situation should be rectified sooner rather than later.
The issue is: how to enable the community to control the private key. An agreed delegation could work but in order for that to function there needs to be a delegation facility, either mediated by a common-ownership community foundation or built into the wallet (either would do at a pinch).
It would be of enormous help to the endeavour if those who are still running a node posted the results from getpeerinfo, I have the code for a peer crawler which I could use to create a picture of where live BEE2 nodes still exist. (We might even be able to persuade Allcoin to cooperate in reverting to BEE, if that is perceived as desirable - the pchMessageStart characters are the actual discriminant between original Beecoin and BeecoinV2 blocks).
I don't believe there's any need to bother soopy with this, his attention seems now totally focused on Navajo and any further load from this quarter would just result in embarrassment.
Comments, objections, observations, encouragement, dissent, are all welcome.
Cheers
Graham
Hello gjhiggins ,
Thank you so very much for your kind inputs and suggestions , even though I was away from the thread , I have always been working regards to BeeCoin developments and an update was finished , checkpointed and will be delivered to the community on Sunday , I was also working on a block explorer as requested by AllCoin , AllCoin was also having an issue of high cpu usage by the BeeCoin Daemon and this was fixed by the recent update and was tested for a while now on an independent node.
Looking forward to review things again for BeeCoin and as you are now here extending support to the community as well , I m sure great things are yet to be seen.
Warm Regards,
~SoopY~