[Dev] Feathercoin 0.9.6.2 * Maintenance fix, build & upgrade issues notes.

wrapper

@Wellenreiter said in [Dev] Feathercoin 0.9.6.2 * Maintenance fix & Issues notes for 0.11.2:

@AcidD we should create and use a feathercoinunits.cpp/.h and use that instead

I agree and this is the same thing we need to look at for other changes during the review whilst moving to head.
The main reason is to make future merges less problematic.

AcidD

Can someone fork Bitcoin into the Feathercoin Github ?

@Wrapper you made a fair point a while back somewhere…if we properly fork from Bitcoin head and then do our commits we can easily pull in their fixes as well ?

wrapper

@AcidD Yes, thats the job I call “Going to Head” !

wrapper

Getting this message opening the debug.log in 0.11.2

The file /home/tony/.feathercoin/debug.log was opened with UTF-8 encoding but contained invalid characters.
It is set to read-only mode, as saving might destroy its content.
Either reopen the file with the correct encoding chosen or enable the read-write mode again in the tools menu to be able to edit it.

AcidD

@wrapper said in [Dev] Feathercoin 0.9.6.2 * Maintenance fix & Issues notes for 0.11.2:

Getting this message opening the debug.log in 0.11.2

The file /home/tony/.feathercoin/debug.log was opened with UTF-8 encoding but contained invalid characters.
It is set to read-only mode, as saving might destroy its content.
Either reopen the file with the correct encoding chosen or enable the read-write mode again in the tools menu to be able to edit it.

When writing to the Debug log, does 0.11.2 leave comments that are written by @lizhi and therefore uses a different character encoding?

wrapper

https://bter.com/trade/ftc_btc

Is running Feathercoin 0.9.3.2

wrapper

@AcidD said in [Dev] Feathercoin 0.9.6.2 * Maintenance fix & Issues notes for 0.11.2:

When writing to the Debug log, does 0.11.2 leave comments that are written by @lizhi and therefore uses a different character encoding?

Server Hosted in Luxemberg + FTC = BTER

wrapper

Issue Notes :

Whilst syncing a (fresh blockchain database/wallet) Feathercoin 0.11.2-dev , mouse over the exclamation mark next to Balances . says Bitcoin

QRCodes did not work - need review after merge complete

Check : Transaction fee set to 0.00001 FTC/kB

Sign message - tool tip on Advanced menu option - Verify message sign message tab says bitcoin

Verify message - tool tip on Advanced menu option - Verify message - Verify message tab says bitcoin

Advanced / Options / Wallet : Check default coin control settings are correct

There are quite a few changes made to the wallet structure, the standard bitcoin connection animation looks Ok. opennames is missing.

@AFB helped to do some fiddling to bring in all the improvements we did into 0.11.2 , possibly make a couple more icons / update some bad new forms.

There is another test (that would help us move to head) - Fork Bitcoin, checkout 0.11 last version - merge ftc 0.11.2

Update autoconfig.sh to test for zxing Directory e.g. :
if [ ! -d “$DIRECTORY” ]; then
# Control will enter here if $DIRECTORY doesn’t exist.
fi

Update Re-Indexing message to be more friendly / informative? (when you upgrade)

Why do we have uFTC and mFTC surely DecaFTC is more logical?? (needs review)

Test and document Smart contracts.

Smart contracts is just a form, review and remove, smart contract form.

SX search for stealth coins not included.

find not utf-8 characters grep -axv ‘.*’ main.cpp

propose launch option shrink debug file :

Add -shrinkdebuglog to the options you use to start feathercoin, or add shrinkdebuglog=1 to your feathercoin.conf. Every startup, if the log is larger than 1MB, it will shrink it to 200KB.

wallet.cpp change control :
// TODO: fix handling of ‘change’ outputs. The assumption is that any
// payment to a script that is ours, but is not in the address book
// is change. That assumption is likely to break when we implement multisignature
// wallets that return change back into a multi-signature-protected address;
// a better way of identifying which outputs are ‘the send’ and which are
// ‘the change’ will need to be implemented (maybe extend CWalletTx to remember
// which output, if any, was change).

Fri, 12 September 2014 16:29:30 -0400 build date incorrect, debug information @wellenreiter

Add these dependencies to FTC unix build docs :
libevent-2.0-5 libevent-dev libevent-extra-2.0-5 libevent-openssl-2.0-5 libevent-pthreads-2.0-5

LogPrintf(" (no) space error(s)

Enter multisync, new address, press ok with no address. – Incorrect error message.
The entered address “” is not a valid Bitcoin address.

Multisig page, - verify message button - not connected to anything …

Update the openSSL version used / review : OpenSSL 1.0.2g 1 Mar 2016

Re-Integrate updated Documents from 0.9.6.2

Review MAN pages - copied in from 0.9.6.1 because 0.11.2 MANs were deleted. need review against Bitcoin 0.11.1

src/qt/forms/debugdialog.ui - Reused form SX form and menu options need reapplying.

feathercoin.qrc has not been implemented in 0.11 - being worked on as part of merge

Icons are missing, test icons - being tested / brought in as part of merge

https://github.com/litecoin-project/litecoin/pull/362 SSE2 Litecoin enhancement.
https://uk.mathworks.com/matlabcentral/answers/93455-what-is-the-sse2-instruction-set-how-can-i-check-to-see-if-my-processor-supports-it?requestedDomain=www.mathworks.com

ACP is not working in 0.11

openssl version and future use review :
https://github.com/peercoin/peercoin/commit/3320650372750068dff45193603d17998a975117

Wellenreiter

@wrapper we should group these notes and create issues directly on github.
Otherwise it is duplicated work

wrapper

I agree, I’ll move them to issues, these are notes while I investigate.

I’ve also created a pull list on Github so we can discuse which and how we pull the missing commits from 0.9.6.2 and, opennames. We can use the experience to to pull in further changes from head.

https://github.com/FeatherCoin/Feathercoin/pull/201

The pull can be used to identify which don’t need or need more icons etc as we agreed, the project will be used to document pulling them in.

https://github.com/FeatherCoin/Feathercoin/projects/1

wrapper

Need to use cherry pick and meld.

~~Try git imerge a try: that will apply your commits one by one, giving you the chance to do a rebase incrementally (meaning you can start a rebase, interrupt it, resume it later!).~~

You can see here a comparison between Incremental merge vs. direct merge vs. rebase :

http://softwareswirl.blogspot.co.uk/2013/05/incremental-merge-vs-direct-merge-vs.html

https://stackoverflow.com/questions/18162930/how-can-i-find-out-which-git-commits-cause-conflicts

wrapper

Testing 0.11.2 re-indexing database after it was viewed by 0.9.6.1

Crashed twice with : /feathercoin-qt Segmentation fault

seems to have carried on after restart. tbc

Wellenreiter

@wrapper check the build-aux/m4/ax_boost-base for the version.
it is 1.58 in bitcoin code, 1.54 should be ok, too, but I’ve set it to >1.20 to support older OS. We may have to increase that back to >= 1.54

wrapper

I’m setting up a test environment. I’ll repeat the test (viewing 0.11 database with 0.9.6.2) after I’ve resynced and, this time, saved uncorrupted / synced 0.11.2 database

wrapper

Merging commits from 0.9.6.2 to 0.11.2 procedure

Install a mergetool. On Linux, meld:

sudo apt-get install meld

Configure your mergetool:

git config --global merge.tool meld

Then, iterate in the following way:

git cherry-pick ....
git mergetool
git cherry-pick --continue

wrapper

First 0.9.6.2 mergeTest cherry pick commit :

https://github.com/FeatherCoin/Feathercoin/pull/201/commits/0ba808af8a10c8231490088932baa2d6ae0c7106
Added man pages for feathercoin, modified icons

commit 0ba808af8a10c8231490088932baa2d6ae0c7106 @wellenreiter01

wellenreiter01 committed on 1 Nov 2015

git cherry-pick 0ba808af8a10c8231490088932baa2d6ae0c7106

  error: cherry-pick is not possible because you have unmerged files.
  hint: Fix them up in the work tree, and then use 'git add/rm <file>'
  hint: as appropriate to mark resolution and make a commit.
  fatal: cherry-pick failed    


git mergetool
Merging:
contrib/debian/manpages/feathercoin.conf.5
contrib/debian/manpages/feathercoind.1
contrib/debian/manpages/feathercoin-qt.1

Deleted merge conflict for 'contrib/debian/manpages/feathercoin.conf.5':
  {local}: deleted
  {remote}: created file
Use (c)reated or (d)eleted file, or (a)bort?

Note
Test - Create © all new MAN files. were MAN pages moved in from Bitcoin 0.11? and then FTCed? should still work.
Are there any other references / links to the original MAN names?

wrapper

2. 0.9.6.2 mergeTest cherry pick commit :

changed paperwallet template and copyright strings

commit 07525719698e379f2c721e8e6ffdc6a08468c843 @wellenreiter01

wellenreiter01 committed on 9 Nov 2015

Contains a number of copyright changes - not need. @Wellenreiter needs to check, wither rest are still needed. The paper wallet image may be, and was added in test.

src/m4/bitcoin_find_bdb48.m4 ---- updated for test
src/m4/bitcoin_find_bdb51.m4 ---- updated for test

wrapper

Sync issue 0.9.6.1 - Resync 1 year - Blockchain and update wallet.

Note : worked with fresh wallet

2017-07-21 08:20:48 ProcessBlock: Preliminary checks
2017-07-21 08:20:48 ERROR: matches claimed amount, CheckProofOfWork() : hash doesn’t match nBits
2017-07-21 08:20:48 AcceptBlockHeader,nHeight=1580548
2017-07-21 08:20:48 GetNextWorkRequired pindexLast block Height=1580547,nBits=474666155
2017-07-21 08:20:48 GetNextWorkRequired the next block Height=1580548
2017-07-21 08:20:48 GetNextWorkRequired fork
2017-07-21 08:20:48 Difficulty rules regular blocks
2017-07-21 08:20:48 GetNextWorkRequired(), nActualTimespan = 5 before bounds
2017-07-21 08:20:48 RETARGET: nActualTimespanShort = 106, nActualTimespanMedium = 67, nActualTimespanLong = 64, nActualTimeSpanAvg = 79, nActualTimespan (damped) = 64
2017-07-21 08:20:48 RETARGET: nActualTimespan = 64 after bounds
2017-07-21 08:20:48 RETARGET: nTargetTimespan = 60, nTargetTimespan/nActualTimespan = 0.9375
2017-07-21 08:20:48 GetNextWorkRequired RETARGET
2017-07-21 08:20:48 nTargetTimespan = 60 nActualTimespan = 64
2017-07-21 08:20:48 Before: 1c4ad4ab 000000004ad4ab00000000000000000000000000000000000000000000000000
2017-07-21 08:20:48 After: 1c4fd1c7 000000004fd1c777777777777777777777777777777777777777777777777777
2017-07-21 08:20:48 ConnectBlock hashPrevBlock=df3735d388ede485e3255d1f389aa651d37bcce1bc04a4408e2bdbdb8239a46f
2017-07-21 08:20:48 ConnectBlock view.GetBestBlock()=df3735d388ede485e3255d1f389aa651d37bcce1bc04a4408e2bdbdb8239a46f
2017-07-21 08:20:48 AddToWalletIfInvolvingMe,hash=1411a9f462d6b47459f7e8abaa402db9bdd6246f3622dedc1717848f27661b10 .
2017-07-21 08:20:48 FindStealthTransactions() tx:1411a9f462d6b47459f7e8abaa402db9bdd6246f3622dedc1717848f27661b10,BOOST_FOREACH nOutputIdOuter=0 ,find txout…
2017-07-21 08:20:48 txout scriptPubKey= OP_DUP OP_HASH160 ba513ceff6297945cbb4c5746f184356adcc2d9b OP_EQUALVERIFY OP_CHECKSIG
2017-07-21 08:20:48 txout hash = 8cb243d8b996f59f7d0c9e0a106cdc7cc6cf88e47b621ed2df00da26697a34dc
2017-07-21 08:20:48 AddToWalletIfInvolvingMe,hash=06ad4778cb2eb3ac4016003fab4c4b58c6de576fa7edd80a619907435f64e8ba .
2017-07-21 08:20:48 FindStealthTransactions() tx:06ad4778cb2eb3ac4016003fab4c4b58c6de576fa7edd80a619907435f64e8ba,BOOST_FOREACH nOutputIdOuter=0 ,find txout…
2017-07-21 08:20:48 txout scriptPubKey= OP_DUP OP_HASH160 123762cccc17098a5b0868eb44557ab50d0a55a6 OP_EQUALVERIFY OP_CHECKSIG
2017-07-21 08:20:48 txout hash = 3c42a83e3ee1f65595ebe93efef179fad9b2e7ab59a1a25cca39da63cd5d6512
2017-07-21 08:20:48 BOOST_FOREACH nOutputIdOuter=1 ,find txout…

Appears to be a similar fault in Litecoin recognizing the Genesis Block …

https://bitcointalk.org/index.php?topic=555733.0

wrapper

Sync 0.9.6.2 - Blank with updated peers.dat error message example …

2017-07-21 08:38:51 receive version message: /Feathercoin:0.9.6/: version 70003, blocks=1808179, us=88.105.71.156:37890, them=104.236.34.9:9336, peer=104.236.34.9:9336
2017-07-21 08:39:24 receive version message: /Feathercoin:0.9.6.1/: version 70005, blocks=1808179, us=88.105.71.156:47522, them=178.238.236.130:9336, peer=178.238.236.130:9336
2017-07-21 08:39:24 Added time data, samples 14, offset +0 (+0 minutes)
2017-07-21 08:42:01 ProcessBlock: Preliminary checks
2017-07-21 08:42:01 ERROR: matches claimed amount, CheckProofOfWork() : hash doesn’t match nBits
2017-07-21 08:42:01 ProcessBlock() ProcessBlock: ORPHAN BLOCK 4, prev=75fa1d017fcaf1463912686b3cb090301c672edbf97cecb67faac9d15223d328
2017-07-21 08:42:02 ProcessBlock: Preliminary checks
2017-07-21 08:42:02 ProcessBlock() ProcessBlock: ORPHAN BLOCK 5, prev=169c84a4bf1c6b36371315aa5ddb2cc95c2ae5d8fff460ea38fa3cbb2715530e

Wellenreiter

@wrapper

I have seen that several times dunig my tests with 0.9.6.* . The ORPHAN BLOCK COUNTER going up to
ProcessBlock() ProcessBlock: ORPHAN BLOCK 751.

It seems there was a number of forks happening, which where resolved later. I can’t remember the block height where it happened, so I can’t tell, that is is the same block where the messages started to show up