In an interesting interview between Coin Desk and Co-Founder and CEO of Clovyr, Amber Baldet, the latter shared reasons why taking gradual steps towards integrating public chains is preferred over having said chains constantly “shoved down enterprises’ throat”.

According to Baldet, implementing public chain right off the bat is not realistic given that there is no,

“credible on-chain privacy or very well-designed privacy preserving architectures for enterprise applications on public chains.”

She took the opportunity at hand to explain why enterprises shouldn’t be pressured into disclosing everything via public chains. The fact that said enterprises have agreed to test the waters is a big improvement enough, but rushing into such matters, according to Baldet, will only result in a complete shutdown.

From the very beginning, Baldet has been vocal about privacy, as it allows enterprises to remain unique by keeping their assets a secret and to ensure that “human consent over how the data we generate is handled,” as reported by Coin Desk. This is why Baldet is more so focused on bridging and building applications, with some control attached to upkeep privacy.

Baldet shared an example which went as follows:

“You don’t need to do a $20 million infrastructure lift on an existing application, so much as you simply enable that connectivity – and from there it’s a more organic way to build the ‘blockchain use case’. You don’t need to get 10 organizations around a table with a bunch of lawyers and spend six months deciding everything up front.”

Ultimately, she stressed the fact that such costly measures can prevent other enterprises from entering the blockchain sphere.

In particular, she shared:

“What we have right now is great for the 1% of businesses that can afford the expensive consultants and pay for the use case creation. […] So, we want to create those reusable components that dramatically lower the barrier to entry for the 99.99% of people in the world who have not even begun to explore what blockchain can mean to their business.”

While she is aware that giving developers the usability they are accustom to in a “private-first way” isn’t facilitative, she considers it as requiring attention and possible solutions.

158 +