In one of my earlier posts, I tried to come up with many use cases that the Steem blockchain can fit into. With 0.20.x we have RC which will reduce the number of operations possible for an account. This will render the public chain difficult for some of the use cases like the citizen driven audits. Considering SMTs are little far away, use cases that includes on boarding of large numbers of users should consider private chains.

![](https://cdn.steemitimages.com/DQmRR7fJ1bM7CXn73dMzmxqgapcazLZ5pw4iWQKXWNsh9wD/image.png)
Source : [ https://commons.wikimedia.org/wiki/Category:Blockchain_illustrations#/media/File:Blockchain_Purple.jpg](https://commons.wikimedia.org/wiki/Category:Blockchain_illustrations#/media/File:Blockchain_Purple.jpg)

# How to use the Steem chain as a private chain

I don't want to discuss about the aspects like change in the currency symbol which is trivial. Rather I want to explore how the code base can be used with change in the initial token supply, use cases if any for SBD, voting for witnesses etc.

To itemize, in a private chain the following will not relevant or not possible.

1. SBD printing - this has to be disabled or a fake market data feed will have to be created
2. Voting and witnesses - will not be relevant
3. Resource Credit and Prevention of Spamming
4. Number of Witnesses (block forgers)


# How to handle the SBD printing ?

This is an aspect I am doubtful about. One method is to remove the SBD printing functionality completely, but then that will fork the code base away from the original code base. Perhaps its better to keep the functionality but don't use it.  The code for printing : will this steal CPU cycles ? I would like to hear from the community on better approaches.

# Voting

The voting process is not going to be relevant. Certain DPOS implementations like  [Aergo](https://www.aergo.io/) from [Blocko](https://www.blocko.io/) has removed the voting. The implementation is used by major companies for their supply chain tracking. They have listed certain companies like Samgsung who is pushing NextLedger for supply chain management and also offering it for the rest of the world. Considering this, not sure how Aergo plays out - but this is an aspect worth investigating.  Aego is implemented in Go-lang and someone hands on with GO-Lang can find details quickly. In the coming days I plan to test this out along with Quora which is a Etherium implementation by JP Morgan Chase. 

# Resource Credits

In the context of the private chain, the resource credits are not necessarily relevant. One idea I can think of is  start with a very large token supply and assign large amount of resource credits to the newly created accounts on the chain. Once again, this is going to be mostly a feature that is not needed in the private chain context and a method to enable - disable will be ideal.

# Number of Witnesses

The minimal number of witnesses needed as of now is 17 and perhaps its possible to tweak and the reduce the numbers with 13, 11, 7, 5, 3 etc ?


# Conclusion

The post is more about some ideas and would love to hear what everyone thinks of the points mentioned. Finding Enterprise use cases to the chain with minimal changes to the code is the objective for this discussion.