[ANN] [BEE2] [BEECOIN V2] POW X11/POS Hybrid - Now With CLIENT CHAT Feature!

[soopy452000]

I'm pretty sure there are some people who care, but as Soopy doesn't care, this coin is in a trouble.

I guess I care as pretty much anyone here does mate or more , I was pretty ill the last few days and was trying to get a few nodes up before a hardfork for BeeCoin including a few updates , unfortunately I didn't receive the servers as they were promised so hoping to get them soon in the next few days. So ofcourse I do care for BeeCoin or I wouldn't even reply here if not for that matter.

Warm Regards,
~SoopY~

[SiNeReiNZzz]

I'm pretty sure there are some people who care, but as Soopy doesn't care, this coin is in a trouble.

I guess I care as pretty much anyone here does mate or more , I was pretty ill the last few days and was trying to get a few nodes up before a hardfork for BeeCoin including a few updates , unfortunately I didn't receive the servers as they were promised so hoping to get them soon in the next few days. So ofcourse I do care for BeeCoin or I wouldn't even reply here if not for that matter.

Warm Regards,
~SoopY~

Hey Soopy! 

What is the state of things ?

[gjhiggins]

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) ...

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

[soopy452000]

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) ...

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~

[TheSea]

Heплoxo бы для нaчaлa oтлaдить бyмaжник.. Я пpoбoвaл в peжимe 24 чaca дepжaть oткpытыe бyмaжники нa 8 кoмпьютepax, нo oни пocтeпeннo "cъeдaют" pecypcы cиcтeмы, ecли тoлькo пpинyдитeльнo нe oгpaничивaть иx aппeтит . C пycтым бyмaжникoм тaкиx пpoблeм нeт . Boзмoжнo yтeчкa пaмяти тoмy винoй .

[soopy452000]

Temporary Block Explorer Till the One That I'm working is finished.

http://beecoinv2.no-ip.net

or

http://www.beecoin.tk

The Client has been Checkpointed and Tested will be posting an update with it.

Warm Regards,
~SoopY~

[soopy452000]

Short Update:

BeeCoinV2 Windows Client as well as the Github has been updated to 1.0.2.

Enjoy!

Github

https://github.com/sherlockcoin/beecoinv2

Windows Wallet

https://www.dropbox.com/s/ml60v8lbfkea2sc/BeeCoinV2%201.0.2%20Windows%20Wallet.zip?dl=0

Warm Regards,

~SoopY~

[gjhiggins]

Short Update:
the Github has been updated to 1.0.2.

The recent commit regresses the version of LevelDB from 0.15 to 0.12, is that intentional?

Cheers

Graham

[SiNeReiNZzz]

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) ...

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

im very excited whats going on with beecoin in the future... 

[thoth-Atlantian]

The community still exists, I was buying Bee's off launch,
And I'm still staking and watching this thread, always forgetting logins to this site but getting new ones....
I would be buying up more bees atm if i could through Allcoin but will have to wait, I'm also happy to donate for new directions and ideas.

So this new wallet is right to set up on new comp and send over from old wallet or do both need to be updated?
be a bugger to lose em after this long, just made bank on my Long lost MINT I expect to do the same on BEE V2.

Keep up the good work this resurgence in Alts could be a slow ramp up to the good ole days 

[GREEDYJOHN]

The community still exists, I was buying Bee's off launch,
And I'm still staking and watching this thread, always forgetting logins to this site but getting new ones....
I would be buying up more bees atm if i could through Allcoin but will have to wait, I'm also happy to donate for new directions and ideas.

So this new wallet is right to set up on new comp and send over from old wallet or do both need to be updated?
be a bugger to lose em after this long, just made bank on my Long lost MINT I expect to do the same on BEE V2.

Keep up the good work this resurgence in Alts could be a slow ramp up to the good ole days  

Are you an OLD NEW-BEE?  

[cryptohunter]

what's going on with beecoin? is the chain still in good shape or is the coin broken right now. I see allcoin still have the wallet frozen.

I have still got the all of the community coins safe.

[soopy452000]

Short Update:

BeeCoinV2 Windows Client as well as the Github has been updated to 1.0.2.

Enjoy!

Github

https://github.com/sherlockcoin/beecoinv2

Windows Wallet

https://www.dropbox.com/s/ml60v8lbfkea2sc/BeeCoinV2%201.0.2%20Windows%20Wallet.zip?dl=0

Warm Regards,

~SoopY~

This update fixes blockchain issues but seems they haven't updated it , I have contacted AllCoin with regards to the same.

[gjhiggins]

BeeCoinV2 Windows Client as well as the Github has been updated to 1.0.2.

The version of LevelDB has regressed from 0.15 to 0.12, is that part of the fix?

Cheers

Graham

[oldkolobok]

Everything is good, but there is no live node, Wallet is not synchronized

[gjhiggins]

This update fixes blockchain issues

I'm curious and would like to reproduce the fix, how did you check that it is actually a fix for the blockchain issues?

I'm not in a position to check anything ...

Code:

Startup time: 07/07/15 10:43:27
Default data directory /home/gjh/.beecoinv2
Used data directory /home/gjh/.beecoinv2
dbenv.open LogDir=/home/gjh/.beecoinv2/database ErrorFile=/home/gjh/.beecoinv2/db.log
Bound to [::]:1108
Bound to 0.0.0.0:1108
Loading block index...
Opening LevelDB in /home/gjh/.beecoinv2/txleveldb
Transaction index version is 70508
Opened LevelDB successfully
LoadBlockIndex(): hashBestChain=6b5d3784d7e4d0fa7795  height=1399721  trust=17278333475265896  date=05/06/15 10:04:22
LoadBlockIndex(): synchronized checkpoint 00000d91aace98244561246182a310d7a7c58ff4b005596ca44a44f9f78219f1
Verifying last 2500 blocks at level 1
 block index           27506ms
Loading wallet...
nFileVersion = 1000200
Keys: 102 plaintext, 0 encrypted, 102 w/ metadata, 102 total
 wallet                  566ms
Loading addresses...
Loaded 85 addresses from peers.dat  2ms
mapBlockIndex.size() = 1405921
nBestHeight = 1399721
setKeyPool.size() = 101
mapWallet.size() = 0
mapAddressBook.size() = 1
ThreadRPCServer started
Done loading
ThreadStakeMiner started
ThreadMessageHandler started
ThreadOpenConnections started
ThreadSocketHandler started
ThreadIRCSeed started
ThreadMapPort started
ThreadOpenAddedConnections started
ThreadDNSAddressSeed started
Loading addresses from DNS seeds (could take a while)
Flushed 85 addresses to peers.dat  61ms
connect() failed after select(): Connection refused
IRC connect failed
IRC waiting 71 seconds to reconnect
trying connection 199.83.128.136:1108 lastseen=371185.0hrs
1 addresses found from DNS seeds
ThreadDNSAddressSeed exited
trying connection 64.251.65.98:1108 lastseen=1.1hrs
GetMyExternalIP() received [83.104.61.47] 83.104.61.47:0
GetMyExternalIP() returned 83.104.61.47
AddLocal(83.104.61.47:1108,5)
refreshWallet
ipcThread started
connection timeout
connection timeout
trying connection 149.126.74.136:1108 lastseen=371185.0hrs
trying connection 64.251.65.98:1108 lastseen=1.1hrs
No valid UPnP IGDs found
connection timeout
connection timeout
trying connection 1.34.180.245:1108 lastseen=371185.0hrs
trying connection 176.109.240.33:1108 lastseen=3008.0hrs
connection timeout
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.7hrs
connection timeout
trying connection 64.251.65.98:1108 lastseen=1.1hrs
connection timeout
trying connection 64.90.187.204:1108 lastseen=72.4hrs
connect() failed after select(): No route to host
trying connection 64.251.65.98:1108 lastseen=1.1hrs
connection timeout
trying connection 31.130.252.16:1108 lastseen=501.5hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.7hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.7hrs
connection timeout
trying connection 213.162.108.2:1108 lastseen=3060.8hrs
connection timeout
trying connection 5.9.56.229:1108 lastseen=931.0hrs
connect() failed after select(): Connection refused
trying connection 92.31.187.182:1108 lastseen=18.7hrs
connection timeout
trying connection 64.251.65.98:1108 lastseen=1.1hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.7hrs
connect() failed after select(): Connection refused
IRC connect failed
IRC waiting 138 seconds to reconnect
connection timeout
trying connection 64.251.65.98:1108 lastseen=1.1hrs
connection timeout
trying connection 176.37.195.36:1108 lastseen=231.4hrs
connection timeout
trying connection 1.34.180.245:1108 lastseen=799.4hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.7hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.8hrs
connection timeout
trying connection 64.251.65.98:1108 lastseen=1.2hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.8hrs
connection timeout
trying connection 64.251.65.98:1108 lastseen=1.2hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.8hrs
connection timeout
trying connection 77.38.15.148:1108 lastseen=3362.2hrs
connection timeout
trying connection 64.90.187.204:1108 lastseen=72.4hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.8hrs
trying connection 199.83.128.136:1108 lastseen=371185.0hrs
connection timeout
trying connection 31.130.255.16:1108 lastseen=132.3hrs
connection timeout
trying connection 149.126.74.136:1108 lastseen=371185.0hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.8hrs
connection timeout
trying connection 1.34.180.245:1108 lastseen=371185.0hrs
connection timeout
trying connection 1.34.180.245:1108 lastseen=799.4hrs
connection timeout
connection timeout
trying connection 64.251.65.98:1108 lastseen=1.2hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.8hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.8hrs
connection timeout
trying connection 64.251.65.98:1108 lastseen=1.2hrs
connection timeout
trying connection 1.34.180.245:1108 lastseen=799.4hrs
connection timeout
trying connection 64.251.65.98:1108 lastseen=1.2hrs
connection timeout
trying connection 31.130.255.16:1108 lastseen=132.3hrs
connection timeout
trying connection 64.251.65.98:1108 lastseen=1.2hrs
connection timeout
trying connection 31.130.255.16:1108 lastseen=132.3hrs
connection timeout
trying connection 112.5.180.220:1108 lastseen=501.5hrs
connect() failed after select(): Connection refused
IRC connect failed
IRC waiting 211 seconds to reconnect
connection timeout
trying connection 109.172.55.170:1108 lastseen=1.1hrs
connection timeout
trying connection 207.192.253.172:1108 lastseen=2988.7hrs
connection timeout
trying connection 64.251.65.98:1108 lastseen=1.2hrs
connection timeout
trying connection 176.37.195.36:1108 lastseen=231.5hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.8hrs
connection timeout
trying connection 89.151.165.144:1108 lastseen=2914.6hrs
connect() failed after select(): Connection refused
trying connection 92.31.187.182:1108 lastseen=18.8hrs
connection timeout
trying connection 31.130.255.16:1108 lastseen=132.3hrs

Does anyone have a synced node that has a BEE2 blockchain less than a month old?

Cheers

Graham

[TheSea]

trying connection 64.251.65.98:1108 lastseen=6.6hrs
connection timeout
received block 2d36b236d8205136d5b5
SetBestChain: new best=2d36b236d8205136d5b5  height=1441122  trust=18906515759841540  blocktrust=3848020133  date=07/08/15 20:04:32
ProcessBlock: ACCEPTED

[cryptohunter]

so how can we get this coin going again?

anyone able to sync the wallet up?

[gjhiggins]

so how can we get this coin going again?

anyone able to sync the wallet up?

Not until yesterday.

Code:

addnode=92.31.187.182:1108
addnode=1.34.180.245:1108

Cheers

Graham

[cryptohunter]

so how can we get this coin going again?

anyone able to sync the wallet up?

Not until yesterday.

Code:

addnode=92.31.187.182:1108
addnode=1.34.180.245:1108

Cheers

Graham

thanks Graham. Next week i'll be aiming to get the community wallet online and get it staking. Then i guess if there are any community left here we need to decide the best way forward from this point.

Would be great to find away to keep the coin online, stable and on coinmarket cap. So sad to see beecoin never even make it on there.