BlockBill : The Blockchain-Powered Paperless Billing Solution
5 . Thanks to its sharding , it scales endlessly , withstands sudden spikes , and is much more resistant to outages than other blockchain networks observing trends from the past few years .
6 . 30 % of the gas fees go to the Developers . Pushing transaction information on a blockchain involves a sequence of computations together with several read-and-write operations across multiple nodes . The cost of energy spent for these operations on the blockchain is referred to as Gas-fees .
A blockchain-based app faces certain problems and NEAR provides solutions for most of these problems [ 20 ]. These are discussed in Chapter 6 .
Storing data on the blockchain can be very expensive , so we need something else to store a large amount of information ; this is necessary and inevitable to make it cost-effective . There is a peerto-peer hypermedia protocol known as the InterPlanetary file system ( IPFS ) for this particular purpose .
IPFS [ 25 ] provides us with a decentralized , trustful database . It is tamper-proof ; once added , data present cannot be changed , but a new version can be added , as it loads material from thousands of peers rather than a single centralized server . Each piece of information is cryptographically hashed to provide a secure , distinctive content identifier , or CID . The validity of IPFS content can be cryptographically verified . There is no duplicate content in IPFS . For example , two identical 1MB files would be saved only once on the same IPFS node if you tried to put them there , removing the need for duplication because their hash would provide the same CID .
We will discuss how the old billing systems transfer to our digital architecture in this chapter and how we implemented the various features , the technical choices we took , and their applicability .
The components that connect the various layers of the overall architecture are shown in Figure
4-1 .
1 . Frontend
A General Purpose Dashboard serves as the primary UX ( User Experience ) component that users will interact with and acts as the skeleton on which all the functionalities are erected . The user will navigate between all the functionalities available through the dashboard . The functions will hit the appropriate destinations ( Smart Contract or IPFS ), giving or receiving data . It has a clean , pleasing and intuitive UI ( User Interface ) design with appropriate entry fields relevant to the purpose of that screen . For instance , in the screen , enter the text / data corresponding to the sequence diagram in a given flow to where this screen belongs .
100 April 2023