Add ERC: Payment Channels with Signed Vouchers#1592
Open
kimbo128 wants to merge 7 commits intoethereum:masterfrom
Open
Add ERC: Payment Channels with Signed Vouchers#1592kimbo128 wants to merge 7 commits intoethereum:masterfrom
kimbo128 wants to merge 7 commits intoethereum:masterfrom
Conversation
Made-with: Cursor
Made-with: Cursor
Collaborator
File
|
Made-with: Cursor
Made-with: Cursor
|
The commit e98790b (as a parent of d094f40) contains errors. |
abcoathup
reviewed
Mar 11, 2026
ERCS/erc-8184.md
Outdated
|
|
||
| ## Abstract | ||
|
|
||
| This specification defines unidirectional payment channels for streaming micropayments using [EIP-712](https://eips.ethereum.org/EIPS/eip-712) typed signed vouchers. A consumer opens a channel by depositing [ERC-20](https://eips.ethereum.org/EIPS/eip-20) tokens into escrow, designating a provider and an expiry timestamp. The consumer then issues incrementally increasing off-chain signed vouchers to the provider in exchange for services. The provider can claim the highest voucher on-chain at any time. Channels settle via provider claim, consumer close after expiry, or cooperative close with mutual signatures. |
Contributor
There was a problem hiding this comment.
Suggested change
| This specification defines unidirectional payment channels for streaming micropayments using [EIP-712](https://eips.ethereum.org/EIPS/eip-712) typed signed vouchers. A consumer opens a channel by depositing [ERC-20](https://eips.ethereum.org/EIPS/eip-20) tokens into escrow, designating a provider and an expiry timestamp. The consumer then issues incrementally increasing off-chain signed vouchers to the provider in exchange for services. The provider can claim the highest voucher on-chain at any time. Channels settle via provider claim, consumer close after expiry, or cooperative close with mutual signatures. | |
| This specification defines unidirectional payment channels for streaming micropayments using [EIP-712](./eip-712) typed signed vouchers. A consumer opens a channel by depositing [ERC-20](./eip-20) tokens into escrow, designating a provider and an expiry timestamp. The consumer then issues incrementally increasing off-chain signed vouchers to the provider in exchange for services. The provider can claim the highest voucher on-chain at any time. Channels settle via provider claim, consumer close after expiry, or cooperative close with mutual signatures. |
abcoathup
reviewed
Mar 11, 2026
ERCS/erc-8184.md
Outdated
| Existing on-chain payment models are poorly suited for this pattern: | ||
|
|
||
| - **Direct transfers** require a transaction per request, making sub-cent payments infeasible due to gas costs. | ||
| - **Job escrow models** (e.g. [ERC-8183](https://eips.ethereum.org/EIPS/eip-8183)) require upfront job specification, evaluator attestation, and multiple state transitions. This is appropriate for discrete deliverables but introduces unnecessary overhead for immediate request-response services. |
Contributor
There was a problem hiding this comment.
Suggested change
| - **Job escrow models** (e.g. [ERC-8183](https://eips.ethereum.org/EIPS/eip-8183)) require upfront job specification, evaluator attestation, and multiple state transitions. This is appropriate for discrete deliverables but introduces unnecessary overhead for immediate request-response services. | |
| - **Job escrow models** (e.g. [ERC-8183](./eip-8183)) require upfront job specification, evaluator attestation, and multiple state transitions. This is appropriate for discrete deliverables but introduces unnecessary overhead for immediate request-response services. |
abcoathup
reviewed
Mar 11, 2026
| @@ -0,0 +1,506 @@ | |||
| --- | |||
| eip: 8184 | |||
Contributor
There was a problem hiding this comment.
Suggested change
| eip: 8184 | |
| eip: 8190 |
Assigning next sequential EIP/ERC/RIP number.
Numbers are assigned by editors & associates.
Please also update the filename.
abcoathup
reviewed
Mar 11, 2026
ERCS/erc-8184.md
Outdated
| title: Payment Channels with Signed Vouchers | ||
| description: Streaming micropayments via EIP-712 signed vouchers over unidirectional ERC-20 payment channels. | ||
| author: Artur Markus (@kimbo128) | ||
| discussions-to: https://ethereum-magicians.org/t/erc-8184-payment-channels-with-signed-vouchers/00000 |
Contributor
There was a problem hiding this comment.
Please create a discussions topic in Eth Magicians.
https://ethereum-magicians.org/c/ercs/57
Made-with: Cursor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This ERC proposes a standard for unidirectional payment channels using EIP-712 typed signed vouchers, designed for streaming micropayments in high-frequency service commerce -- particularly AI agent-to-provider interactions.
Key Features
Relationship to ERC-8183
This standard is complementary to ERC-8183 (Agentic Commerce):
Production Reference
This pattern has been in production on Polygon Mainnet since late 2025 as DrainChannelV2, powering a marketplace of AI service providers.
Contract: 0x0C2B3aA1e80629D572b1f200e6DF3586B3946A8A
Note
The Ethereum Magicians discussion thread will be created once forum trust level requirements are met. The discussions-to field will be updated accordingly.
Made with Cursor