DIP-32: Email Welcome Packs with Testnet Tokens for Workshops at DEVCon(nect)

[0xkkonrad]

Description

Related DIP issue

Checklist

• [x ] Correct markdown (e.g. headers with ##, header surrounded by ---)
• [ x] syntax check
• [x ] filename is DIP-X.md (with X being the correct DIP number)
• [ x] header contains (in this order)
  • [x ] DIP
  • [x ] Title
  • [x ] Status
  • [x ] Themes
  • [x ] Tags
  • [x ] Authors
  • [x ] Resources Required (optional)
  • [x ] Discussion (with link to devcon forum)
  • [x ] Created (in the format year-month-day e.g 2020-4-20)
• [ x] contains these sections:
  • [x ] Abstract
  • [ x] Rationale
  • [ x] Implementation
  • [ x] Operational Requirements & Ownership
• [ x] PR title prefixed with DIP-X

[ligi]

Thanks for the proposal - just some small nits - formally only the Rationale is missing
We will discuss it later this week (Thursday)

[RiverRuby]

It may also be worth a collaboration with emailwallet.org team, a group funded by EF's PSE! This way the ticket email can directly be the receiver of the test token.

[ligi]

@vb7401 can you elaborate how the collaboration would work on a technical level?

[RiverRuby]

I'm not a full expert, just a friend/fan of that team haha. From my understanding, they are building a smart contract wallet for arbitrary email addresses email@domain.com, where transferring tokens is gated by sending an email from email@domain.com with the specified action. This works because each email comes with a DKIM signature from its domain.com mailserver, which can then be verified on-chain cheaply using a ZKP, from which the action specified (sending money, sending an NFT) can be authorized.

It may be too early stage for them to support the specific types of test tokens this proposal needs, but roughly I am imagining that these tokens can directly be given to the smart contract wallets for each of the pretix emails instead of doing a flow with a claim link + sending them to another wallet. From my understanding of the protocol, this can be done even if the email hasn't set up a wallet yet! The best person to contact is https://twitter.com/yush_g, one of the leads on the project.

In general, I am very bullish on emailwallet.org long-term being the right medium for "token airdrop to emails that have a ticket" solutions, especially in communities that are less web3 focused/pilled!

[ligi]

I would need to dig into email-wallet from the surface I have concerns wrt centralisation and readyness - just wanted to try it out and got this:

So I think for DEVConnect we should go with peanut

[RiverRuby]

Yep, they're working on shipping a lot of the functionality for Devconnect, so it might be too difficult to make everything work out. Perhaps for a future Devcon 😃🤞

[ligi]

Sorry but we went with the PCDPass faucet solution in the end: https://twitter.com/_pk910_/status/1721472568765345955

Your solution is great - but we want to encourage users to use PCDPass