What’s the status of this? I’m having trouble finding good information. I am very interested in using this type of subscription model in an app I’m working on. Is the contract safe to use? Is there work left to be done? Any information would be helpful. Thanks!
While AFAIK there are a few implementations of EIP-1337 that made it into production, I’d invite you to checkout superfluid as a subscription solution, which has been running in production for a few months now
Hey @matt , not sure if you have thought about on-chain subscription this way, but a EIP-3754 vanilla NFT standard may help take this further. Check it out here.
How do the developers ever plan on service providers being able to charge ERC20 tokens when ERC20 tokens require approval on the end user?
The end user could hypothetically approve the maximum amount (2^256), but that enables the possibility of the service provider to just take all their coins.
Wouldn’t an alternative coin standard need to be invented? The new approval function would take in a start date and a period length (monthly, yearly, etc.), and the provider could only charge once within the start date and period length (and then the start date would be updated to the latest timestamp)
hey, i came across ERC-1337 while researching payment standards for AI agents. Good spec, i think it stagnated because there was no real adoption case back then
there is now. AI agents need recurring access to APIs, data feeds, and compute. x402 is already seeing real agent payment volume and stripe just launched their own centralized agent subscription product last week. An open standard would prevent this from getting locked into proprietary rails
i’ve been thinking about what a modernized 1337 looks like. ERC-4337 integration for gasless renewals, ERC-8004 agent identity hooks, and a concrete ref impl
i’d pick up the revival work if the original authors are open to it. Timing feels right and i can put in the hours. Would kevin and the others be interested?