any news about frozen coinexchange.io wallet?

I made withdrawal from Poloniex  2017-08-24 05:51:04
Bought 2 years before: 2016-04-02

Simply make standard withdrawal and create ticket thereafter, if it would not processed automatically.
I have send 1.01 PIGGY for test.
The rest of coins after support have pushed their wallet up (after confirmed arrival of testing 1.00 PIGGY to my desktop wallet).

with coming +18 Billion supply do you seriously believe that somebody will spend (invest  ) 10 K USD (1.8 BTC) simply to hold market on current state?

the price will definitely sink down

simply make 12500 to 1 swap instead of 10000 to 1 by artifical inflation :-)

IMHO the swap is not needed at all
DOGE has 111 Billion, BCN 184 Billion supply and x2000 higher price without any swap :-)

80 Billion for past 4 years
and +18 Billion for next 3 months??

we'll have 1-2 litoshi price too long...

shit

Tradesatoshi has processed withdrawal of tons of FLAPs to my wallet few hours ago

would they come back to account if they are on "wrong" chain?

Hi guys,

Why the chain has stopped?

I also confirm that old v3.2.0 wallet.dat can be recovered just by file replacement without privatekey importing.

However I'm nor sure if every version of old wallet.dat will be recognized by V5 without problems.
For example, V4 wallet.dat (year 2015 POS etc.) synchronyzed years ago after  block 699 999 may not work(if you have delete v3.2.0 wallet.dat and are keeping v4 only).

Privatekey dumping - importing is universal procedure and must work ever (for coin amounts confirmed before block 700 000).

if repairwallet command / blockchain rescanning doesn't work - try privatekey dump/import
your funds are stored primary in blockchain, not in the wallet.dat file 

use Blockexplorer for detailed imformation about every transaction status

It seems to be situation described above:
1 FLAP balance PC #2
OLD BALANCE minus 1 FLAP (sent) minus 37 FLAP (comission) PC #1
OLD BALANCE PC #3

PC #1 and PC #3 wallets must be identical as recovered from the same old wallet with the same address.

BUT current amounts are "different" because PC #3 don't see your last transaction.

Unfortunately I have not FLAP QT on hand right now and can't check - please try RPC commands in debug window on PC #3:

repairwallet
or
rescan

(you can type help before that and check if command is allowed in current QT version)

You must have identical transactions and coin amounts on both PC #1 and #3 thereafter.

QT ver.3.2.0 is not working with current blockchain.
It's not possible move coins between old wallets.
But possible to recover old wallet/wallets on new blockchain in QT ver.5
If you have several old wallets with different addresses, you must recover every of them apart.

If you have only one old wallet and want to move coins to other PC:

Use 3.2.0 only for privatekey dumping on first PC (debug command in console).
Save this privkey.

Go to second PC.
Check whether directory ..AppData/Roaming/Flappycoin exist.
If YES, rename entire folder to other name, for example /FlappycoinOLD
Better way is to make archive copy of this old folder somewhere in secure place away from ..AppData/Roaming.
May be this folder contain another old wallet and you want to recover this one too.

Download new QT ver. 5 from Github, save proper .conf file and .lib

Start QT ver. 5 application. Wait for full synchronization.
You will have 0 (ZERO) balance at this point. It's normal.
QT ver. 5 will create new clear wallet on "clear" PC (old Flappycoin folder is renamed to FlappycoinOLD or moved to archive copy (not removed forever !!!) and not seen by application).
So this ZERO in not your balance yet.
Go to debug window.
Type importprivkey yoursavedprivatekey
Press Enter and wait some minutes for full blockchain scan.
Your old wallet with all previous information (old address, coin amount, thansaction data) will be recovered.
Wait for full synchronization.
Exit application.
Save arhive of entire new ..AppData/Roaming/Flappycoin folder in secure place.
Save archive of your new wallet.dat file from ..AppData/Roaming/Flappycoin in secure place.

NEVER LEAVE YOR WALLET.DAT FILE NOR PRIVATEKEY STRING ELSEWHERE IN PUBLIC ACCESSIBLE PLACES !

If you have "several" old wallets with the same address but different coin amount (actually the same wallet from different PC), you will have the last coin amount recorded in blockchain (according to last confirmed transaction for this address).

If you have more than one old wallet, save them all in secure place before any manipulation.
Rename every wallet.dat file to different name (for example, wallet-YEAR-MONTH-DAY.dat) to prevent overwrite.
Make privatekey for every old one
(copy back to old ..AppData/Roaming/Flappycoin folder on first PC
rename wallet-YEAR-MONTH-DAY.dat to standard wallet.dat
start ver.3.2.0 application
dump privatekey and save)

Import every privatekey in QT ver. 5 on second PC and save every new recovered wallet under unique name.

please DO NOTHING with your coins in previous wallets before official announce from thread starter

all coins confirmed in blockchain before block 700000 are spendable

they can be "imported" in current QT ver. 5 by dumpprivkey - importprivkey procedure after [current] QT synchronisation

so, there are active:

[2001:464b:10d3::3]:58548
54.186.211.206:11556
88.89.11.212:11556

here is my flappycoin.conf
synchronized
3 active connections righ now


flappycoin-5 windows qt.exe from there https://github.com/Flapmin/Windows-Wallet-

my QT shows 2 active connections righ now
synchronised
.conf as before

and how about REDDcoin, NETcoin etc.?
it seems to be enough stable POS for past years

! backup your current wallet.dat elsewhere in secure place before manipulations !

save QT in new empty folder with libwinpthread-1.dll and check if /Roaming/Flappycoin is also empty at start besides .conf file

don't use your real wallet.dat at the first start
allow program to create it (dummy with 0 balance)

if no nodes are seen after start - try to add them manually in console by typing every string and press Enter after each:

addnode 96.52.216.191:11556 add
addnode 88.89.11.212:11556 add
addnode 24.9.245.200:11556 add
addnode 54.186.211.206:11556 add
addnode 104.244.216.187:54890 add

of course magically not
but getting the chain moving is principal
previous POS attempts were killed not by POS itself
IMHO by every few hours crashing chain 

have you no worries about possible intellectual property / trademark use violation?

for example on Github

my be contributor is nearly to QT update, therefore current wallet was deleted from Dropbox?