Forum Discussion
Multi member consortium - governance of shared resources
Thanks for the feedback Cody.
On fees, I'm asking about the subscription plan for the nodes, payable to Azure.
IBM allows consortium members to split between members:
"For priced plans in the IBM Cloud, don’t worry, you’re not alone, the cost of a blockchain network is shared across its members!
How does it work? First choose one of the following service plans. For monthly plans, each member organization must pay a network entry fee, and then purchase Fabric Peers which provide access to the network for deploying and executing chain code, and for updating the ledger." - https://www.ibm.com/blogs/bluemix/2017/08/ibm-blockchain-platform-generally-available/
Is a network split pricing option available on Azure?
My concern is that the entire existence of the network depends on 1 member being up to date on their fees within a consortium, for the network to exist. Splitting it reduces the risk and is more fair to consortium members
- Zaid Mahomedy (unsure why my profile appears as null on this forum)
Hi Zaid,
You shouldn't have a single party in control of any layer of the ledger stack; from cloud provider to node operator. As I mentioned above, each member on the network gets to deploy and control their own infrastructure. This means that the billing is separate and there is no centralized dependency. If one member doesn't pay their bills, there nodes will go down; however, a blockchain network should exist across multiple members and subscriptions, implying that the ledger will not be impacted.