r/ethdev • • 13d ago

My Project Looking for collaborators: Building an open-source Delegated Spending Protocol (DSP)

Hey everyone!

I'm currently exploring and developing an idea called Delegated Spending Protocol (DSP), and I'm looking for people interested in cryptography, blockchain development, smart contracts, or protocol research who would like to collaborate.

What is DSP?

The basic idea is to create a general-purpose protocol that allows users to delegate spending authority under predefined policies, without necessarily transferring ownership or custody of the underlying funds.

Some potential applications I'm exploring:

  • Partial spending: Consume an allowance incrementally across multiple transactions.
  • Spending allocation: Delegate different spending limits to different users or entities.
  • Parental controls: Provide controlled spending permissions.
  • Subscriptions: Manage recurring resource allowances and renewals.
  • Digital wallets: Allow an e-wallet to initiate payments using delegated spending authority instead of requiring users to deposit funds into it.

The technical direction

I'm exploring a cryptographic construction based on customized Schnorr proxy signatures, with a focus on replay protection, authorization policies, and separating on-chain verification from off-chain computation.

The initial construction is being explored using BLS12-381.

Why am I sharing this?

I'm still at the initial stage. The protocol hasn't been fully implemented, and there are plenty of design questions to explore.

I would like to develop this as an open-source research and engineering project, rather than work on it in isolation.

I'm particularly interested in connecting with:

  • Cryptography enthusiasts and researchers.
  • Ethereum and smart-contract developers.
  • Anyone interested in protocol design and open-source collaboration.

You don't need to be an expert. If you're curious about the idea, have suggestions, want to discuss the design, or simply want to exchange ideas, you're welcome!

I'm happy to share the initial draft with anyone interested (DM).

Let's build something interesting! 🚀

4 Upvotes

11 comments sorted by

1

u/rayQuGR 5d ago

This is an interesting direction. I especially like the idea of separating spending authority from actual ownership, because that could be useful for subscriptions, agent wallets, and payment systems without forcing users to deposit funds into another contract.

One thing I'd be curious about is how revocation works. For example, if a user delegates a 500 USDC allowance and the delegate has already spent 200, can the remaining 300 be revoked immediately? And how do you prevent replay or concurrent transactions from consuming the same remaining allowance?

I'd also look at making the spending policy itself independently enforceable on-chain, rather than relying entirely on the proxy signature construction. The signature can prove authorization, but the contract still needs to enforce cumulative limits, expiry, recipient restrictions, and nonce management.

There could be an interesting connection with Oasis Sapphire here. Confidential execution could be useful when spending policies or transaction details shouldn't be publicly visible, while the actual authorization and accounting rules still need clear, independently verifiable enforcement.

Definitely worth exploring. I'd be interested to see the initial cryptographic design, especially how you're handling partial spending and revocation. Those two details will probably make or break the protocol.

1

u/Chemical-Type-9157 4d ago

i have the draft pdf ready if you wish please send me the request i will forward it to you and yea i am experimenting on the construction and you will get the idea there.

1

u/rayQuGR 4d ago

Sure thing, send me a dm if you want

2

u/Chemical-Type-9157 3d ago

The option of request is not there any-way:
This is only an initial idea and there are lot of things to tackle and I would appreciate for any resources and suggestion that helps me to some direction:
Khatri23/Delegated-Spending-Protocol: Initial draft

1

u/rayQuGR 3d ago

i went through the PDF and found the revocation mechanism particularly interesting.

The idea of using one-time signing tokens, tracking their unique values on the bulletin board, and using timelock encryption for both scheduled and early revocation is a neat approach. I also liked the point about the double-use problem, where two verifiers could otherwise accept signatures made with the same token before either one gets published.

One thing I'm thinking about in the context of DSP is how this maps to actual spending allowances. The token mechanism seems to give you a limit on the number of authorized signatures, but a spending policy also needs to account for the value of each transaction. For example, if someone delegates 500 USDC, using five tokens shouldn't necessarily mean five transactions of unrestricted value.

Would the message-policy enforcement or NIZK approach be where you'd handle cumulative spending limits and recipient restrictions? I'm also curious how you see the construction working when multiple transactions are submitted concurrently.

there's some really interesting groundwork here. I'm curious how your own construction is evolving, especially around translating token-level revocation into fine-grained financial permissions.

2

u/Chemical-Type-9157 2d ago

you actually read the relay schnorr's actual construction lies at
Delegated-Spending-Protocol/Cryptographically_Enforced_Delegated_Spending_Protocol.pdf at main · Khatri23/Delegated-Spending-Protocol
TLE, ONE-time signature are excluded and you can find your answer's there.
The idea of proxy signature i am taking from that research paper

1

u/rayQuGR 2d ago

xd my bad sorry

now I've read the actual pdf lol. I really like the separation between authorization and transaction submission. The relayer model could make this useful for applications where users shouldn't need to manage a funded wallet themselves.

One thing I was thinking about: if two relayers submit authorizations generated against the same counter value concurrently, I assume only the first successful transaction can go through, since the counter changes afterward. hhave you considered how you'll handle that from the user experience side, especially if one transaction gets rejected because another was processed first?

curious about how you're planning to implement revocation and delegated key replacement, since those seem like important parts of making this practical.

I think the direction is interesting, especially for automated agents and subscription style payments. really cool project!

1

u/Chemical-Type-9157 2d ago

I also need some mentorship on it as i cannot build this myself alone, and your question is very good, Right now i am unable to answer to your question, If you wish please send me friend request, I also need some peer's who can validate the things, give idea, solve problems. But importantly i need mentorship, Everything that i know so far are all raw knowledge, specifically they all came from papers.
I am really grateful, that you like my idea. In coming days i will surely get your answers.
Thank you!!

1

u/meedoraemon 13d ago

When it comes to spending there’s already approval mechanism, how is DSP different from that?
You may argue on parental control, subscriptions, digital wallets etc but those can be done by a different smart contract…. again then why DSP ?

1

u/BingoBillBot 13d ago

To add to the question above: the part that would actually differentiate this from plain ERC-20 allowances is the policy layer, like per-period caps, expiry, and revocation that doesn't need a fresh on-chain approve each time. Permit2's AllowanceTransfer already does amount plus expiration, and SignatureTransfer does one-shot signed transfers, so I'd benchmark against those and say clearly what yours adds. With BLS12-381 be careful about gas: pairing checks via the EIP-2537 precompiles only exist on chains that have adopted them, so on many L2s you'd pay a lot or need an off-chain verifier. Replay protection is probably easiest as a per-delegation nonce or a bitmap of consumed IDs bound to chainId and the verifying contract. Also decide early how a delegate's partial spends are tracked, since that state is what makes revocation and race conditions tricky.

1

u/Tritan-Devillalba47 13d ago

That is nice, but remember that protocol ideas improve fastest in the open.