The gateway works already very fine, but there are a few minor issues:
I still don’t know how to get a link to the PPC Gateway in front of a paid article (at least not possible with the theme)
The content is fetched by the admin API and only gets rendered in a very simple html for the paying user. You can find a flask proxy in the repo which could simply stream the entire ghost page to the user, but if have a hard time setting it up (authentication, headers and so on)
I’d love to find contributors who could bring in their knowledge in as well
I have not yet planned to integrate other cryptos, but porting the implementation should be fairly easy:
Just exchange the iota client with another and listen to a given address. The rest stays the same I encourage you to fork the repo, maybe we can build a multi crypto version together.
The reasons i chose IOTA are the following:
Feeless: if paying for a post the price should range in the sub one dollar region, so any fee at all would destroy the incentive to use a pay per content offer.
Other than that it was the initial idea to implement a feeless version because all other solutions are costly (paypal, stripe, patreon, onlyfans etc.)
Scalable: other than blockchains, the IOTA Tangle scales, i.e. even if a million blog users use a such system at the same time it wouldn’t be an issue → still fast and feeless
Speed: other than my slow test_wallet in python, the official wallet needs around 2 seconds for a transaction. The internet user is impatient. Even 2 seconds is an eternity for them. Waiting an hour (bitcoin) or minutes (ethereum) for a transaction to confirm is out of question when you want to buy just an article for a quick read.
On top IOTA is very well known and connected here in the DACH region as a non-profit based in Germany. But afaik. it is less known around the world, that’s right.
I don’t have much experience with stripe. But as far as i know it is already part of the ghost stack. So maybe it would be better to build a pay per content solution with it within ghost (?) other than using my gateway approach.
Still, stripe is a costly payment provider and may prove not cost-effective in a pay per content situation.
I’m currently abusing the location field to manage an authors personal address. This is not optimal, but works, as this field takes all kind of strings.
I already looked into ghost but i’m not familiar enough with it to make a pull request.