Skip to content

Conversation

@IAmKio
Copy link
Contributor

@IAmKio IAmKio commented Dec 16, 2024

Abstract

The Universal Orchestrator RPC aims to standardise the universal shape and requirements of a request for a solution from an arbitrary system managing an Ethereum wallet to, ultimately, an Orchestrator.

An arbitrary system could be a website, device, app, server program etc - anything that manages an Ethereum wallet, speaks Ethereum JSON-RPC and is looking to request solutions from an Orchestrator.

All solutions from an Orchestrator are ChA¹ (Chain Abstraction-first) by default.

Discussions: https://ethereum-magicians.org/t/erc-7845-universal-orchestrator-rpc/21885

@eip-review-bot
Copy link
Collaborator

eip-review-bot commented Dec 16, 2024

✅ All reviewers have approved.

Linting issues fixed
Adding temporary EIP to header
@github-actions github-actions bot removed the w-ci label Dec 16, 2024
Adding links to standard references
Changing links to relative
@github-actions github-actions bot added the w-ci label Dec 17, 2024
Fixing relative links to ERCs
@github-actions
Copy link

The commit 64dad91 (as a parent of 47519ee) contains errors.
Please inspect the Run Summary for details.

Changing link references to EIP
@github-actions github-actions bot removed the w-ci label Dec 17, 2024
ERCS/erc-7845.md Outdated
@@ -0,0 +1,644 @@
---
eip: 7845
title: Minimal Orchestrator RPC
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While there's no hard rule against it, I would recommend not using "minimal" in your title/description. The definition of minimal is extremely subjective and the term doesn't really provide useful information to readers. It would be better to highlight characteristics of your proposal that would differentiate from similar hypothetical proposals.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Understood - the name has been changed to Universal Orchestrator RPC. Just a note, i'm currently doing research to figure out if the term Orchestrator is still current.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have a slight preference for SVG images, if you can provide them. If not, PNGs are fine too.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately the tool i used, swimlanes.io - only exports in PDF or PNG. My apologies.

ERCS/erc-7845.md Outdated

## Abstract

> "Hey Google, swap my SHIB for Pillar"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We like to avoid mentioning specific products in proposals. It unfairly advertises projects that exist today over ones that come after going final.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed - this has been changed. Thanks.

ERCS/erc-7845.md Outdated

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 and RFC 8174.

The Orchestrator's external interface(s) that expose functionality to an end-user application or another system `MUST` use JavaScript Object Notation (JSON).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reserve backticks for inline code. The RFC 2119 key words should be unformatted uppercase.

ERCS/erc-7845.md Outdated

The Orchestrator's external interface(s) that expose functionality to an end-user application or another system `MUST` use JavaScript Object Notation (JSON).

The following data definitions are available and `MUST` **prefer chain abstraction (ChA¹)**, unless stated.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is unclear what "prefer chain abstraction" means.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have added an explanation for clarity.

ERCS/erc-7845.md Outdated

The following data definitions are available and `MUST` **prefer chain abstraction (ChA¹)**, unless stated.

The following sequence diagram shows the flow that this ERC aims to standardise:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should write as if the proposal was already Final. Maybe something like:

Suggested change
The following sequence diagram shows the flow that this ERC aims to standardise:
The following sequence diagram shows the flow of events in this proposal:

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahh understood - thanks, i'll check the rest of the document for this also.


The request definition is what a wallet sends to an Orchestrator for solutions to one or more problems. The request follows the specification from Ethereum JSON-RPC.

#### RPC
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This section seems to be re-explaining JSON RPC. I'm not sure how necessary it is.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whilst i understand what you're suggesting - for the sake of being clear and completion, i would prefer to leave this here to make it crystal clear that this is an Ethereum RPC request and that the params property is a Problem[].

ERCS/erc-7845.md Outdated
- towards address 0x50840CE036eEf2005d3c4d6f6Eb65f8116a01629
- with symbol USDC, amount 5

:::info
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure this'll render the way you want. Double check it after merging.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@eip-review-bot eip-review-bot changed the title Add ERC: Minimal Orchestrator RPC Add ERC: Universal Orchestrator RPC May 4, 2025
@eip-review-bot eip-review-bot enabled auto-merge (squash) June 30, 2025 19:08
Copy link
Collaborator

@eip-review-bot eip-review-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All Reviewers Have Approved; Performing Automatic Merge...

@eip-review-bot eip-review-bot merged commit ea32548 into ethereum:master Jun 30, 2025
18 of 22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants