As an American myself, is not BritCoin akin to me supporting a YankeeCoin? Seems offensive. At minimal unprofessional. For me, the comparison need not go further.

I do not view it as 'national patriotism' myself, again as an American. I align it closer to 'old English respect' or perhaps even 'old world respect'. I hope that is not offensive or a poorly worded attempt to convey my feeling. I do know much of the old world might not deserve respect, but certainly roots do.

This is how Sterlingcoin birthed from the UK and British Isle and grew into "... for the world". Many of the people reading this are not British. Some not even by decent. I propose this as a problem being resolved that is unique for a 'country coin'.

Steven, I get the impression from your response to my previous post that you are in an apologetic frame of mind.

I sincerely hope that is not the case, as you are the last person in the entire crypto industry who should ever feel the need to apologise for how your developments are proceeding.  Your total commitment to this project cannot and should not be questioned.

If I gave the impression in my previous post that I was being even the slightest bit disparaging about the current slow pace of progress please be assured that this was not at all my intention and do please accept my sincere apology for any unintended slight.

I think we are all well aware that the unfortunate event affecting the development and operation of the CWI infrastructure has had an adverse effect upon all of its dependent and associated coins; you can certainly not be blamed for that.

I am glad to hear that you are resolved to soldier on, but then, I never doubted that would be the case.

I will be marching alongside you every step of the way.

As I have previously indicated, I am not really a techie kind of person; I’m an accountant by profession.  Accordingly, I am not the ideal individual to comment meaningfully on proposed technical upgrades.  I will say, however, that I am a recent convert to the concept of masternodes and, if that is your preferred direction of travel, it gets my vote.

The idea of a coin swap does sound wise, but it is your decision.

Best of luck with all your endeavours.


Sterling Sentinel

Hello CryptoCanary

I am going to start the build again this weekend using db-6.1.36.NC.tar.gz. Is your Raspberry Pi working ok?

Yes, now the correct reference! By the end of the year, there will be 10,000 subscribers. If you are interested in the partnership, we can start advertising the channel and, in parallel, Sterlingoin advertising!? We will make real subscribers 30,000-50000 thousand for half a year on the channel

Yes, now the correct reference! By the end of the year, there will be 10,000 subscribers. If you are interested in the partnership, we can start advertising the channel and, in parallel, Sterlingcoin advertising!? We will make real subscribers 30,000-50000 thousand for half a year on the channel

For the 'record', I do have Windows and Mac SLG v1.6 binaries built with DB 4.8, DB 5.3, and of course the released DB 6.1. These binaries are not really public, in a perfect world we would all be using the same DB version. This is why the Mac wallet was compiled using DB 6.1 as of Sterlingcoin v1.6. It was easier to upgrade Mac users than to downgrade Windows users.

These other versions (DB 4.8, 5.3) were retained to support someone that may have portability issues. I am just making the community aware, we do have options should a Windows or Mac user ever find themselves in a situation needing them. We should be able to recover your coins in any event, regardless of DB version used initially. Again, just mentioning this so the community is aware the support capability exists. These binaries could be supplied to someone in need, so no one else touches their wallet.dat file but themselves.

Hi Sapfon. So very sorry for the slow response. I had been away for some personal matter for several days. Please do not think your issue was being ignored.

Being stuck for that long certainly means something is wrong. A few things could be the culprit. First, and take no offense to this obvious culprit, has it run out of disk space? I assume that answer is no and you would have already been aware of that. Bear with my thinking out loud.

Second, a misbehaving peer. I know this seems very unlikely given the number of peers, but it might be a quick fix and worth a minute. 1) Stop your wallet. 2) Navigate within the SLG data directory (Windows: c:\Users\Sapfon\AppData\Roaming\sterlingcoin\  or  Linux: ~/.sterlingcoin/ ) and delete ONLY the peers.dat file. 3) Start the wallet.

Third, getting into more time intensive resolutions, you may have an unconforming blockchain (you forked somehow). This does seem unlikely given the number of peers also, but troubleshooting. To check this, let's compare the block hash of the latest block you have, block 715128. The block explorer reveals this block hash as 46d11aebe6bee6f5c2cad719c1d9479ac7fca93fbc4b48402607926ca9822cab and we want to compare that to what block hash you have for block 715128. To do so from Windows, click the 'Explorer' button and input 715128 in the block number input box. Then click 'Jump to Block'. The Block Hash is the 2nd line of output. In Linux you would issue the RPC command "./sterlingcoind getblockhash 715128". Comparing the first and last few characters will suffice, 46d1 ... 2cab. If yours is different, a resync will be in order as the reorganization functions of the wallet certainly have failed you in 121 days. If your hash is the same, I suspect the above second resolution should fix the issue.

I am sorry you are having an issue and hope this information helps. Again, sorry for the slow response and you feeling the need to scour 250 pages. Of course, this slow of a response is not normal and not the time a community member should expect assistance. Unique circumstances made it so and I will be standing by to offer more assistance if needed.

First two parts were not the issue but 3rd... It gives me 21bcb6b37863e881f1427f7d7bb5868bc4f433088cbc9d8c5647f9a9ae4cc512 as Block hash :O So I need to resync apparently.

Snapshotting would be the fastest way, http://Sterlingcoin.org/SterlingcoinSnapshot796871.zip (~372 MB) Extract and overwrite those contained files into your Sterlingcion data directory ( %appdata%/sterlingcoin/ or ~/.sterlingcoin/ ). Delete the peers.dat file. Start the wallet and allow it to fully sync. This snapshot is 2 months old, but should give you a very healthy head start.

I suspect this might be occurring for people because few coins are being consistently staked on the network. Difficulty drops very low and many wallets submit a block to the network at about the same time. This flood of blocks across the network forces 'islands' to form and be built on faster than consensus agrees across the network. The islands become locked.

We need more coins constantly staked I believe. I am acquiring as many as I can and staking them 24 7.

Please verify your chain against the explorer and stake your Sterlingcoin as often as possible.

EDIT: Linux or Pi users: the above snapshot is of the data files from a machine with DB 6.1. Earlier versions of Berkeley DB will not read it. Windows and mac users: your wallet uses DB 6.1 already. The snapshot will work fine for you.

Thanks for supplying the snapshot, but when I go to "Extract All" I get a message saying that the zip file is empty!

Size of folder = 364,016 KB

Sorry to bother you, but can we possibly try that again, please?  


Sterling Sentinel