NAV price taking a serious beating as of late and gotta say I find the lack of updates...disturbing.

Good to know. Is that done by IP recognition or by "client version number" recognition?

Thanks for the quick answer, I was delving into the LGD code to see what I could find. Our ports are safe as well.

One thing I did notice while checking around is we have 2 peers on the 1.0.0 client...

Soopy, is our magic safe? I hope you know what I mean.

seems to happen when you first download the chain but after reloading wallet it showed correctly, but then next time i loaded wallet and it had to catch up same thing happened again, easy temp fix is to just reload when it is caught up to current.

                         Guys i not know what it means but, you better have a look ad this

         from today cryptsy is taking off legendarycoin because max coins mining was 10.000.000  but a week ago there deposits was around 550.000.000

         they did look ad it and some block rewards did reverse and had a amount of 600.000 a block

         when i look into the github files, i found out this from 14 april somebody did something with the coin and it has the topic note legendary coin

         but inside the files i see only orangecoin maybe its me, but something dev wrong here

        https://github.com/muddafudda/legendarycoin

        many users from cryptsy that where trading LGD lost big amount of money and did go up in smoke so i was think better warning you all

       have a nice day
        
  

 static const unsigned int MAX_BLOCK_SIZE_GEN = MAX_BLOCK_SIZE/2;
 static const unsigned int MAX_BLOCK_SIGOPS = MAX_BLOCK_SIZE/50;
 static const unsigned int MAX_ORPHAN_TRANSACTIONS = MAX_BLOCK_SIZE/100;
-static const unsigned int MAX_TX_COMMENT_LEN = 140; // LegendaryCoin: 128 bytes + little extra
 static const unsigned int MAX_INV_SZ = 50000;
-static const int64 MIN_TX_FEE = 1 * CENT;
-static const int64 MIN_RELAY_TX_FEE = 0.1 * CENT;
-static const int64 MAX_MONEY = 10000000 * COIN;
-static const int64 PREMINE = 300000 * COIN; // 3% Premine for promotion of coin
-static const int64 MAX_MINT_PROOF_OF_WORK = 7 * COIN;
-static const int64 MAX_MINT_PROOF_OF_WORK_LEGACY = 7 * COIN;
-static const int64 MAX_MINT_PROOF_OF_STAKE = 0.50 * MAX_MINT_PROOF_OF_WORK;	// 50% annual interest
-
+static const int64 MIN_TX_FEE = 10 * CENT;
+static const int64 MIN_RELAY_TX_FEE = 10 * CENT;
+static const int64 MAX_MONEY = 200000000 * COIN;			// 70 bil
+static const int64 CIRCULATION_MONEY = MAX_MONEY;
+static const double TAX_PERCENTAGE = 0.005;
+static const int64 MAX_MINT_PROOF_OF_STAKE = 0.025 * COIN;	// 5% annual interest
+static const int CUTOFF_POW_BLOCK = 10000;
+static const int START_POS_BLOCK = 9998;

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

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

Just hopped into it to see if anybody was on.  Is chat working in qt version 2.0.7 as well?