Topic: [ANN] FlappyCoin - PoS Released - 6/29 - Need Counterparty Fork - 4btc - page 3. (Read 41356 times)
November 19, 2015, 04:35:11 AM
Do any of you know of a good way to release coins that seemed to be stuck trying to stake a block that wasn't accepted by the network? I tried -rescan and that didn't work, at the moment I'm in the processes of re-downloading the blockchain.
November 18, 2015, 12:23:33 PM
Cryptsy has been notified of the new wallet update.
hold off on that until i do the one with the fixing minting and the negative stake fix (should be tonight)
November 18, 2015, 11:10:11 AM
Cryptsy has been notified of the new wallet update.
November 18, 2015, 03:25:23 AM
Can anybody post any new "addnode=" for flappycoin.conf ?
I have only 2 active connections for last three days since I've started my wallet again
I have only 2 active connections for last three days since I've started my wallet again
see here:
https://chainz.cryptoid.info/flap/#!network
-> node list
Code:
addnode=104.131.68.98
addnode=118.96.212.98
addnode=129.21.141.135
addnode=129.21.141.193
addnode=129.21.141.94
addnode=173.81.241.136
addnode=176.36.244.198
addnode=178.112.233.159
addnode=192.99.91.78
addnode=194.135.92.14
addnode=46.105.129.29
addnode=62.202.41.207
addnode=71.41.188.110
addnode=77.116.27.251
addnode=81.36.60.164
addnode=81.44.138.234
addnode=84.161.237.60
addnode=94.61.193.156
addnode=118.96.212.98
addnode=129.21.141.135
addnode=129.21.141.193
addnode=129.21.141.94
addnode=173.81.241.136
addnode=176.36.244.198
addnode=178.112.233.159
addnode=192.99.91.78
addnode=194.135.92.14
addnode=46.105.129.29
addnode=62.202.41.207
addnode=71.41.188.110
addnode=77.116.27.251
addnode=81.36.60.164
addnode=81.44.138.234
addnode=84.161.237.60
addnode=94.61.193.156
this is mine on a fast network:
Code:
addnode=46.105.129.29
November 18, 2015, 02:12:38 AM
Can anybody post any new "addnode=" for flappycoin.conf ?
I have only 2 active connections for last three days since I've started my wallet again
I have only 2 active connections for last three days since I've started my wallet again
November 17, 2015, 06:21:24 PM
-the fact that mining is set to false by default
please also check this (from my previous post):
when gen=1 is set, it does not stake. getgenerate tells true, but i have to write setgenerate true again in the debug console.
then it immediatly stake, when there are enough connections.
maybe the problem is when it starts - there are no connections and it doesnt try it again!
a simple delay of 1 minute would solve this or even better an automatic retry (check connections every x minutes).
no. thats not how getarg works.
its because the -command that would be fed in if you were to run it from command line are not overridden by .conf file settings. so the default -gen=0 via command line is not overridden by the config gen=1
bitcoin.cpp line 120 is a comment on this
if that is not clear also util.cpp line 1116 which is inside the ReadConfigFile function. im kinda sad i knew this without looking anything else up besides the line number....
November 17, 2015, 05:16:23 PM
-the fact that mining is set to false by default
please also check this (from my previous post):
when gen=1 is set, it does not stake. getgenerate tells true, but i have to write setgenerate true again in the debug console.
then it immediatly stake, when there are enough connections.
maybe the problem is when it starts - there are no connections and it doesnt try it again!
a simple delay of 1 minute would solve this or even better an automatic retry (check connections every x minutes).
November 17, 2015, 03:36:51 PM
found slight error on FLAP wallet. not a scary huge update but the next update will fix:
-the fact that mining is set to false by default
-block mining spacing that makes it impossible to mine a block more often than every 30 seconds
-a fix that makes it impossible to stake a negative amount after block 710,000 because right now if you stake less than 0.02 FLAP in a block you get a negative amount that is between -0.001 and -0.000001 FLAP. (so negligible losses) but it still shouldnt happen.
-the fact that mining is set to false by default
-block mining spacing that makes it impossible to mine a block more often than every 30 seconds
-a fix that makes it impossible to stake a negative amount after block 710,000 because right now if you stake less than 0.02 FLAP in a block you get a negative amount that is between -0.001 and -0.000001 FLAP. (so negligible losses) but it still shouldnt happen.
November 17, 2015, 08:55:57 AM
I would like to claim the CounterParty Bounty!
What I need
- A VPS with a cool domain (flapcounter.io or something)
What I need
- A VPS with a cool domain (flapcounter.io or something)
November 17, 2015, 08:49:12 AM
EDIT: does not work, forget it...
when gen=1 is set, it does not stake. getgenerate tells true, but i have to write setgenerate true again in the debug console.
then it immediatly stake, when there are enough connections.
maybe the problem is when it starts - there are no connections and it doesnt try it again a bit later!
so a simple delay of 1 minute would solve this or even better an automatic retry.
warning/info:
i restartet the wallet several times, and forgot to enable staking "setgenerate true", because the default is false.
To fix this, create or edit the file "flappycoin.conf" where the wallet.dat resides and put
Now it automatically start staking (proof with "getgenerate" in the console)
when gen=1 is set, it does not stake. getgenerate tells true, but i have to write setgenerate true again in the debug console.
then it immediatly stake, when there are enough connections.
maybe the problem is when it starts - there are no connections and it doesnt try it again a bit later!
so a simple delay of 1 minute would solve this or even better an automatic retry.
warning/info:
i restartet the wallet several times, and forgot to enable staking "setgenerate true", because the default is false.
To fix this, create or edit the file "flappycoin.conf" where the wallet.dat resides and put
Code:
gen=1
in it.Now it automatically start staking (proof with "getgenerate" in the console)
November 16, 2015, 06:09:36 PM
My wallet won't sync. Is the problem solved or not?
I'm guessing your question is related to one I had a few pages back.
So, according to this (https://chainz.cryptoid.info/flap/#) at the time of posting we're at block 700442 and that is supported by my peer connections. My wallet says that it is on block 700442, yet still thinks it is 13 hours behind? How do we counter the slow network when there may be long periods of time when no blocks were created (which I'm assuming causes the wallets to think they are behind?)?
no, its not because they think they are behind. the code of a wallet doesnt actually care about the last block time. the gui just shows the behind message if the last block was over 2 hours ago for the user to see the chain has stopped. people need to just turn on staking in their wallets and the chain moves. no one has staking on, then the chain wont move.
So, if there has been a two hour delay since the last block was process, you'll probably get that message. Good news is, the network is smoothing out so that these delays should disappear.
November 16, 2015, 06:02:22 PM
Opened the Flap wallet and it shows as synced now on block 702500.
thats the block all 4 of the wallets i am running are on
Sounds like that is the main chain then? I'm on 702518, which is about right with the time that has passed... How many people are having client issues (and do we know why the block explorer is behind?)?
November 16, 2015, 05:28:41 PM
Opened the Flap wallet and it shows as synced now on block 702500.
thats the block all 4 of the wallets i am running are on
November 16, 2015, 05:01:29 PM
Opened the Flap wallet and it shows as synced now on block 702500.
November 16, 2015, 04:53:20 PM
My wallet won't sync. Is the problem solved or not?
what block r u on?
November 16, 2015, 04:20:17 PM
My wallet won't sync. Is the problem solved or not?
November 16, 2015, 04:03:32 PM
Ok.
For now, i will put in a new wallet with commands "dumpprivkey" and "importprivkey"
thanks
For now, i will put in a new wallet with commands "dumpprivkey" and "importprivkey"
thanks
November 16, 2015, 03:47:18 PM
a question: POS works even when the wallet is encrypted ??
you have to unlock it before it can stakehow unlock???
If you have a password set you can go to the Help menu button and open the Debug Console.
Once it is opened type the following command into the bar and set the time limit you want it to stay open.
walletpassphrase yourpassword timetostayopen
It will look something like this,
walletpassphrase thisismypass 6000
This will keep your wallet unlocked for 100 minutes.
if im not mistaken if you dont enter a time or enter 0 then it will stay unlocked until you lock it or restart the wallet
With previous experience it has to be a set time limit. I don't know for sure with FlappyCoin as the settings could be different but with the other PoS coins I use it functions this way.
If you skip the time it will throw an error as it needs all 3 parameters to work. I'm not sure about 0 but I would take a gander that it wouldn't unlock it.
November 16, 2015, 03:44:44 PM
a question: POS works even when the wallet is encrypted ??
you have to unlock it before it can stakehow unlock???
If you have a password set you can go to the Help menu button and open the Debug Console.
Once it is opened type the following command into the bar and set the time limit you want it to stay open.
walletpassphrase yourpassword timetostayopen
It will look something like this,
walletpassphrase thisismypass 6000
This will keep your wallet unlocked for 100 minutes.
if im not mistaken if you dont enter a time or enter 0 then it will stay unlocked until you lock it or restart the wallet
November 16, 2015, 03:41:08 PM
a question: POS works even when the wallet is encrypted ??
you have to unlock it before it can stakehow unlock???
If you have a password set you can go to the Help menu button and open the Debug Console.
Once it is opened type the following command into the bar and set the time limit you want it to stay open.
walletpassphrase yourpassword timetostayopen
It will look something like this,
walletpassphrase thisismypass 6000
This will keep your wallet unlocked for 100 minutes.
Jump to: