├── README.md └── contributing.md /README.md: -------------------------------------------------------------------------------- 1 | # Awesome Blockchain Subscriptions [![Awesome](https://cdn.rawgit.com/sindresorhus/awesome/d7305f38d29fed78fa85652e3a63e154dd8e8829/media/badge.svg)](https://github.com/sindresorhus/awesome) 2 | 3 | *A curated collection of links for blockchain subscriptions and recurring payments.* 4 | 5 | Subscriptions, or any kind of recurring payments, aren't trivial to build on a blockchain. The underlying mechanisms only allows payers to move money from their account and no one else. Despite that, there are plenty of projects and hackers who are actively trying to go around these limitations. 6 | 7 | The list is periodically updated with new links. Click "Watch" in the right top corner to follow. Your contributions are welcomed. Add links [by yourself](contributing.md). 8 | 9 | ## Table of Contents 10 | 11 | * [Projects](#projects) 12 | * [Discussions](#dapps) 13 | * [Users](#users) 14 | * [Other](#other) 15 | * [License](#license) 16 | 17 | ## Projects 18 | 19 | * [TokenSubscriptions](https://github.com/austintgriffith/tokensubscription.com) - WyoHackathon 2018 winner. Set-it-and-forget-it token subscriptions on the Ethereum mainnet. 20 | * [8x](https://github.com/8xprotocol/monorepo) - Enables decentralised recurring payments on the Ethereum blockchain. 21 | * [Groundhog](https://groundhog.network/) - Friction-free subscription payments for consumers and merchants. 22 | * [Chronos Protocol](https://chronosprotocol.org/chronos-white-paper.pdf) - Facilitates continuous payments by adding a new, time-based dimension to money, taking subscriptions down to the minute or second. 23 | * [Lab10 Streems](https://github.com/lab10-coop/streem-poc) - Proof of concept on time-based payments. 24 | * [BitShares](https://bitshares.org/technology/recurring-scheduled-payments) - Smart contract platform with built-in support for recurring payments and subscription payments. 25 | * [PumaPay](https://github.com/pumapayio/puma-poc) - An advanced billing infrastructure for Merchants. 26 | 27 | ## Discussions 28 | 29 | * [ERC-948](https://github.com/ethereum/EIPs/issues/948) - First discussion on adding subscriptions on Ethereum. 30 | * [EIP-1337](https://github.com/ethereum/EIPs/pull/1337) - Subscriptions format proposed by [Gitcoin](https://gitcoin.co). 31 | * [Ethereum Subscriptions Standards](https://github.com/EthereumOpenSubscriptions/standard) - A set of proposed standards built on Ethereum. 32 | * [Gitcoin's Slack](https://gitcoin.co/slack) - Come join the #proj-subscriptions channel 33 | 34 | ## Users 35 | 36 | A list of dapps and companies which integrated or are interested in enabling decentralised subscription mechanisms. 37 | 38 | * [Gitcoin Grants](https://gitcoin.co/grants/) - Projects funded through monthly pledges. 39 | * [ETHGrants](https://ethgrants.com) - Recurring Ethereum funding via token subscriptions. 40 | * [Shopify](https://www.shopify.com/bitcoin) - Ecommerce platform. Future dApp. 41 | * [Wix](https://www.wix.com/) - Dead simple website creator. Future dApp. 42 | 43 | ## Other 44 | 45 | * [ChronoLogic](https://chronologic.network) - Debt smart contracts & temporal innovation on Ethereum. 46 | * [Coinbase](https://support.coinbase.com/customer/en/portal/articles/2168187-how-can-i-create-or-cancel-a-recurring-transaction-) - Centralised solution which enables cryptocurrency recurring payments. 47 | * [Ethereum Alarm Clock](https://github.com/ethereum-alarm-clock/ethereum-alarm-clock) - Schedules transactions for the future. It inspired the development of many projects from above. 48 | * [Software licences as non-fungible tokens](https://medium.com/collabs-io/software-licences-as-non-fungible-tokens-1f0635913e41) - Tokenising SaaS licenses. 49 | * [Subscription Services on the Blockchain](https://media.consensys.net/subscription-services-on-the-blockchain-erc-948-6ef64b083a36) - ConsenSys article highlighting the prospect of blockchain subscriptions. 50 | 51 | ## License 52 | 53 | [![CC0](http://mirrors.creativecommons.org/presskit/buttons/88x31/svg/cc-zero.svg)](https://creativecommons.org/publicdomain/zero/1.0/) 54 | -------------------------------------------------------------------------------- /contributing.md: -------------------------------------------------------------------------------- 1 | # Contribution Guidelines 2 | 3 | ## Table of Contents 4 | 5 | - [Adding to this list](#adding-to-this-list) 6 | - [Adding something to an awesome list](#adding-something-to-an-awesome-list) 7 | - [Updating your Pull Request](#updating-your-pull-request) 8 | 9 | ## Adding to this list 10 | 11 | First, thank you for your suggestions! 12 | 13 | Please ensure your pull request adheres to the following guidelines: 14 | 15 | - Search previous suggestions before making a new one, as yours may be a duplicate. 16 | - Make sure the list is useful before submitting. That implies it has enough content and every item has a good succinct description. 17 | - Make an individual pull request for each suggestion. 18 | - Use [title-casing](http://titlecapitalization.com) (AP style). 19 | - Use the following format: `[List Name](link) - Description.` 20 | - Link additions should be added to the bottom of the relevant category. 21 | - New categories or improvements to the existing categorization are welcome. 22 | - Check your spelling and grammar. 23 | - Make sure your text editor is set to remove trailing whitespace. 24 | - The pull request and commit should have a useful title. 25 | - The body of your commit message should contain a link to the repository. 26 | 27 | Then append your suggestion to the list of "Links Sent by Readers" section. Once in a while, I review this list and move links to other categories. 28 | 29 | See you there! 30 | 31 | ## Adding something to an awesome list 32 | 33 | If you have something awesome to contribute to an awesome list, this is how you do it. 34 | 35 | You'll need a [GitHub account](https://github.com/join)! 36 | 37 | 1. Access the awesome list's GitHub page: https://github.com/snario/awesome-cryptoeconomics 38 | 2. Click on the `readme.md` file: ![Step 2 Click on Readme.md](https://cloud.githubusercontent.com/assets/170270/9402920/53a7e3ea-480c-11e5-9d81-aecf64be55eb.png) 39 | 3. Now click on the edit icon. ![Step 3 - Click on Edit](https://cloud.githubusercontent.com/assets/170270/9402927/6506af22-480c-11e5-8c18-7ea823530099.png) 40 | 4. You can start editing the text of the file in the in-browser editor. Make sure you follow guidelines above. You can use [GitHub Flavored Markdown](https://help.github.com/articles/github-flavored-markdown/). ![Step 4 - Edit the file](https://cloud.githubusercontent.com/assets/170270/9402932/7301c3a0-480c-11e5-81f5-7e343b71674f.png) 41 | 5. Say why you're proposing the changes, and then click on "Propose file change". ![Step 5 - Propose Changes](https://cloud.githubusercontent.com/assets/170270/9402937/7dd0652a-480c-11e5-9138-bd14244593d5.png) 42 | 6. Submit the [pull request](https://help.github.com/articles/using-pull-requests/)! 43 | 44 | ## Updating your Pull Request 45 | 46 | Sometimes, a maintainer of an awesome list will ask you to edit your Pull Request before it is included. This is normally due to spelling errors or because your PR didn't match the awesome-* list guidelines. 47 | 48 | [Here](https://github.com/RichardLitt/docs/blob/master/amending-a-commit-guide.md) is a write up on how to change a Pull Request, and the different ways you can do that. 49 | --------------------------------------------------------------------------------