How can "chronicled" manage transaction fee with "open-registry-sdk"?


#1

As for “open-registry-sdk” case, I’m just wondering how “chronicled” manages the transaction fee if the client makes a transaction create/get/delete/update. because these actions have to be paid for miners via 20GWei(approx. $5) every transaction. For example, I buy temperature logger, then, the client registers it into ethereum on public chain, the user was allowed to get new blockchain address which is the logger’s. after that, the user updates temperature logger’s status many times. but the chronicled server(or own server) has to pay any transaction via ethereum.
Is this case, chronicled(or own server) must cover all transaction fees on your own, right?
Or, how can you balance out the paid fee?