New Drips SDK with dev-friendly abstractions

[efstajas]

We currently don't maintain a real "SDK" for Drips anymore, and our old SDK has always been a pretty tight wrapper around the protocol. That means that additional external steps were (and are) required for actually creating high-level entities like "Drip Lists" and "Projects" on Drips, which have always been combinations of on-chain protocol functionality plus external metadata.

Both for our own sanity and potential external builders, it'd be great to have a new type of SDK that exposes "higher-level" functions like createDripList or claimProject or createContinuousDonation. Calling these functions should produce metadata and transactions that result in valid high-level Drips entities that also appear on the Drips app.

This would be great for our own use, and also (more importantly) provide a solid base for others to build on in contexts like Hackathons.

Some open questions:

• We use Ethers v6 for our own app, but Wagmi is very popular. Can / should we realistically support both?
• Ideally the SDK would not require bringing your own Pinata access token for publishing metadata. Could & should we create dedicated, tightly validated public API endpoints on our app that publish metadata for projects & drip lists via Pinata, that the SDK could then connect to?

[ryscheng]

I know @bitbeckers has been putting a lot of thought into similar questions for the Hypercerts SDK

He might be a good person to get feedback from