Feathercoin 0.8.5 Client

wrapper

ACK, will get back on more tests.

Wellenreiter

[quote name=“Bushstar” post=“40992” timestamp=“1386402498”]
[quote author=Wellenreiter link=topic=4885.msg40679#msg40679 date=1386359283]
For the release, we can link the package depot to the main page, as you suggested before.

Just give me a heads up, so I can pull the last revision about a day before the release message get’s out and start the packaging process
[/quote]

Can you please go ahead and pull the latest version?

We should release this as Wrapper suggests as RC1.
[/quote]

Done.

It shows as version 0.8.5.0_rc1 on [url=http://software.opensuse.org/package/feathercoin]http://software.opensuse.org/package/feathercoin[/url]

By the way, the new splash screen looks great :)

wrapper

Sanity check, Beta3

Compiled Linux 13.10,
tested translations,
general test + adjust settings.
Press all buttons.
Mouse over descriptions.
Debug log, getpeerinfo, no errors noted.
sync with network

>>>>>>>>>>

New splash screen is Mint. Looks great.

I’ll do 13.04 32 bit compile as well next, just in case.

Bushstar

[quote name=“iawgoM” post=“41538” timestamp=“1386493709”]
[quote author=wrapper0feather link=topic=4885.msg41291#msg41291 date=1386444813]
New splash screen is Mint. Looks great.
[/quote]

Well, thank you ::)
[/quote]

Kudos to iawgoM, thanks for the new splash screen :)

Bushstar

I have now linked in all RC1 releases into the first post of this thread. I’m thinking that these should be linked into the front page as the main downloads with links to the old build below. Do this sound sane?

ftcMagic

I’ve built it on my Archlinux box from GIT and have been using it constantly as my main wallet. It receives just fine from the pool I use, it sends just fine to BTC-e. All buttons work; I’ve encountered no crashes. I haven’t used the RCP console, and I haven’t tried solo mining with it. Other than that, what needs to be checked before release?

wrapper

I have a Blockchain database update issue, possibly due to Qt5 compile.

Will take a few hours to recompile and test import wallet to Virtual box wallet.

Fields are aligned to wrong fields in Recieve database. After update 0.6.4.4 to 0.8.5 RC1

Tried -reindex and -rescan (no change).

Still advise caution updating to new 0.8.5. client, unless in clean test environment. Always back up wallet anyway.

Wellenreiter

I’m using qt4 and haven’t noticed any problem.
How does the problem show up?

keep me updated.

Bushstar

Wrapper, have you been able to recreate the blockchain DB corruption?

What kind of error message did you get on launch? This may be a well documented quirk :)

Wellenreiter, I have seen your fix for Debian on GitHub and will give it a spin tomorrow.

Wellenreiter

simply added a close button to the qrcode window. beneficial for all versions I think ;)

wrapper

[quote name=“Bushstar” post=“43526” timestamp=“1386873903”]
Wrapper, have you been able to recreate the blockchain DB corruption?

What kind of error message did you get on launch? This may be a well documented quirk :)
[/quote]

Still got 0.8.5 upgrade / restore back up -receive fields description mismatch.

I’ve reproduced some upgraded wallets and also cut down Debug.log file for the upgrade period.

I’ve checked but not seen any similar fault, too busy could be wrong. Let me know if Maintenance Task identified…

Is it because mining had no Address label? so the all addresse field content dropped down one? In my case address Bit-messa**** being first in the index. Which is why it is the new mining label?

I’ll look at data structures and get back.

wrapper

I can’t find why my receive address got mismatched after update, yet. We need a workaround whatever. May be a coincidence but got this in Debug.log.

AddToWallet 261d5a88ba8a9b56c3b85fae9c42f2301c942e4c649117df414fe234b63984c2
AddToWallet 390a6f0d0abd8cba8218af790047833576a23363ae1bc6c11856970f7ac8834a
ERROR: bool CBlock::ReadFromDisk(const CDiskBlockPos&)() : deserialize or I/O error
ERROR: bool CBlock::ReadFromDisk(const CDiskBlockPos&)() : deserialize or I/O error
ERROR: bool CBlock::ReadFromDisk(const CDiskBlockPos&)() : deserialize or I/O error
-rescan

See below my mining has a “bit-message label”. the 6i1BPX is my mining receive.

Field description mismatch. I only just updated my real system, so that should be clean of tests.

This is the line in main.cpp that adds the receive address to the wallet on a rescan.

>>>>>
// make sure all wallets know about the given transaction, in the given block
void SyncWithWallets(const uint256 &hash, const CTransaction& tx, const CBlock* pblock, bool fUpdate)
{
BOOST_FOREACH(CWallet* pwallet, setpwalletRegistered)
pwallet->AddToWalletIfInvolvingMe(hash, tx, pblock, fUpdate);

[attachment deleted by admin]

Nexistenz

With the change up to 0.8.5 is there a possibility for distributing a block chain bootstrap? The one thing I kept hearing from folks that I’ve turned on to feathercoin is that it takes so long for the initial sync. From my view it only makes sense to streamline the process given the client upgrade from 0.6.x to 0.8.x means bootstrap.dat support is built in.

As it stands now I’ve started handing out thumb drives which contain the installer, a batch file, and my relatively up-to-date block chain with index, blk0001.dat and blkindex.dat, as a zip file. The user runs the batch file and if the block chain isn’t found in the users data directory, it’s extracted from the zip file, and finally the installer is run. While this works fine it is somewhat archaic in nature. Given the updated client supports bootstrapping is there a plan to release an official bootstrap so I can simply say download this and this and enjoy?

wrapper

The easiest way I’ve found to update someone’s blockchain over the local LAN.

To do that go to help debug, then use addnode onetry to add another PC with wallet that is on the network, the wallet sync then happens automatically.

You can check you got the link, getpeerinfo to display the connected peers.

Also, the initial sync problem you describe is not unique to Feathercoin, it effects all flavours of p2peer coins.

Kevlar

[quote name=“Nexistenz” post=“43869” timestamp=“1386958039”]
With the change up to 0.8.5 is there a possibility for distributing a block chain bootstrap? The one thing I kept hearing from folks that I’ve turned on to feathercoin is that it takes so long for the initial sync. From my view it only makes sense to streamline the process given the client upgrade from 0.6.x to 0.8.x means bootstrap.dat support is built in.

As it stands now I’ve started handing out thumb drives which contain the installer, a batch file, and my relatively up-to-date block chain with index, blk0001.dat and blkindex.dat, as a zip file. The user runs the batch file and if the block chain isn’t found in the users data directory, it’s extracted from the zip file, and finally the installer is run. While this works fine it is somewhat archaic in nature. Given the updated client supports bootstrapping is there a plan to release an official bootstrap so I can simply say download this and this and enjoy?
[/quote]

I’m so glad you’re asking, since we need someone to volunteer for this.

Please, take that zip, add a nice README.txt explaining what it is, add it to uTorrent, seed it, and post the magnet link here. You’ll be doing everyone a great service.

wrapper

I agree with kevlar …

Going off topic on my 0.8.5 Upgrade database bug tho’ Any thoughts 3 back…

Nexistenz

[quote name=“Kevlar” post=“43883” timestamp=“1386960685”]
I’m so glad you’re asking, since we need someone to volunteer for this.

Please, take that zip, add a nice README.txt explaining what it is, add it to uTorrent, seed it, and post the magnet link here. You’ll be doing everyone a great service.
[/quote]
I’d be more than willing to, but with the crap internet I’ve got,1Mb/254Kb service, there’s no way I could seed it properly. I wouldn’t be adverse to throwing it up somewhere if someone else would like to seed it though, but since it’s literally two files zipped, not the block chain serialized, pretty much anyone could do it. As it stands I just [url=http://hastebin.com/weyidilumo.dos]threw up[/url] the script that’s included on the thumb drive with instructions on how to use it yourself when making thumb drives to give out.

wrapper

I’ve found a bug in upgrading some clients. I haven’t found the cause.

It happens on Kubuntu 13.10 with a standard [guide] Virtualbox Linux compile and my PC, upgrade 0.6.4.4 or import a 0.6.4.4. backup.

My Wallet receive address and database field labels got mismatched after upgrade. 6i1B~ is my mining address and the label was blank before the upgrade, now say Bit-message the wrong label (See image 2.)

This is how it used to look - Mining n/a
(see image 3.)

I couldn’t easily find a .DAT file generic viewer to see why there might be a field match…

When testing previous Beta versions of 0.8.5 I got the field mismatch but mined coins showed up, ok.

Notes
I didn’t compile it as Qt5 (see image 1)

Both databases were Berkelay5.1

[attachment deleted by admin]

Bushstar

Wrapper, is that 64bit or 32bit Kubuntu?

So you get the same problem if you create a new 0.6.4.4 wallet to import?

I’m wondering if you get the same problem if you create a new wallet, import your private keys and then import that to 0.8.5. Perhaps your .dat file is unhappy.

I will setup a VM and try to recreate the problem, let me know if it is 32 or 64 bit.

wrapper

[quote name=“Bushstar” post=“44175” timestamp=“1387011581”]
Wrapper, is that 64bit or 32bit Kubuntu?
So you get the same problem if you create a new 0.6.4.4 wallet to import?
I’m wondering if you get the same problem if you create a new wallet, import your private keys and then import that to 0.8.5. Perhaps your .dat file is unhappy.
I will setup a VM and try to recreate the problem, let me know if it is 32 or 64 bit.
[/quote]

It is 64bit. I don’t have my 0.6.4.4 wallet as I thought my backups were the same and just upgraded it. I was doing a Virtualbox compile first, which was slow, so I just went ahead. Then the same happened in the VirtualBox test .

Previously, I think I was testing new installs not upgrades, done a lot, exact detail hazy.

I can reproduce small databases from my initial FTC wallet backup then send that to you, should make mode of failure obvious?. +Test Upgrade works on very old wallet backups?

Sorry for delay, just found “notify me of relpies” in “Attachments and other options”