HEAT Forum

HEAT Discussion => HEAT Server issues => Topic started by: warmach on August 07, 2017, 11:16:22 PM

Title: HEAT API Function Missing
Post by: warmach on August 07, 2017, 11:16:22 PM
I am adapting my FIMK pool code so that I am ready once the HEAT leasing goes active.  In updating my code, I found a FIMK API call that was not recreated in the HEAT API.  I have looked for similar functions that accomplish the same goal, but haven't found a new set of function calls that accomplish the same thing as the FIMK API does.

FIMK API Function:  getAccountLessors

This function returns that list of lessors to an account at a specific block height.  This is useful for determining how to divide up the block reward. 

As the leasing functionality is yet to be active, this function may still be added to the API.  Can anyone confirm this is being added?
Title: Re: HEAT API Function Missing
Post by: Eliphaz on August 10, 2017, 11:30:49 AM
It's likely added when leasing becomes available, supposedly within 1-2 months from now.
Title: Re: HEAT API Function Missing
Post by: warmach on December 27, 2017, 10:03:53 PM
I am adapting my FIMK pool code so that I am ready once the HEAT leasing goes active.  In updating my code, I found a FIMK API call that was not recreated in the HEAT API.  I have looked for similar functions that accomplish the same goal, but haven't found a new set of function calls that accomplish the same thing as the FIMK API does.

FIMK API Function:  getAccountLessors

This function returns that list of lessors to an account at a specific block height.  This is useful for determining how to divide up the block reward. 

As the leasing functionality is yet to be active, this function may still be added to the API.  Can anyone confirm this is being added?

Do we know if/when this API function will be implemented?  I don't see it listed for the 2.4.0 release.
Title: Re: HEAT API Function Missing
Post by: VonGraff on January 12, 2018, 03:44:29 PM
Hi Svante, out of curiosity: Is this API call still considered? Or would it better anyway to use microservices once released to set-up an automated pool?