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
As part of #3294, we should add the feePurse to be used for paying for execution, to Zoe methods. We can separate this task from the actual charging of the feePurse. In effect, feePurses are required, but all calls are still free.
If we assume a lower-level stamp model (see #3294) that reduces spam generally, the only methods that require a feePurse are:
install,startInstance,offer,getPublicFacet
And the following are queries that only require a stamp and no charge:
makeFeePurse is not a query, but it's also no charge because to charge a fee for making a feePurse wouldn't be very sensical.
As part of this task, we should provide a version of Zoe that has the original API, with the feePurse partially applied. This will allow us to retain the old tests mostly unchanged, which lightens the load significantly.
The text was updated successfully, but these errors were encountered:
katelynsills
changed the title
Add chargeAccount arg to Zoe methods. Also partially apply the chargeAccount to produce original Zoe API
Add feePurse arg to Zoe methods. Also partially apply the feePurse to produce original Zoe API
Aug 10, 2021
As part of #3294, we should add the feePurse to be used for paying for execution, to Zoe methods. We can separate this task from the actual charging of the feePurse. In effect, feePurses are required, but all calls are still free.
If we assume a lower-level stamp model (see #3294) that reduces spam generally, the only methods that require a feePurse are:
And the following are queries that only require a stamp and no charge:
makeFeePurse
is not a query, but it's also no charge because to charge a fee for making a feePurse wouldn't be very sensical.As part of this task, we should provide a version of Zoe that has the original API, with the feePurse partially applied. This will allow us to retain the old tests mostly unchanged, which lightens the load significantly.
The text was updated successfully, but these errors were encountered: