Skip to content

optimize ymax resolver submissions using invokeEntry rather than zoe offers #11966

@dckc

Description

@dckc

What

Eliminate the invitationMakers facet of the resolver; allow resolver clients invoke the settleTransaction method directly.

When all clients have migrated, we can eliminate invitationMakers.

Why

The resolver facet uses invitationMakers and continuing zoe offers even though submissions involve no exchange of assets. As of #11746 , this is no longer necessary.

Note the planner exo, whose methods are invoked directly, without making a zoe invitation. The resolver should work the same way.

How

The offer result from the makeResolverInvitation handler should be the service facet that has the settleTransaction method.

Note that both the portfolio-contract and portfolio-deploy package need updates.

See especially the delegate ymax control; invite planner; submit plan test in the portfolio-deploy package.

Update services/services/ymax-planner too.

As usual, pay close attention to packages/portfolio-contract/CONTRIBUTING.md. Make sure yarn test passes.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions