You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The feature known as "first signer pays" will allow the gyftietokens and gftorderbook contracts to cover the CPU and NET stakes for users. This is particularly important given the congestion and cost of resources on the EOS network.
This will address the now all to common error message as shown here:
In order to implement this feature, we'll develop a feature where the user will sign the transaction and the transaction will be forwarded to a custom web service, where a "noop" (no-operation) action will be prepended to the transaction. It will be signed by a Gyftie contract, and this will enable that contract/account to cover the resources
The underlying eosio feature was released with version 1.8, but this description/overview goes all the way back to 2018. This illustrates how critical development of this feature is, and even more so in light of increased staking requirements.
The feature known as "first signer pays" will allow the gyftietokens and gftorderbook contracts to cover the CPU and NET stakes for users. This is particularly important given the congestion and cost of resources on the EOS network.
This will address the now all to common error message as shown here:
![image](https://user-images.githubusercontent.com/32852271/76672903-d6a67180-6576-11ea-81e8-1cb6585d1b7e.png)
In order to implement this feature, we'll develop a feature where the user will sign the transaction and the transaction will be forwarded to a custom web service, where a "noop" (no-operation) action will be prepended to the transaction. It will be signed by a Gyftie contract, and this will enable that contract/account to cover the resources
The underlying eosio feature was released with version 1.8, but this description/overview goes all the way back to 2018. This illustrates how critical development of this feature is, and even more so in light of increased staking requirements.
EOSIO/eos#6332
The text was updated successfully, but these errors were encountered: