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.
Hope i could answer all your questions properly