I personally feel this thread can be closed. My reasons…
The version in question is 0.8.7.3 - Windows, 64BIT. That version is no longer the production version and no longer works with 0.9.6.
0.9.6 Windows binaries and setup files have been uploaded to the official Feathercoin GitHub page.
https://github.com/FeatherCoin/Feathercoin/releases and are confirmed as working and virus free
@wrapper said in ORPHAN BLOCK 751 Blockchain Sync Stuck.:
@lizhi
Re: Testing 0.9.3.2 - Full Re-synchronisation :
Whilst I haven’t had to restart like @Aciddude, the debug.log has now hit 2.6GB with the messages.
Do a ‘cat >> debug.log’ followed by a ‘ctrl-c’
This will empty the logfile, even while the client is running
@lizhi said in FTC 0.9.3.2 Synchronisation problems:
Fix it , I can sync blockchains.
https://github.com/FeatherCoin/Feathercoin/commit/a6e3064572195451ead14e0320f5546734163ad6
I’ve merged this into my fork and I’m testing as well. Thanks!
@Wellenreiter
I was able to figure that out. I was fortunate enough to have an extra laptop that I could do a fresh install of 16.04. I was able to compile the wallet with no problems.
@ghostlander said:
It’s possible technically to downgrade a Berkeley DB to an older format using their command line tools. I build wallets with v5.3.28 currently. v6 is the AGPL v3 which might cause legal issues with the BSD/MIT software.
Thanks for the update.
With the recent work completing builds testing, thanks to @Aciddude and @Wellenreiter,
All versions of Feathercoin up to 0.9.3.1 have a full set of P.P.A.s available for most Linux distributions software centres.
How to install Feathercoin PPA / binaries…
http://forum.feathercoin.com/topic/8327/guide-how-to-install-feathercoin-wallet-binaries-on-ubuntu-and-debian-linux-ppa
@Radent said:
@wrapper :
my PC with windows 7. wallet qt was sync. my new wallet does not balance, but in my paper wallet have any coins.
If that is the case, simply delete the directory %appdata%/feathercoin, start the wallet again and wait for it to sync.
Your problem should be solved then.
The feathercoin block explorer doesn’t find the trnsaction id:
http://explorer2.feathercoin.com/tx/41ad34bb7f6128d98f132297a9fa011448d81a3d89e8432ee210c5852b1473d2
returns
'transaction not found’
So the transaction didn’t make it to the block chain.
Hi - Jake did you find an answer to your query in the end?
Note : Re : Forum Notifications.
Email notifications may need to be configured for NodeBB or and email pluging added
[nodebb-plugin-pushbullet] Push Notifications for NodeBB | NodeBB
Good to hear, that your problem is solved.
I’ve market the thread as ‘solved’. If you don’t agree, you can flat is as unsolved with the topic tools located at the first post
Hi @jvds,
first of all welcome to the forum.
There is no feature to block any connection in the wallet code.
The problem is to get one initial connection to the feathercoin network, so the addresses of the active nodes can be learned.
If all build in mechanisms to get this first connection established fail, you can manually add a node to get the synchronization started.
For feathercoind:
start feathercoind
then issue the command `feathercoind addnode 46.4.0.101 add’
For feathercoin-qt:
start the gui
from the main window select ‘help’ ->‘Debug Window’ -> ‘console’
enter ‘feathercoind addnode 46.4.0.101 add’ in the input field at the bottom of the window
This should open a connection to the node 46.4.0.101 which is a p2pool node where a feathercoind is running all time. After some time additional nodes will be learned and the synchronization will start.
Please be aware, that each node has a maximum number of parallel connections and when this is reached, no additional connections will be accepted. Therefore it may take some time to get the initial connection.
If this doesn’t help, please provide the wallet version and OS you are using and if possible the content of the file debug.log which is located in the feathercoin data directory
I will move this thread to the support forum so other developer will find it more easily. You are able to post to that category, too after your initial post in the new member area.
Thanks for the update.
The question remains, what caused the problem with the 0.9.5 wallet.
Did you send coins to a stealth address?
Can you provide the first digit of the receiving address?
