frankTheTank72
frankTheTank72
Thanks for your input @hacdias Yes it is similar to StarageMax but as I understood the setup the StorageMax is set and will never change if the user not somehow...
Thanks for the answer @hsanjuan. I was not aware that the cluster is doing the calculation already in the background. I thought it is just looking at StorageMax. My proposal...
Ticket can be set to close- thx
check here https://github.com/burst-apps-team/phoenix/issues/201
In the text field - i would highlight the fee section Color or/and bold letters. Make the Background for the selection of buy or sell ( with the toggle )...
@deleterium this is covered with the neonclasic or ?
We should allow the following states : 
I can see your concern, but we have two parts Part i - avoid notForSale message We have right now this really generic in the pay() function- but we should...
From my point of view is this change working without a HF. We should create a new table which only store asset_id and tx_id and block height. In this case...
Currently we use the price information in the landing page , so i would keep the data stack as it is