4 ms·
But if all the telcos have to agree anyway, why not just use a centralized db with cryptographic signatures?
by TylerE 8y ago
But if all the telcos have to agree anyway, why not just use a centralized db with cryptographic signatures?
- abtinf 8y agoA key element of blockchain is the associated business logic (smart contracts). You need an immutable ledger and you need agreed upon business logic. You have your choice of consensus algorithms. Most of the time when people say blockchain, they mean the public networks like bitcoin or ethereum. But if you move to a private, permissioned network model, you can use consensus algorithms that don’t need mining and have very high transaction speeds. This is the approach taken by IBM Blockchain (via the Linux Foundation’s open source hyperledger fabric project) and a few others.
- pphysch 8y agoHow is a private blockchain functionally different from the average database?
- TylerE 8y agoIBM can charge 8-figure consulting fees instead of 7.
- abtinf 8y agoThe database is distributed among independent nodes. Each participant has their own copy of the immutable ledger and world state. Entries are cryptographically signed. All interactions run through smart contracts (you can’t just insert/update). You can form channels to engage in private transactions between a subset of the network, without divulging the existence of the transaction to the full network.
- Joeboy 8y agoSo eg. if telco A says a call was 8 minutes long and telco B says it was 15 minutes - what kind of smart contract / business logic decides how long the call was?
- zeroxfe 8y agoThat's conflict-resolution logic, and up to the peers to decide a priori (they will likely already have this, since it is not an uncommon scenario.) The value here (in addition to decentralized validation and consensus) is also in transparency and accountability, which disincentivizes fraud.
- Joeboy 8y ago> That's conflict-resolution logic, and up to the peers to decide a priori (they will likely already have this, since it is not an uncommon scenario.) Or you could just say you don't know?
- zeroxfe 8y ago> Or you could just say you don't know? Ugh, there's really no need for that! I actually worked in telecom for years, including integrating cellular network gear with third-party billing and settlement systems (like Amdocs.) Billing is hugely complicated and the third party systems cost in the millions of dollars in licensing and maintenance fees. They include thousands of rules to deal with the variety of scenarios (especially in conflict-resolution) that play out when peers settle with each other. The peers themselves work out large and complex legal contracts before they're encoded into these systems.
- Joeboy 8y agoI wasn't saying you don't know because you're ignorant about the telecoms industry. I think you don't know how to algorithmically resolve a conflict between two adversaries who assert significantly different versions of history, because nobody knows how to do that. I don't have your telecoms insider knowledge, but I feel fairly confident I know what would happen if a telco was suspected of inexcusable misreporting: people would check the data, have meetings and decide what they wanted to do about it. Maybe there's scope for automation of a bunch of deterministic stuff that would happen before it got to that point, but the actual resolution of actual conflict has to be a human process.
- Angostura 8y agoBecause then you have to decide who you are going to trust to run the database.
- root_axis 8y agoThat's not really a hard problem though, .e.g. git and github; any changes made on the host are easily and immediately detectable and verifiable, no block chain necessary.