Be careful going down the 'fair route' i.e. a long PoW phase unless you have a seriously good retargeting system. The native Peercoin and Novacoin retargeting on every block doesn't work anywhere near as well as KGW, DGW, Digishield etc.

A short PoW stage may help to get and keep miners interested long enough to sustain high hash rates and add some resistance to attackers using pool-hopping tactics. These attackers love to drive the difficulty through the roof, stop mining suddenly, leaving the blockchain stuck. It happens a lot with new coins and it causes a lot of problem when legitimate people struggle to find blocks; they will just give up very quickly.

Also, a lot of miners seem to like to mine a coin for a while and move on to something else fairly soon.

I've tried what you suggested and it syncs here with or without nodes added to .conf.

It looks it's not syncing at times because blocks aren't been found often enough due to the difficulty being 7 and hashrate is pretty low at present, so the network is stuck on blocks for a while. Looks like it may be back to the drawing board for the difficulty calculation.

Right let's set this straight. The Scrypt blockchain was abandoned only when nobody was mining it at all. Not a single miner touched that chain for weeks.

I was conscientious of people who had mined the Scrypt blockchain and kept it running for almost 6 months because of other people's interests. In February, I stated to the people who were community co-devs as well as being miners, that the premine was too high and that it would be much better to start afresh but they wouldn't accept this, so it continued as before and until it was effectively dead. Relaunching was not a decision that was taken lightly but there was no other option available and it will not be done again.

If you were a miner wasted electricity in the process, then I'm genuinely sorry for this but the indications were clear from the very start that it would not have been successful or widely adopted. It was pointless even trying to market it and if it's of any consolation, I wasted a lot of money too on maintaining nodes, not to mention bounties where BNT was not wanted, but the biggest investment was an absolutely ridiculous amount of time keeping things going.

Coin swaps would have resulted in another large premine which would defeat the whole object of doing a relaunch to resolve issues that were prevalent from the original launch.

The ANN shows the percentage as a decimal value and how much was premined. I'll update this for you and make it more clear that it was only 50,000 out of 10 million coins.

Bitnote was relaunched with a completely new blockchain and a 0.05% premine. The old blockchain and thread is obsolete now.

Just wondering if the problem is still there if you could try deleting the blockchain from your server and recompile the daemon to see if picks up the right chain.

The nodes are currently showing to be on the same block as your pool though.

Looks like someone is back doing attacks and there could be a blockchain fork if different amounts are being displayed. The seed nodes are working and it should settle back to right chain at some point in the near future.

If for any reason your nodes aren't being picked up, try addnode=95.85.37.201 and addnode=188.226.180.208.

Hard fork has been released.

The subsidy rates have been increased and are very generous for early miners plus the PoS interest rate is absolutely colossal!!!

The wallet has been uploaded again as the Qt.exe file and another zipped folder added.

It is same the blockchain from the re-release and it hasn't started again. The first 1440 blocks are the original ones and took several days to mine because of the difficulty spikes, which should hopefully now be fixed.

On mega try downloading as standard rather than .zip and see if it works. I'll put a dropbox link up straight away.

The code has been rectified and the blockchain is now working.

The source code is here: https://github.com/BitNote/bitnote

Windows wallet here: https://mega.co.nz/#F!mdYGDAhY!TvNu89ZWdCpXjBebr-EYCQ.

Mac and Linux wallets will be available later today hopefully.

THE NORMAL PoW SUBSIDY OF 50 BNT PER BLOCK HAS ONLY JUST STARTED SO IF YOU INTERESTED IN MINING , NOW WOULD BE A GOOD TIME TO START WHILE THE DIFFICULTY IS VERY LOW!!!

I had deleted everything inside the thread including the announcement and title and have put back now.

My sincerest apologies for removing posts. In all honesty it was a moment of stupidity and should not have been done.

The release has been plagued by non-stop attacks to spike the difficulty up which causes the blockchain to hang completely. The native retarget for each block just isn't effective. I am working on a solution to fix the issue but it's causing all kinds of compilation errors so can't be released until it works.

Bitnote is now released with a completely new blockchain.

THE NORMAL PoW SUBSIDY OF 50 BNT PER BLOCK HAS ONLY JUST STARTED SO IF YOU INTERESTED IN MINING - NOW WOULD BE A GOOD TIME TO START WHILE THE DIFFICULTY IS VERY LOW. HARD FORK WITH 250% ANNUAL INTEREST HAS BEEN RELEASED!!!

To ensure a fair start, blocks rewards were set to 1 coin per block for the first 1440 blocks to enable more mining pools to be set up. The normal block reward will be 50 Bitnotes for the first 3 months and tapered after that.



Specification:

• X11 Pow/PoS
• 10 million maximum coins
• PoW stage for 3 months
• 1 coin per block for first 1440 (approx 2 days)
• 50 coins per block
• 2.5% annual interest
• 6 confirms for sending/receiving
• 100 confirms for mining
• 0 starting difficulty

Website
http://www.bit-note.org/

Ports:
RPC - 43661
P2P - 43662

Windows Qt-wallet

VirusTotal Detection Ratio: 0 / 53

SHA256:   1e6f91a2ca62b3d4ce9b6134a4363f9fcab29f56f172a55c07faea5421afaf86
MD5:   3c8750fb1195733f8374a69c743ab235

https://mega.co.nz/#F!mdYGDAhY!TvNu89ZWdCpXjBebr-EYCQ

(Please download wallet using 'standard' download not 'zip' as the file is already zipped and you may received corruption) warnings.

Dropbox Link
https://www.dropbox.com/s/kqik816ad1ewbtl/bitnote-qt.zip


Linux Qt-wallets and self-compile instructions:

https://mega.co.nz/#F!DMZ3FayS!A-MrisF271fS4A0Q1GRtrQ

32 bit Wallet - VirusTotal  Detection Ratio: 0/52

SHA256:   7d75191bbadaf0f5968fb92544cec4d0132d6fd853bb6b0f5302bb2546779462
MD5:   1aac7e35c4c4b0adc010d66170ddc26e

64 bit Wallet - VirusTotal  Detection Ratio: 0/52

SHA256:   e1be194874ea735eef6c834f43a1109c65f3367fb2e94791088ae205e0471f1e
MD5:   c9a6df0458e4873b3d8774834aac2a4c


Mac Wallet:
Coming Soon
https://mega.co.nz/#F!7RByiLQB!az3RLYRKxLCtsOlh_ZcA3Q


Github Source:
https://github.com/BitNote/bitnote


Current Bounties:
New Logo Design!!! 500
Block explorer   250


Sample Config File:


Mining Pools
http://webcoin.me:8080
http://bitnote.minerpools.com/


Mining
Download X11 mining software here:  
This software may generate virus scan false positives so you will need to create a rule/exception to prevent it being intercepted by your antivirus software. Extract the minderd files and create a new file with Notepad. In this files, enter the following:

Solo mining through wallet

Or

Pool mining


The username and password should be the same as those entered in your bitnote.conf file. Save this .text file as bitnote.bat - making sure that you choose from the 'Save as type' drop down box 'All Files' otherwise it will be saved as a text file. Place bitnote.bat batch in the same folder as minerd.exe but don't open up the file yet!

Using a CMD window, navigate In the folder where you have saved the bitnote Wallet, hold down shift key and right click on an empty space. Select 'Open command window here' and in the CMD Prompt window, type:


This will instruct your wallet to open with the -server switch and enable minerd to work its magic. Now go back to the folder where minerd was extracted and open up bitnote.bat and minerd should now start mining.


There is a 50,000 BNT premine which is 0.5% as percentage and 0.05 as a decimal of the total 10 million BNT that will ever be produced. This is for bounties, marketing and future development work.

You'll need to update the SSL version to 1.0.1.g on any nodes you run and recompile the daemon (the easy part).

Then you need also need to upgrade SSL on Windows, Linux and OSX (if you have wallets for these) and recompile the wallets - which is probably not what you wanted to hear

I've been watching your posts and have resisted the temptation to get involved until now. You have breached a major barrier of trust when you openly talk about market manipulation and doing so says a lot about your motivations as a developer and the sneaky ways in which you operate.

A free T-shirt for only 0.1 BTC.

Basically, that's $43.40 for a T-shirt and a vote. What a fucking bargain - I'll take 100 of 'em.

Sorry but Orbitcoin should not be featured on that list. It does have its problems but to be regarded as a dead coin is not only extremely unfair but absolutely untrue.

Orbitcoin still has a market capacity that can be traded in US Cents (not single satoshis) and its acting/stand-in a dev, ghostlander, does actually appear to be a developer, not a mere 'cloner' like 99% of the current so-called devs in here. The premine by the original creator was absolutely ridiculous but people know about this and still support it. The community is also very active over on cryptocointalk.

If it's of any help, try again with a virtual machine running Windows 7 or even XP.

For simplicity's sake, the easiest compile route is probably the Qt 4.8 libraries as these requires less patching and they CAN build static wallets that are much more stable than dynamically linked ones i.e. those which need the extra DLLs/libraries. Nothing is worse than when you've spent ages getting a wallet compiled and it crashes every time on start or exit.

Follow the compile and dependency instructions in the thread posted above to the letter (well almost) and make sure you scroll down to the qt 4.8 section! You don't need protoc, libprotobuf, libpng or qrencode for building Litecoin wallets and NOT adding these will reduce the likelihood of errors that will only complicate matters.

Each time you come across an error, google the last few lines of your error messages one at a time (starting with the last line) and if this fails to provide a solution, go to the top lines and try these. Most of the issues are caused by the links to deps not being correctly stated in the qt.pro file. Whatever problems you have, many other people will have faced the same issues and google is your #1 friend for finding issues that other people have posted help requests for.