Fimkrypto forum

English discussion => General FIMK Discussion => Topic started by: warmach on July 18, 2015, 09:09:06 PM

Title: Warmach's Forging Pool
Post by: warmach on July 18, 2015, 09:09:06 PM
This pool is completely automated and there is no minimum balance or lease length requirements.  My goal is to create a laid back, easy going group of FIMKers. 

Pool website has about a 1-5 minute delay behind blockchain.  It may take 1-5 minutes before transactions on blockchain show up on website.

Pool Website:

http://fim.warmach.info/pool

Pool Account:

FIM-JS7L-HU5X-XUTT-2GGQH
https://www.mofowallet.com/launch.html#/accounts/FIM-JS7L-HU5X-XUTT-2GGQH/activity/latest (https://www.mofowallet.com/launch.html#/accounts/FIM-JS7L-HU5X-XUTT-2GGQH/activity/latest)

Pool Fee:

1% FIM at withdrawal

Payouts:

Payouts are initiated by the lessor with a blockchain message sent to the Pool account.  Message can contain anything except items in pool settings section.  The message only indicates a withdrawal request of confirmed balance minus 0.1 FIM network fee and pool fee.  Payout occurs when message reaches 1440 confirmations.

Depending on popularity of pool, I may enforce a maximum balance and automatically send a payout.  I don't not wish to be a bank and hold large sums of money.

Pool Logic:

When you lease your balance to the pool, the balance is used for forging blocks by the pool.  If the pool forges a block, the block rewards are given to the pool.  Once the block is confirmed, the block rewards are then divided up to those lessors proportionately who had active leases at the time the block was forged.  The divided rewards are then recorded in the database while the actual funds stay in the pool's account.  Once a request is made to withdraw the funds, the database calculates the total confirmed rewards available to the account and the payment is made to the lessor.

While the funds are being held by the pools account, they are used to increase the total forging power of the pool.  This increases the likelihood of another block being forged which will then be divided up by the lessors.  The pool account balance is not used when determining the ratio of the payouts.  In this way, lessors continue to benefit from increased forging power.  In addition, all fees paid remain in the pool account so as to again increase total forging power for the benefit of the lessors.  The only time the pool receives any FIM is from the 1% fee.  Forging payouts only go towards lessors.

If your funds remain in the pool after your lease has expired, any new block rewards received after your lease expiration will not be distributed to the expired lease account.  Your funds will be used to increase forging power for pool and its active lessors.  While you may not benefit, your fellow lessors do. 

Pool Settings
The pool software can accept messages sent via the FIMK network and will adjust the pool settings accordingly.

To adjust the settings, send a message on the FIMK network to the pool address above and include one of the following settings below. All messages sent to pool will send a response message indicating your message was received and processed.

SETTINGS
Pool will respond with message listing the pool settings for you account

AUTO PAY ON
Turn on lease end payouts. The new setting will take effect the next time you lease your balance to the pool.

AUTO PAY OFF
Turn off lease end payouts. The new setting will take effect the next time you lease your balance to the pool.

EMAIL yourEmail@email.com
Set an email address associated with your account.

REMINDER ON
Turn on lease end reminder emails. This feature requires an email to be linked to your account. The new setting will take effect the next time you lease your balance to the pool.

REMINDER OFF
Turn off lease end payouts. This feature requires an email to be linked to your account. The new setting will take effect the next time you lease your balance to the pool.
Title: Re: Warmach's Forging Pool
Post by: warmach on July 24, 2015, 01:59:05 AM
I sent a message of thanks the beta testers via blockchain.  Thanks again for helping out!
Title: Re: Warmach's Forging Pool
Post by: warmach on July 24, 2015, 03:18:49 AM
What features would you find useful or fun in a forging pool?  Once we are out of beta, I would like to continue to add features.

How about automatic asset investment with your pool earnings?

Lottery blocks where participants put in 50 FIM and then winner take all?
Title: Re: Warmach's Forging Pool
Post by: dance on July 24, 2015, 11:28:29 AM
What features would you find useful or fun in a forging pool?  Once we are out of beta, I would like to continue to add features.

How about automatic asset investment with your pool earnings?

Lottery blocks where participants put in 50 FIM and then winner take all?
Automatic withdrawal on leasing expiration or/and notification message?
Compound interest?
Title: Re: Warmach's Forging Pool
Post by: warmach on July 24, 2015, 01:48:38 PM
Automatic withdrawal on leasing expiration or/and notification message?
Compound interest?

Automatic withdrawal...simple but a great idea!

Compound interest...  The pool itself does kind of have compound interest.  Any forged blocks that are older than 1440 are used for a forging balance until the funds are withdrawn. 

Thanks for the ideas!
Title: Re: Warmach's Forging Pool
Post by: Mapa on July 24, 2015, 02:55:02 PM
Automatic withdrawal...simple but a great idea!

Compound interest...  The pool itself does kind of have compound interest.  Any forged blocks that are older than 1440 are used for a forging balance until the funds are withdrawn. 

Thanks for the ideas!
Time-based withdrawal process with fixed fee does cause som problems (atleast for small capitol leasers). Lets make a small example and set the expiration for 10'000 blocks (~3.5 days).

Jimmie with 100 FIM and Jack with 100k FIM leases their capitals at same point. With current 1% block forging rate, the pool would be forging 100 blocks on this period of time equaling 20'000 FIM. Jimmie's stake before the fees would be approx. 1 ‰ (20 FIM) and Jack's would be 99.99% (19'980 FIM). With fixed fee on leasing Jimmie would pay 25% vs. Jack paying less than 1‰.

Usually pools use fixed-% fee instead, which doesn't lead to this case.
Title: Re: Warmach's Forging Pool
Post by: warmach on July 24, 2015, 03:38:26 PM
Time-based withdrawal process with fixed fee does cause som problems (atleast for small capitol leasers). Lets make a small example and set the expiration for 10'000 blocks (~3.5 days).

Jimmie with 100 FIM and Jack with 100k FIM leases their capitals at same point. With current 1% block forging rate, the pool would be forging 100 blocks on this period of time equaling 20'000 FIM. Jimmie's stake before the fees would be approx. 1 ‰ (20 FIM) and Jack's would be 99.99% (19'980 FIM). With fixed fee on leasing Jimmie would pay 25% vs. Jack paying less than 1‰.

Usually pools use fixed-% fee instead, which doesn't lead to this case.

You are right, but automatic withdrawal would be voluntary. 

I had not considered % based fees but you make a good point about taking a higher percentage of the little guy with flat fee.  I may have to change the fee...
Title: Re: Warmach's Forging Pool
Post by: warmach on July 24, 2015, 11:58:23 PM
I had not considered % based fees but you make a good point about taking a higher percentage of the little guy with flat fee.  I may have to change the fee...

As I think about this more, this makes more sense.  I want everyone to be able to participate regardless of FIM balance.  After all, my FIM balance doesn't have that many zeros... :)

The pool will be changing the pool fee from 5 FIM per withdrawal to 1% FIM fee taken at withdrawal. 

Beta testers may PM or blockchain message me requesting the 5 FIM withdrawal fee.  I hate to make a change like this after people have already leased their balance.

Any new leases starting.....NOW...Will use the 1% fee.

Thanks Mapa for clearly explaining the impact of my previous pool fee. 
Title: Re: Warmach's Forging Pool
Post by: warmach on August 02, 2015, 01:09:38 AM
I've migrated the pool server to a server in a Tier 1 data center.  Previously, the pool site and FIM server were hosted on a Raspberry Pi and was subject to power and internet outages.  While we only had 2 hours of total down time since starting, I felt that moving to a more reliable server location was important. 

As a result, I now have two Raspberry Pi machines freed up and I can now run a full server backup, in case there is a problem at the data center, as well as having a test server for development. 

With the new release today, I will be running the 0.5 FIM server on my test Pi and seeing how that runs. 

I also will be looking more into the transient messaging.  It seems ideal for making withdrawal requests as it is unnecessary for a withdrawal request AM to stay on the blockchain forever.  Until then, please use the existing AM method for withdrawal requests.
Title: Re: Warmach's Forging Pool
Post by: dance on September 01, 2015, 04:50:59 PM
Pool logic isn't absolutely clear to me. Regarding the FIMKs which were forged using my leased balance. Are they added to my "FIM Contribution" during forging? Do they forge in my favor when lease period is expired (if there was no withdrawal)? Or they are working for the pool owner?
Title: Re: Warmach's Forging Pool
Post by: warmach on September 01, 2015, 06:56:12 PM
Pool logic isn't absolutely clear to me. Regarding the FIMKs which were forged using my leased balance. Are they added to my "FIM Contribution" during forging? Do they forge in my favor when lease period is expired (if there was no withdrawal)? Or they are working for the pool owner?

Good questions!

When you lease your balance to the pool, the balance is used for forging blocks by the pool.  If the pool forges a block, the block rewards are given to the pool.  Once the block is confirmed, the block rewards are then divided up to those lessors proportionately who had active leases at the time the block was forged.  The divided rewards are then recorded in the database while the actual funds stay in the pool's account.  Once a request is made to withdraw the funds, the database calculates the total confirmed rewards available to the account and the payment is made to the lessor.

While the funds are being held by the pools account, they are used to increase the total forging power of the pool.  This increases the likelihood of another block being forged which will then be divided up by the lessors.  The pool account balance is not used when determining the ratio of the payouts.  In this way, lessors continue to benefit from increased forging power.  In addition, all fees paid remain in the pool account so as to again increase total forging power for the benefit of the lessors.  The only time the pool/pool owner receives any FIM is from the 1% fee.  Forging payouts only go towards lessors, which I am also a pool lessor for my personal balance.

If your funds remain in the pool after your lease has expired, any new block rewards received after your lease expiration will not be distributed to the expired lease account.  Your funds will be used to increase forging power for pool and its active lessors.  While you may not benefit, your fellow lessors do.  This scenario likely played out during your active lease as well giving you the benefit of forging using another lessors confirmed balance.  Keeping track of rewards for expired leases would be complicated and more likely prone to error. 

I do plan on adding an auto payout feature on lease expiration once we are out of beta.  Hopefully we can be out of beta in another month. 

I hope this helps!
Title: Re: Warmach's Forging Pool
Post by: dance on September 01, 2015, 07:53:25 PM
That explains more.
So, the balance of FIM-JS7L-HU5X-XUTT-2GGQH - is actually the sum of non-taken-yet withdrawals, or it contains your own FIMKs too?
Title: Re: Warmach's Forging Pool
Post by: warmach on September 01, 2015, 07:58:17 PM
That explains more.
So, the balance of FIM-JS7L-HU5X-XUTT-2GGQH - is actually the sum of non-taken-yet withdrawals, or it contains your own FIMKs too?

FIM-JS7L-HU5X-XUTT-2GGQH contains the not-taken-yet withdrawals and the pool funds.  The pool funds come from the 1% fee assessed  at withdrawal.  My personal funds are held in a different account that is leased to the pool.  I follow the same steps to withdraw my personal earnings as every lessor. 

Title: Re: Warmach's Forging Pool
Post by: dance on September 01, 2015, 08:30:43 PM
FIM-JS7L-HU5X-XUTT-2GGQH contains the not-taken-yet withdrawals and the pool funds.  The pool funds come from the 1% fee assessed  at withdrawal.  My personal funds are held in a different account that is leased to the pool.  I follow the same steps to withdraw my personal earnings as every lessor.
So your fees are working in favor of pool lessors.
Thanks for answers.
It would be good to have in FIM/NXT some kind of `lease-prolongation` transaction and not to wait 1440 blocks between leasings...
Title: Re: Warmach's Forging Pool
Post by: warmach on September 01, 2015, 08:39:00 PM
So your fees are working in favor of pool lessors.
Thanks for answers.

No problem.

It would be good to have in FIM/NXT some kind of `lease-prolongation` transaction and not to wait 1440 blocks between leasings...

I've tested the lease stuff a bit and found that you can send a new lease transaction 1439 blocks before your lease expires.  This means that your balance will only be idle for a few blocks between leases. 

I wrote a perl script that checks how long is left on a lease and then send the new lease transaction.  It requires a full running FIMK node and a machine for the script to run on.  http://forum.fimk.fi/index.php?topic=616.0    I'd be willing to host the script for people, but it the transaction requires your secret password and I don't want to be responsible for security someone's secret password.
Title: Re: Warmach's Forging Pool
Post by: kani on September 01, 2015, 09:01:26 PM
I've tested the lease stuff a bit and found that you can send a new lease transaction 1439 blocks before your lease expires.  This means that your balance will only be idle for a few blocks between leases. 

It gets better than that!

You can have one pending lease issued at any time during an active lease.  The pending lease will take effect as soon as the active lease has expired (assuming it has had 1440 blocks to mature).  Once the pending lease becomes the active lease, a new pending lease can be submitted.
Title: Re: Warmach's Forging Pool
Post by: warmach on September 01, 2015, 09:04:13 PM
It gets better than that!

You can have one pending lease issued at any time during an active lease.  The pending lease will take effect as soon as the active lease has expired (assuming it has had 1440 blocks to mature).  Once the pending lease becomes the active lease, a new pending lease can be submitted.

Sweet!  I tried during an active lease but kept getting an error.  I assumed it was due to being over 1440 blocks.  I will have to revisit this...

Did you do add a pending lease via API call or using the Lompsa client?
Title: Re: Warmach's Forging Pool
Post by: kani on September 01, 2015, 09:12:27 PM
Did you do add a pending lease via API call or using the Lompsa client?

I just send a new lease transaction using the Lompsa client.  API call would probably work, too.

As far as I know, there is no good way to actually view pending leases in the client.
Title: Re: Warmach's Forging Pool
Post by: kani on September 01, 2015, 09:52:33 PM
Let me illustrate:

1: Submit the first lease and wait 1440 blocks.
2: Once lease is active, submit a new one which becomes pending (do with at least 1440 block left in active to avoid any inactive balance)
   -- note: if a new lease is issued before the pending becomes active, the pending is overwritten with the new.
3: When the active lease expires, the pending becomes the new active.
4: Repeat from 2.
Title: Re: Warmach's Forging Pool
Post by: dance on September 01, 2015, 11:48:28 PM
1: Submit the first lease and wait 1440 blocks.
2: Once lease is active, submit a new one which becomes pending (do with at least 1440 block left in active to avoid any inactive balance)
Yep, that will work for now.
Title: Re: Warmach's Forging Pool
Post by: warmach on September 02, 2015, 12:31:35 AM

As far as I know, there is no good way to actually view pending leases in the client.

I used the client with no problem.  Thanks for the tip! 

I didn't see either a way to see pending leases.  On the other hand, my pool scripts queries the API.  The API just added the new lease length onto the existing lease.  So, now my account is leased to the pool for 41287 blocks.  Looks like API returns total lease(s) length.  I wonder how it would be different if I set a pending lease to lease to a another account....  Hmm... 
Title: Re: Warmach's Forging Pool
Post by: farcurlew on September 09, 2015, 04:13:12 AM
Thanks for setting this up. Until the latest releases I had no trouble forging. Now it is a different story.
Your pool simplified things for me.
Title: Re: Warmach's Forging Pool
Post by: warmach on September 09, 2015, 02:15:47 PM
Thanks for setting this up. Until the latest releases I had no trouble forging. Now it is a different story.
Your pool simplified things for me.

I am happy I could help.  This makes it worth the effort!
Title: Re: Warmach's Forging Pool
Post by: warmach on September 26, 2015, 08:19:57 PM
I have removed the "BETA" tag from the pool.  We've been running several months without any software issues. 

Now that the basic functionality of the pool is in place, I'd like to do some more development on it to add features.  I plan to work on an auto-payout on lease end first.  Please feel free to chime in with other features you may like to see included.
Title: Re: Warmach's Forging Pool
Post by: dance on January 01, 2016, 10:34:57 AM
Pool is not working?
Title: Re: Warmach's Forging Pool
Post by: warmach on January 01, 2016, 02:42:44 PM
Pool is not working?

The live server can be picky.  For some reason, that I have not yet figured out, the FIM process dies.  Because of this, I have a backup server running that continues to forge even though the main server process stopped.  I have restarted it and the server will need to catch up on blocks forged and then issue payout requests.  I am sorry about this.  I am trying to figure out what the best solution is going forward. 

I am sorry I missed this.  My wedding anniversary and new year distracted me from keeping an eye on it.
Title: Re: Warmach's Forging Pool
Post by: warmach on January 01, 2016, 03:43:56 PM
Happy New Year!

Thanks for all those forging with my pool.  At our height we had 9 lessors, including myself.  I look forward to what this coming year has in store. 

I wanted to give you a few updates on the pool. 

1.  The live server seems to have an issue that kills the FIM process at random.  It could be 12 hours or 12 days before it happens again.  This makes it hard to troubleshoot.  Rest assured that forging never stops.  I have two backup FIM clients running that forge for the pool.  The backup clients only forge and do not process payouts.  I am considering scrapping the live server and moving to my more reliable backup servers.

2.  I had been starting development of new features but realized that the current Perl scripts were very limited in what they could handle.  I have decided to re-code the pool software to use Python.  This will make future development easier and quicker.  I am currently in the process of re-coding and testing.

I will post as I have more info to pass along. 

Title: Re: Warmach's Forging Pool
Post by: Dirk Diggler on January 01, 2016, 03:55:37 PM
Perhaps you could try running FIMK from an upstart script and have it auto-restart on shutdown.
Then from a post-start stanza http://upstart.ubuntu.com/cookbook/#post-start run a script or single command line command to start forging.

There is a working example here https://github.com/fimkrypto/fimk_chef_repo/blob/master/cookbooks/fimk/templates/default/fimk.conf.erb.
Thats a part of our chef deployment setup.
Title: Re: Warmach's Forging Pool
Post by: dance on January 01, 2016, 05:48:01 PM
Happy New Year!

Thanks for all those forging with my pool.  At our height we had 9 lessors, including myself.  I look forward to what this coming year has in store. 

I wanted to give you a few updates on the pool. 

1.  The live server seems to have an issue that kills the FIM process at random.  It could be 12 hours or 12 days before it happens again.  This makes it hard to troubleshoot.  Rest assured that forging never stops.  I have two backup FIM clients running that forge for the pool.  The backup clients only forge and do not process payouts.  I am considering scrapping the live server and moving to my more reliable backup servers.

2.  I had been starting development of new features but realized that the current Perl scripts were very limited in what they could handle.  I have decided to re-code the pool software to use Python.  This will make future development easier and quicker.  I am currently in the process of re-coding and testing.

I will post as I have more info to pass along.
ok, happy New Year too!
Title: Re: Warmach's Forging Pool
Post by: Zska on January 01, 2016, 08:34:10 PM
Thank you for making that pool and keeping it alive. I'll keep leasing to you.

Happy new year to all!
Title: Re: Warmach's Forging Pool
Post by: warmach on January 02, 2016, 02:14:28 PM
Perhaps you could try running FIMK from an upstart script and have it auto-restart on shutdown.
Then from a post-start stanza http://upstart.ubuntu.com/cookbook/#post-start run a script or single command line command to start forging.

There is a working example here https://github.com/fimkrypto/fimk_chef_repo/blob/master/cookbooks/fimk/templates/default/fimk.conf.erb.
Thats a part of our chef deployment setup.

I may have implement this, but I don't think it is my problem.  The server doesn't shutdown, the FIM server process is killed.  I think it is a memory limit issue as I have this running on a low resource device. 

Title: Re: Warmach's Forging Pool
Post by: warmach on January 02, 2016, 02:40:45 PM

I wanted to give you a few updates on the pool. 

1.  The live server seems to have an issue that kills the FIM process at random.  It could be 12 hours or 12 days before it happens again.  This makes it hard to troubleshoot.  Rest assured that forging never stops.  I have two backup FIM clients running that forge for the pool.  The backup clients only forge and do not process payouts.  I am considering scrapping the live server and moving to my more reliable backup servers.


I decided to swap my live/backup servers.  My backup server ended up being much more reliable of a setup than my live setup.  The change should be transparent to the end user. 
Title: Re: Warmach's Forging Pool
Post by: warmach on January 06, 2016, 10:49:12 PM
I have updated my two backup servers to 0.6.0 fim server.  They are running fine and ready for the hard fork in two weeks.  I'm going to give them a couple more days to run before updating the live server.
Title: Re: Warmach's Forging Pool
Post by: warmach on January 11, 2016, 12:07:09 AM
I have updated my two backup servers to 0.6.0 fim server.  They are running fine and ready for the hard fork in two weeks.  I'm going to give them a couple more days to run before updating the live server.

The live server has been updated to 0.6.0 FIM server.  All servers are updated and running.  We are ready for the hard fork on 1/18.
Title: Re: Warmach's Forging Pool
Post by: warmach on January 15, 2016, 05:29:00 PM

Thanks for all those forging with my pool.  At our height we had 9 lessors, including myself.  I look forward to what this coming year has in store. 


We're half way through January and we've beat our previous record for most lessor at once.  We will have a 11 total lessors once our newest lease confirms! 

I'd like to welcome our new lessors and thank our long time friends who have been forging with us.
Title: Re: Warmach's Forging Pool
Post by: warmach on January 24, 2016, 06:42:14 PM


1.  The live server seems to have an issue that kills the FIM process at random.  It could be 12 hours or 12 days before it happens again.  This makes it hard to troubleshoot.  Rest assured that forging never stops.  I have two backup FIM clients running that forge for the pool.  The backup clients only forge and do not process payouts.  I am considering scrapping the live server and moving to my more reliable backup servers.


I figured out that this was a low memory problem.  I knew the server was running at about the max it could reasonably handle based on its memory.  I added more physical memory and the issue went away.  I think that when the java process hit that upper physical memory limit, it shutdown the FIM server to conserve memory for the OS.  My guess is that the FIM server needed more memory on occasion based on network activity and API calls I am making from the pool.  Either way, it's been running for a week with no hangups.
Title: Re: Warmach's Forging Pool
Post by: warmach on February 05, 2016, 03:08:17 PM

I wanted to give you a few updates on the pool. 

2.  I had been starting development of new features but realized that the current Perl scripts were very limited in what they could handle.  I have decided to re-code the pool software to use Python.  This will make future development easier and quicker.  I am currently in the process of re-coding and testing.


I have finished re-coding the pool scripts into Python.  I will have the new scripts running on my development server for a week or so to make sure the numbers match up against the live and backup servers.  Once we get past this final testing, I'm going to push them live and then start working on new pool features.  Thanks for your patience!
Title: Re: Warmach's Forging Pool
Post by: Eliphaz Fimk on February 05, 2016, 05:04:25 PM
Nice timing! People have asked about setting up FIMK mining pool and I've referred them to your public mining scripts on this forum. Are they still relevant? Why did you switch from Perl to Python?
Title: Re: Warmach's Forging Pool
Post by: warmach on February 05, 2016, 08:52:59 PM
Nice timing! People have asked about setting up FIMK mining pool and I've referred them to your public mining scripts on this forum. Are they still relevant? Why did you switch from Perl to Python?

Yes, the perl scripts I put up on this forum are what my live and backup pools have been running from the beginning.  They will work fine.

I switched to python because I have some new features I want to implement in the pool.  The design of python allows those updates to be easier and faster to write.  They could have been done in Perl, but they would have been messier to write and maintain.  In addition, python is a better fit for my programming style. 
Title: Re: Warmach's Forging Pool
Post by: OrgiOrg on March 11, 2016, 01:38:46 PM
i like your pool  :cheers: :thumbup:

which new features you would like to add?
Title: Re: Warmach's Forging Pool
Post by: warmach on March 11, 2016, 04:03:07 PM
i like your pool  :cheers: :thumbup:

which new features you would like to add?

Glad you like it! 

Right now, I'm working on setting up auto payouts at lease end.  It is taking a little longer than I expected because I needed to build an internal scheduling component to setup future payments to lessors. 

Do you have a feature request?
Title: Re: Warmach's Forging Pool
Post by: warmach on March 11, 2016, 04:07:16 PM
As I'm working on the auto payout, I've been asking myself the question on how long should I wait once a payout request is made before issuing it?  The standard confirmation of a transaction is 1440 confirmed blocks.  To me, this seems too long.  What do you feel is an appropriate time to wait?

In a broader question, while 1440 confirmations is official, what is the practical confirmations number before a transaction is unlikely to be reversed?
Title: Re: Warmach's Forging Pool
Post by: OrgiOrg on March 15, 2016, 10:39:44 AM
1440 conformations seems to be okay ... I don't have a problem in waiting for my free FIMKs  :cheers: :thumbup:
Title: Re: Warmach's Forging Pool
Post by: OrgiOrg on March 15, 2016, 10:43:00 AM
Glad you like it! 

Right now, I'm working on setting up auto payouts at lease end.  It is taking a little longer than I expected because I needed to build an internal scheduling component to setup future payments to lessors. 

Do you have a feature request?

- configure a payout range ... if I earn a amount of FIMK which I like to payout it should be automatically transfered to my wallet
- automatically re-lease ... that would be really cool
Title: Re: Warmach's Forging Pool
Post by: warmach on March 15, 2016, 03:47:13 PM
- automatically re-lease ... that would be really cool

I admit, that would be really helpful.  The problem is that I would need your secret key to renew the lease. 

Another option would be to use a script file to automatically renew the lease.  The only catch is you need an always on computer and ideally a running FIMK client.  I started a topic and uploaded a sample script here, https://forum.fimk.fi/index.php?topic=616.0

Once I get the auto payout piece done, I was going to work on end of lease notifications.  When a lease is close to ending, I would then send a blockchain message or possibly email with a reminder to renew the lease.  That is probably the best that I can do without actually holding the key to your account (which I don't want that responsibility!)  Other ideas on how to make this easier are welcome!
Title: Re: Warmach's Forging Pool
Post by: warmach on March 30, 2016, 11:32:34 PM
I have added new features to the pool software!  I've tested these to the best of my ability, but a test environment can never replicate the live system.  Please PM me or post here any issues you may have with these new features. 

Pool Settings
The pool software can accept messages sent via the FIMK network and will adjust the pool settings accordingly.

To adjust the settings, send a message on the FIMK network to the pool address above and include one of the following settings below. All messages sent to pool will send a response message indicating your message was received and processed.

SETTINGS
Pool will respond with message listing the pool settings for you account

AUTO PAY ON
Turn on lease end payouts. The new setting will take effect the next time you lease your balance to the pool.

AUTO PAY OFF
Turn off lease end payouts. The new setting will take effect the next time you lease your balance to the pool.

EMAIL yourEmail@email.com
Set an email address associated with your account.

REMINDER ON
Turn on lease end reminder emails. This feature requires an email to be linked to your account. The new setting will take effect the next time you lease your balance to the pool.

REMINDER OFF
Turn off lease end payouts. This feature requires an email to be linked to your account. The new setting will take effect the next time you lease your balance to the pool.

Title: Re: Warmach's Forging Pool
Post by: dance on March 31, 2016, 04:16:21 PM
I have added new features to the pool software!  I've tested these to the best of my ability, but a test environment can never replicate the live system.  Please PM me or post here any issues you may have with these new features. 

Pool Settings
The pool software can accept messages sent via the FIMK network and will adjust the pool settings accordingly.

To adjust the settings, send a message on the FIMK network to the pool address above and include one of the following settings below. All messages sent to pool will send a response message indicating your message was received and processed.

SETTINGS
Pool will respond with message listing the pool settings for you account

AUTO PAY ON
Turn on lease end payouts. The new setting will take effect the next time you lease your balance to the pool.

AUTO PAY OFF
Turn off lease end payouts. The new setting will take effect the next time you lease your balance to the pool.
I think that "auto pay" should be turned "on" by default for any new leaser. And maybe there should be a separate command for manual payout, and random message will be answered with not just a withdrawal, but with the list of available commands also. Something like "Command not recognised. You will be payed XXX fimks in 1440 blocks. The list of available commands is:".
Title: Re: Warmach's Forging Pool
Post by: warmach on March 31, 2016, 06:48:07 PM
I think that "auto pay" should be turned "on" by default for any new leaser. And maybe there should be a separate command for manual payout, and random message will be answered with not just a withdrawal, but with the list of available commands also. Something like "Command not recognised. You will be payed XXX fimks in 1440 blocks. The list of available commands is:".

Thanks for the input dance!  I wrestled with those two questions myself.  I would love more input from the community.  I chose the existing setup primarily because it was how the pool worked before the new settings.  If someone didn't go to pool site or this forum, then I still wanted them to be able to use the pool as expected.  Truthfully, I would bet that people would easily figure it out, but I at least would want to announce the change before putting it in place.

The added benefit of keeping auto payout disabled by default, the funds stay in pool and contribute to forging power.  There are still a couple forgers from the very beginning who still have a balance to collect.  I've contacted them via the blockchain but haven't heard from them.  While we wait for them to collect their balance, all the current forgers benefit with added forging power.
Title: Re: Warmach's Forging Pool
Post by: dance on March 31, 2016, 10:56:37 PM
The added benefit of keeping auto payout disabled by default, the funds stay in pool and contribute to forging power.  There are still a couple forgers from the very beginning who still have a balance to collect.  I've contacted them via the blockchain but haven't heard from them.  While we wait for them to collect their balance, all the current forgers benefit with added forging power.
Well, when funds stays in not-forging account, it helps other accounts to forge more too :)
Title: Re: Warmach's Forging Pool
Post by: warmach on April 01, 2016, 12:37:41 AM
Well, when funds stays in not-forging account, it helps other accounts to forge more too :)

Excellent point!  I had not considered it from that angle...   :cheers:
Title: Re: Warmach's Forging Pool
Post by: bittimikko on April 02, 2016, 11:08:04 AM
 :) Using options works
Title: Re: Warmach's Forging Pool
Post by: warmach on April 02, 2016, 03:53:41 PM
:) Using options works

Thanks for testing it out!
Title: Re: Warmach's Forging Pool
Post by: OrgiOrg on April 04, 2016, 02:58:47 PM
I have added new features to the pool software!  I've tested these to the best of my ability, but a test environment can never replicate the live system.  Please PM me or post here any issues you may have with these new features. 

Pool Settings
The pool software can accept messages sent via the FIMK network and will adjust the pool settings accordingly.

To adjust the settings, send a message on the FIMK network to the pool address above and include one of the following settings below. All messages sent to pool will send a response message indicating your message was received and processed.

SETTINGS
Pool will respond with message listing the pool settings for you account

AUTO PAY ON
Turn on lease end payouts. The new setting will take effect the next time you lease your balance to the pool.

AUTO PAY OFF
Turn off lease end payouts. The new setting will take effect the next time you lease your balance to the pool.

EMAIL yourEmail@email.com
Set an email address associated with your account.

REMINDER ON
Turn on lease end reminder emails. This feature requires an email to be linked to your account. The new setting will take effect the next time you lease your balance to the pool.

REMINDER OFF
Turn off lease end payouts. This feature requires an email to be linked to your account. The new setting will take effect the next time you lease your balance to the pool.


very very cool!  :thumbup:
Title: Re: Warmach's Forging Pool
Post by: warmach on April 04, 2016, 03:33:12 PM
Ok, now that the new settings are in place and live, what do I work on next? 

I was thinking of setting up a simple lottery for pool members.  Any useful or fun ideas?
Title: Re: Warmach's Forging Pool
Post by: OrgiOrg on April 04, 2016, 09:44:50 PM
pump the price of FIMK please  :P
Title: Re: Warmach's Forging Pool
Post by: eRoh on April 05, 2016, 09:44:14 AM
pump the price of FIMK please  :P

Somebody is already doing that. :-D
(remember that the whale bought quite a bunch at 20-30 satoshis)
Title: Re: Warmach's Forging Pool
Post by: OrgiOrg on May 11, 2016, 11:17:18 PM
Is your script allright? Got no mail and no automatic payout ...
Title: Re: Warmach's Forging Pool
Post by: warmach on May 12, 2016, 01:27:09 PM
Is your script allright? Got no mail and no automatic payout ...

Can you post or PM me your account number?  I am looking into this and think I understand what happened.  I just want to double check against your account activity.

Title: Re: Warmach's Forging Pool
Post by: OrgiOrg on May 12, 2016, 08:48:45 PM
PM send
Title: Re: Warmach's Forging Pool
Post by: warmach on May 13, 2016, 03:35:08 AM
PM send

I figured out where the bug in my code is.  When my code sees a new lease come in, it then schedules the reminder email and/or end of lease payout if the account has these options set.  In your case, you renewed the lease, then sent the messages turning on the auto payout.  My code is not properly looking for an existing lease and applying the new pool settings for this existing lease. 

Once you lease with the pool again, it will properly schedule the payout and email.  Since it only happens in this one special circumstance, these types of bugs can be tough to root out.  I will get to work on fixing this.

Thanks for letting me know so that I can fix it!
Title: Re: Warmach's Forging Pool
Post by: warmach on May 14, 2016, 03:12:52 PM
I figured out where the bug in my code is.  When my code sees a new lease come in, it then schedules the reminder email and/or end of lease payout if the account has these options set.  In your case, you renewed the lease, then sent the messages turning on the auto payout.  My code is not properly looking for an existing lease and applying the new pool settings for this existing lease. 

Once you lease with the pool again, it will properly schedule the payout and email.  Since it only happens in this one special circumstance, these types of bugs can be tough to root out.  I will get to work on fixing this.

Thanks for letting me know so that I can fix it!

I got the code updated.  It should now correctly look for an existing lease and then create the appropriate scheduled payouts and reminders. 
Title: Re: Warmach's Forging Pool
Post by: OrgiOrg on June 07, 2016, 10:46:52 AM
again no mail ... send you a PM!
Title: Re: Warmach's Forging Pool
Post by: warmach on June 07, 2016, 10:10:37 PM
again no mail ... send you a PM!

I checked both my database and email server and they both confirm the email being sent.  Try checking your spam folder. 
Title: Re: Warmach's Forging Pool
Post by: Puffi on June 19, 2016, 10:27:45 PM
The pool website cannot be reached. Is everything alright?
Title: Re: Warmach's Forging Pool
Post by: warmach on June 20, 2016, 02:06:11 AM
The pool website cannot be reached. Is everything alright?

Web server crashed. Forging continued on live and backup servers. I did a full server reboot and services restart.

We are good to go.
Title: Re: Warmach's Forging Pool
Post by: warmach on August 30, 2016, 06:21:54 AM

My pool's setup was that a user needed to request payout for their share of the forged funds.  As such, there are several user balances that are ready to be withdrawn, but it seems the accounts are inactive.  I say they are inactive because the have a zero balance and have not seen any activity in about a year.  I have reached out to them before telling them they still have a balance on the pool and am ready to do so again.

In your opinion, at what point in time do these funds become abandoned?  Is it reasonable to say that after a year of not using the pool and two messages indicating a balance to be withdrawn, I can claim these funds?

Right now, these unclaimed funds are helping the pool by being used in it's forging power.  So, they are not idle.  At the same time, I don't want to hold more FIMK than I have to. 

Thoughts?
Title: Re: Warmach's Forging Pool
Post by: Zska on August 30, 2016, 10:33:31 PM
I think year i enough if account is inactive and withdraw requests are published in forum
Title: Re: Warmach's Forging Pool
Post by: kani on August 31, 2016, 01:10:12 AM
I think a year is fair when combined with best-effort communication.  I suggest to create a post on this forum and on bitcointalk thread with accounts listed.  Then give another month to reply.
Title: Re: Warmach's Forging Pool
Post by: Pohatta on May 23, 2017, 09:46:10 PM
What happened to this pool? There seems to be no activity in the account for the last three weeks and also the web page seems to be frozen.
Title: Re: Warmach's Forging Pool
Post by: warmach on May 24, 2017, 07:38:30 PM
What happened to this pool? There seems to be no activity in the account for the last three weeks and also the web page seems to be frozen.

My bad...  The software has been pretty solid so I only check in on it ever couple weeks.  It has been longer this time because I was preparing and then away on vacation.  After that, my family was working through some illnesses. 

The server has been running and forging without interruption.  My pool script did have an error and stopped processing blocks.  This usually happens because of an unexpected character or something in a message.  I'm troubleshooting now and will update when I have more info.  Once fixed, the script will process the future blocks and credit the FIM to the forgers as usual.

Sorry.

Title: Re: Warmach's Forging Pool
Post by: warmach on May 24, 2017, 08:46:01 PM
My bad...  The software has been pretty solid so I only check in on it ever couple weeks.  It has been longer this time because I was preparing and then away on vacation.  After that, my family was working through some illnesses. 

The server has been running and forging without interruption.  My pool script did have an error and stopped processing blocks.  This usually happens because of an unexpected character or something in a message.  I'm troubleshooting now and will update when I have more info.  Once fixed, the script will process the future blocks and credit the FIM to the forgers as usual.

Sorry.

We are back up and running normally.
Title: Re: Warmach's Forging Pool
Post by: Pohatta on May 25, 2017, 12:46:39 PM
Excellent. Thanks!
Title: Re: Warmach's Forging Pool
Post by: heatinvest on May 25, 2017, 09:24:00 PM
If anyone wants to sell FIMK, PM your offers.
Title: Re: Warmach's Forging Pool
Post by: Zlotnik on October 14, 2018, 06:11:45 PM
What is the actual status of the pool?
Title: Re: Warmach's Forging Pool
Post by: warmach on February 11, 2019, 03:11:36 PM
What is the actual status of the pool?

After a number of hardware failures and rebuilds, I've decided that the pool is shutting down.  In FIMK's current state, is not worth rebuilding again.  If the devs decide to pick up project again, I may start the pool back up again.