ANN Mandatory update FLAP FINAL Miners to share BILLIONS of Coins 10 days !SWAP! - page 42.

n00bminer

member

Activity: 104

Merit: 10

Quote from: hanzou on July 20, 2017, 05:30:38 PM

I think I figured it out. If you run with -mintxfee=0.0001 -minrelaytxfee=0.0001 that makes a 4000 FLAP transaction cost something reasonable like 0.3 FLAP.

Unfortunately everybody's nodes are setting the default fees really high so at first my transactions weren't getting accepted by the network. So then I applied these settings to my node that carried hashpower to pull my low-fee transactions through.

So we could benefit if anyone here running an active node could go ahead and edit flappycoin.conf accordingly.

Code:

mintxfee=0.0001
minrelaytxfee=0.0001

stopped the node and added that to the .conf, trans fees are as above now!

spartagates

member

Activity: 116

Merit: 10

Developer has been a bit quiet of late? An update would be cool

menlatin

sr. member

Activity: 366

Merit: 260

Quote from: crys191971 on July 20, 2017, 05:35:59 PM

They own about 5000000 flappycoins a few years ago. Can I do anything with these coins?

By 'they' do you mean 'I'? If so, you can download the new V5 wallet, sync it with the available bootstrap.dat and then copy your old wallet.dat into the C:\Users\[USER]\AppData\Roaming\FlappyCoin folder and you should have your coins back.

wailord284

newbie

Activity: 52

Merit: 0

Quote

I think I figured it out. If you run with -mintxfee=0.0001 -minrelaytxfee=0.0001 that makes a 4000 FLAP transaction cost something reasonable like 0.3 FLAP.

Unfortunately everybody's nodes are setting the default fees really high so at first my transactions weren't getting accepted by the network. So then I applied these settings to my node that carried hashpower to pull my low-fee transactions through.

So we could benefit if anyone here running an active node could go ahead and edit flappycoin.conf accordingly.

I edited my node to use this now! So far a 25 flap transaction went from a flap fee of 73 to 5.7 so that is significantly better

crys191971

sr. member

Activity: 304

Merit: 250

They own about 5000000 flappycoins a few years ago. Can I do anything with these coins?

hanzou

newbie

Activity: 38

Merit: 0

Thanks uBm! And ugabuga for the PM.

Quote from: n00bminer on July 20, 2017, 01:45:40 PM

Update: node is up and pulling blockchain down. ( 198.98.48.192:11556 )

Nice work getting everything built and running on Linux.

Quote from: uBm on July 19, 2017, 03:53:59 PM

the tx fee isssue

I think I figured it out. If you run with -mintxfee=0.0001 -minrelaytxfee=0.0001 that makes a 4000 FLAP transaction cost something reasonable like 0.3 FLAP.

Unfortunately everybody's nodes are setting the default fees really high so at first my transactions weren't getting accepted by the network. So then I applied these settings to my node that carried hashpower to pull my low-fee transactions through.

So we could benefit if anyone here running an active node could go ahead and edit flappycoin.conf accordingly.

n00bminer

member

Activity: 104

Merit: 10

Update: node is up and pulling blockchain down. ( 198.98.48.192:11556 )

You may want to add to your "How to build a node instructions"

Code:

iptables -A INPUT -p tcp --dport 11556 -j ACCEPT
iptables -A INPUT -p udp --dport 11556 -j ACCEPT

uBm

member

Activity: 88

Merit: 10

@hanzou solomining:
to keep it simple:

Quote

sgminer -k scrypt -o http://ipfromwallet:11555 -u user -p yourpassword
pause

for more information about sgminer type sgminer.exe -h
configure flappycoin.conf in %appdata% >> flappycoin before mining
sample:
daemon=1
server=1
listen=1
rpcuser=user
rpcpassword=yourpassword
rpcallowip=*
rpcport=11555
port=11556
addnode=24.9.245.200
addnode=104.244.216.187:54890
addnode=54.186.211.206:11556
addnode=[2001:464b:10d3::3]:58548
addnode=88.89.11.212:11556
addnode=172.91.203.163:11556

hanzou

newbie

Activity: 38

Merit: 0

Quote from: n00bminer on July 20, 2017, 10:48:30 AM

If we can get a linux binary for the daemon I could add it to one of my node vps

wailord284 and I can help you with that as we both got flappycoin-qt running on Raspbian. Which Linux distro and architecture are you targeting?

Or if you'd like to attempt to build it yourself, for the most part the instructions in doc/build-*.md work. I did this:

Code:

sudo apt-get install build-essential libdb5.3++-dev libminiupnpc-dev qt4-qmake libqt4-dev \
  libbooost-thread-dev libboost-system-dev libboost-filesystem-dev libboost-program-options-dev
git clone https://github.com/Flapmin/Flappy5.git
cd Flappy5/src
make -f makefile.unix # see notes

I left out libssl-dev as others mentioned having trouble with it, and you can see my earlier instructions for building openssl locally and pointing makefile.unix to it. Later when I ran qmake and plain make for the Qt build I didn't bother specifying my own openssl, so it might actually work with libssl-dev on some systems after all.

IIRC if you don't have libdb4.8 you shouldn't attempt to migrate an old wallet.dat, but libdb5 is fine for fresh wallets.

Quote from: ugabuga on July 19, 2017, 03:57:17 PM

Between 150K ~ 500K ... part of the day I need to reduce to be able to work ...

That would suggest you have a GPU or some small ASIC miner. Can you answer my earlier question about how to solo-mine with sgminer?

n00bminer

member

Activity: 104

Merit: 10

If we can get a linux binary for the daemon I could add it to one of my node vps

adsamy

full member

Activity: 200

Merit: 100

There are many old coins going back to the bull market this year, and I hope you can make meaningful progress

hanzou

newbie

Activity: 38

Merit: 0

Ok I got the OS X build working on Sierra and can now set a breakpoint in main.cpp.

However, I just sent 10000 FLAP and this time the transaction fee was only 3.406, so I'm left without a pathological case to inspect. Is anyone else still seeing the egregiously high tx fees?

One theory I have is that because the fee is based on the size of the transaction, it could be explained because yesterday I was attempting to send from the particular wallet that had dominated mining for a day. 4000 / 25 FLAP block reward = 160 input txIDs, which might explain why it could appear like a "large" transaction in terms of bytes. I'll have to check when I get access to that GeForce box again.

Even if that discrepancy can be explained, we still should fix this if there's no need to run with such high tx fees.

ugabuga

sr. member

Activity: 316

Merit: 250

Quote from: hanzou on July 19, 2017, 03:04:07 PM

Quote from: ugabuga on July 19, 2017, 12:42:46 PM

I'm just bursting money into electricity with the pc day and night pulling ...

Considering our low total network hashrate, you may be the one who has kept the coin alive. What sort of hash rate are you running at?

Between 150K ~ 500K ... part of the day I need to reduce to be able to work ...

uBm

member

Activity: 88

Merit: 10

cool to see people still supporting this topic/coin, i hope the developer can do anything abut the tx fee isssue, also the coin itself needs update, codebase seem a bit dusty to me compared to doge btc etc ... including version number

edit : Flapmin [Last Active: July 01, 2017, 11:30:34 PM]

hanzou

newbie

Activity: 38

Merit: 0

Quote from: ugabuga on July 19, 2017, 12:42:46 PM

I'm just bursting money into electricity with the pc day and night pulling ...

Considering our low total network hashrate, you may be the one who has kept the coin alive. What sort of hash rate are you running at?

Quote from: wailord284 on July 19, 2017, 01:56:42 PM

Hi, do you have experience with making one for Arch Linux? I am unable to downgrade my OpenSSL too far because it causes system instability. Do you know how I could compile it from source and then point the flappycoin source to look for that compiled Openssl? Thanks for you're help.

It would take a bit of time to get an Arch docker container so I'll put that off until later, but here's how I build openssl 1.0.1 on Ubuntu:

Code:

$ curl -O https://ftp.openssl.org/source/old/1.0.1/openssl-1.0.1u.tar.gz
$ tar xfz openssl-1.0.1u.tar.gz
$ cd openssl-1.0.1u
$ ./Configure -fPIC --prefix=$HOME/myopenssl linux-generic32 no-asm enable-static-engine
$ make && make install

Then when you build flappycoind, add args as follows:

Code:

make OPENSSL_INCLUDE_PATH=$HOME/myopenssl/include OPENSSL_LIB_PATH=$HOME/myopenssl/lib -f makefile.unix

Quote

Figured I'd also mention I'm able to compile the qt and daemon on my raspberryPi running raspbian which has allowed me to run a node 24/7 but, due to its ARM architecture transferring the compiled binary doesn't work. I also tried to make a p2pool for flappycoin but am getting an error so if you have experience with that maybe we could work together or something.

A bit confused. You tried transferring the build from one Raspberry Pi to another? That should be fine unless one is ARMv7 (Pi 2 and beyond) and the other ARMv6 (Raspberry Pi 1, B+, or Zero).

I don't have my Raspberry Pi on hand at the moment. For the p2pool building problem, how about you private-message me with the log and I'll take a look at the log tonight. I'm totally cool if you end up collecting the aforementioned bounty!

wailord284

newbie

Activity: 52

Merit: 0

Quote

I may be able to help as I have a bit of experience building openssl from source and can do it in any Docker container to match your system, then send you either compiled binaries or my build script. What Linux distro / libc version are you targeting? Assuming v1.0.1l will do.

Hi, do you have experience with making one for Arch Linux? I am unable to downgrade my OpenSSL too far because it causes system instability. Do you know how I could compile it from source and then point the flappycoin source to look for that compiled Openssl? Thanks for you're help.

Figured I'd also mention I'm able to compile the qt and daemon on my raspberryPi running raspbian which has allowed me to run a node 24/7 but, due to its ARM architecture transferring the compiled binary doesn't work. I also tried to make a p2pool for flappycoin but am getting an error so if you have experience with that maybe we could work together or something.

ugabuga

sr. member

Activity: 316

Merit: 250

WOW !!!!!

More than 72 billion Huh

I'm weeks to mine half a million because I thought there would be "few" flap, after all, I'm just bursting money into electricity with the pc day and night pulling ...

Sad... very sad... Angry

hanzou

newbie

Activity: 38

Merit: 0

Yeah that makes sense. Thanks Sravas!

Quote from: ugabuga on July 18, 2017, 07:41:33 PM

Out of curiosity, does anyone know what is the total of valid, outstanding Flap?

It's been a while since I've played with this interface, but I found this command:

Code:

gettxoutsetinfo
{
"height" : 770300,
"bestblock" : "a6a9fc86471046194e13984f79e26857aa363e229ae5e8e5af7e45120cfd7478",
"transactions" : 387128,
"txouts" : 458774,
"bytes_serialized" : 26298262,
"hash_serialized" : "e41dddbccadc84c8b510344219b15eb60d2ded8ab660c74d673919aeba11bd7a",
"total_amount" : 72429393501.99800110
}

which would indicate about 72.4 billion FLAP, somewhat higher than the original 70 billion target.

Quote from: flappycoinrevive on July 12, 2017, 11:05:05 PM

our only mining pool has been shutdown. Can anyone startup another one. Reward offering.

I may be interested in attempting this. How much is the reward offering?

That's not my main motivation, but it would be nice to avoid any surprise if I happen to get stuck debugging some challenging issues in an unfamiliar setup.

Quote from: uBm on July 16, 2017, 04:51:13 AM

Also the tx fee issue has to be sorted out, that is bugged. No matter what i set as minimum, it takes sometimes 50 % of the transaction as plus for tx fee.

I saw https://github.com/Flapmin/Flappy5/issues/1 and confirmed the same problem with a screenshot. I think it wouldn't be hard to set a breakpoint in the applicable TxFee source lines and step through to see where it blows up. However, using a debugger would first require building from source. Are any of you guys doing that already and have some tips?

Quote from: uBm on July 16, 2017, 04:51:13 AM

if i would be able to compile the linux version - that would help, but it seems it is not possible neither on my vserver nor on a local virtual machine, seems to be open ssl related. ( 1.1 vs 1.01).

I may be able to help as I have a bit of experience building openssl from source and can do it in any Docker container to match your system, then send you either compiled binaries or my build script. What Linux distro / libc version are you targeting? Assuming v1.0.1u will do.

wailord284

newbie

Activity: 52

Merit: 0

Quote from: Sravas on July 19, 2017, 04:20:04 AM

Quote from: hanzou on July 18, 2017, 11:18:12 PM

...

I went through this procedure and can confirm it successfully transferred my 2014 balances and I was able to mine more coins on top of that as we sit here at block 769528. I did not need to install the old client, run importprivkey or any of the additional steps in Sravas's description.

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).

Ok thanks for the clarification. I got myself confused. Glad to see that this is working!

Sravas

newbie

Activity: 44

Merit: 0

Quote from: hanzou on July 18, 2017, 11:18:12 PM

...

I went through this procedure and can confirm it successfully transferred my 2014 balances and I was able to mine more coins on top of that as we sit here at block 769528. I did not need to install the old client, run importprivkey or any of the additional steps in Sravas's description.

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).

Topic: ANN Mandatory update FLAP FINAL Miners to share BILLIONS of Coins 10 days !SWAP! - page 42. (Read 40440 times)