Execution instructions and pricing

[trvrggrep]

As a model developer I want to be able to associate model execution instructions and pricing terms with my model’s registration in Reppo.

Acceptance criteria

• The model developer is able to store model contract interfacing instructions in the Reppo model registration contract
• The model developer can specify the price per execution request
• The model developer can specify the accepted erc20 tokens for execution
• The Reppo model registration contract has access to model developer-specified pricing and terms for model execution
• A small protocol fee can be captured at the time of payment for execution

Decision

• We are leaving “model execution terms” out of this user story, and focusing on “model execution pricing”, as model execution terms would require an integration with Story for IP terms. Integrating an IP framework would greatly increase the scope of this user story.

Questions

• How should pricing work for execution streams?

[trvrggrep]

Sprint planning September 25, 2024

attendees: @DavideSilva @Trevor Jacka

a.c. updates

No work performed this sprint. Pushing to next sprint.

[trvrggrep]

Sprint planning October 9, 2024

a.c. oustanding:

No work performed yet for this sprint.

Will have this completed by end of sprint (7 days away).

[trvrggrep]

Sprint planning Oct 16 2024

a.c. updates:

• Model developer can specify token and amount of payment required for inference in the model-specific contract (haven't pushed)
  • The model developer can specify the accepted erc20 tokens for execution
  • The model developer can specify the price per execution request
  • The Reppo model registration contract has access to model developer-specified pricing and terms for model execution
• The registration contract contains metadata for the model-specific address and function for submitting inference request
  • The model developer is able to store model contract interfacing instructions in the Reppo model registration contract

Outstanding:

• A small protocol fee can be captured at the time of payment for execution
• will push to repo. Then ready for for QA.

[trvrggrep]

@DavideSilva this ticket was updated to include the a.c. "A small protocol fee can be captured at the time of payment for execution". Makes more sense to have it here. Lmk if you want me to create a separate story so that we can leave protocol fees out of this sprint.

[trvrggrep]

a.c. updates

• Protocol fee can be specified
• Will set at 10% of inference cost to begin with
• The fee is captured in the registry smart contract

Outstanding items:

• Create a protocol Safe multisig for capturing the fees in the future (needs ticket)
• Should the protocol charge fees for all inferences? What if there is no payment involved? (Needs ticket)