Topic: [ANN] FlappyCoin - PoS Released - 6/29 - Need Counterparty Fork - 4btc - page 21. (Read 41385 times)
June 13, 2015, 10:58:10 PM
It stopped syncing all together? What blk files did it create?
June 13, 2015, 09:40:43 PM
I just sent some with v4.0 wallet and they went through. You might have to resync your wallet to get those funds to show up again and then try sending them again.
Is there a bootstrap for 4.0 available?
http://www.goflap.io/download/bootstrap.dat
I think the bootstrap is a tad off, it went to block 700 something and then marked itself as old and stopped.
June 13, 2015, 09:12:32 PM
I just sent some with v4.0 wallet and they went through. You might have to resync your wallet to get those funds to show up again and then try sending them again.
Is there a bootstrap for 4.0 available?
http://www.goflap.io/download/bootstrap.dat
June 13, 2015, 08:49:28 PM
the pool i am running on 129.21.141.135:3032
(connect instructions above)
is processing the 4.0 transactions. we do need a little bit more hash over there.
if your tx is stuck try a resync. that might help. it was never a code problem. just a problem that 3.2 cant send 4.0 tx. we probably should have had the mining pools update first. now i know that for the future.
(connect instructions above)
is processing the 4.0 transactions. we do need a little bit more hash over there.
if your tx is stuck try a resync. that might help. it was never a code problem. just a problem that 3.2 cant send 4.0 tx. we probably should have had the mining pools update first. now i know that for the future.
June 13, 2015, 08:37:22 PM
I just sent some with v4.0 wallet and they went through. You might have to resync your wallet to get those funds to show up again and then try sending them again.
Is there a bootstrap for 4.0 available?
June 13, 2015, 07:22:51 PM
Should I tweet this info?
Please mine FLAP on temp pool before POS starts.
129.21.141.135:3032
Username = your payment address
PW = can be anything
Please mine FLAP on temp pool before POS starts.
129.21.141.135:3032
Username = your payment address
PW = can be anything
You can if you want, but it looks like we may have it covered. New transactions are being processed between v4.0 wallets now. Any stuck transactions will need to resync blockchains.
June 13, 2015, 07:15:56 PM
I just sent some with v4.0 wallet and they went through. You might have to resync your wallet to get those funds to show up again and then try sending them again.
I think we're good to go now that Chasing Coin is on v4.0 and our temp pool is v4.0.
Re-commence wallet upgrades!!
I think we're good to go now that Chasing Coin is on v4.0 and our temp pool is v4.0.
Re-commence wallet upgrades!!
June 13, 2015, 07:01:39 PM
can anyone confirm that a transaction they sent with a 4.0 wallet has gone through. the 4.0 pool has solved a block and i know my 4.0 transaction that was stuck has been sent. has anyone elses gone through now?
My transactions haven't gone through yet, no.
For some reason the 1.8M transaction to a player of DK went through the day I sent it which was sent 1 minute after the other one and the other transaction didn't.
Currently 75,250.02 FLAP floating around somewhere out there.
June 13, 2015, 06:41:33 PM
can anyone confirm that a transaction they sent with a 4.0 wallet has gone through. the 4.0 pool has solved a block and i know my 4.0 transaction that was stuck has been sent. has anyone elses gone through now?
June 13, 2015, 03:51:05 PM
Chasing Coin is on the new wallet, but hasn't solved any blocks yet....
June 13, 2015, 02:13:22 PM
Should I tweet this info?
Please mine FLAP on temp pool before POS starts.
129.21.141.135:3032
Username = your payment address
PW = can be anything
Please mine FLAP on temp pool before POS starts.
129.21.141.135:3032
Username = your payment address
PW = can be anything
June 13, 2015, 01:16:28 PM
See that guys? We need all miners on the new temporary pool!
June 12, 2015, 04:29:20 PM
for those of you a bit concerned with the unconfirmed transactions for 4.0 wallets, we are going to start a temporary 4.0 pool (temporary because flappy stops mining in 25k blocks anyway) and will post address and information in this thread within 6 hours, this is just to get those transactions confirmed so you dont have to wait until PoS starts
edit: pool is 129.21.141.135:3032
you username should be the address you want to receive your payments
your password can be anything
edit: pool is 129.21.141.135:3032
you username should be the address you want to receive your payments
your password can be anything
June 12, 2015, 02:05:12 PM
Are there any plans to get the coin run on Cryptsy again? I still have some Flappy coins there. Would be nice to withdraw them when the new wallet works.
Its been on Cryptsy Ltc market for a year now. https://www.cryptsy.com/markets/view/FLAP_LTC
June 12, 2015, 01:10:53 PM
Are there any plans to get the coin run on Cryptsy again? I still have some Flappy coins there. Would be nice to withdraw them when the new wallet works.
June 12, 2015, 01:10:34 PM
PLEASE HALT ALL TRANSACTIONS UNTIL FURTHER NOTICE.
We think there is an issue with mining pools not being on the updated wallet, and not packing transactions from the new wallet. Please contact, tweet, msg all known mining pools to get them to update. If this doesn't solve the problem, we may be looking at something bigger.
We think there is an issue with mining pools not being on the updated wallet, and not packing transactions from the new wallet. Please contact, tweet, msg all known mining pools to get them to update. If this doesn't solve the problem, we may be looking at something bigger.
Will the unconfirmed transactions confirm with a fix? For instance, I have 20+ payments sent that are still unconfirmed from yesterday.
if the payments were sent with a 4.0 wallet, and assuming that is actually a field recognition error that is occurring (which is what i am lead to believe it is as this time) then yes. those transactions that are unconfirmed should confirm
June 12, 2015, 01:03:38 PM
PLEASE HALT ALL TRANSACTIONS UNTIL FURTHER NOTICE.
We think there is an issue with mining pools not being on the updated wallet, and not packing transactions from the new wallet. Please contact, tweet, msg all known mining pools to get them to update. If this doesn't solve the problem, we may be looking at something bigger.
We think there is an issue with mining pools not being on the updated wallet, and not packing transactions from the new wallet. Please contact, tweet, msg all known mining pools to get them to update. If this doesn't solve the problem, we may be looking at something bigger.
Will the unconfirmed transactions confirm with a fix? For instance, I have 20+ payments sent that are still unconfirmed from yesterday.
June 12, 2015, 12:27:03 PM
PLEASE HALT ALL TRANSACTIONS UNTIL FURTHER NOTICE.
We think there is an issue with mining pools not being on the updated wallet, and not packing transactions from the new wallet. Please contact, tweet, msg all known mining pools to get them to update. If this doesn't solve the problem, we may be looking at something bigger.
We think there is an issue with mining pools not being on the updated wallet, and not packing transactions from the new wallet. Please contact, tweet, msg all known mining pools to get them to update. If this doesn't solve the problem, we may be looking at something bigger.
June 12, 2015, 11:21:34 AM
Whoopsie daisy! We found a sending problem with the new wallet Sit tight while we fix it!
June 12, 2015, 09:40:13 AM
With new wallet UPnP port mapping is unavailable, that is not good. It means guaranteed issues with conectivity (unable to accept incoming connections). Number of reachable nodes is already low and without UPnP enabled it will surely go down.
http://i.imgur.com/aElqmiV.jpg
http://i.imgur.com/aElqmiV.jpg
that is incorrect, UPNP mapping is on, i compiled the wallets with upnp mapping enabled
Are you suggesting that I faked that screenshot?
No, absolutly not. What he means is that he enabled the upnp mapping when he compiled the wallets. So all the wallets have upnp enabled for better connectivity.
What you image shows is that we can't disable UPnP mapping
Jump to: