35 ms·
The biggest thing I see standing in the way of this vision of the future is that it seems to actively go against IT best practices that medium/big orgs have in
by dcosson 11y ago
The biggest thing I see standing in the way of this vision of the future is that it seems to actively go against IT best practices that medium/big orgs have in place.
For instance, the github example in the article is cool but it seems like every company over ~100 employees switches to github enterprise or a similar self-hosted tool where every employee has an isolated account and it's only accessible on the corporate network/VPN.
I've looked around out of curiosity and I haven't really found any good information about building a secure IT organization while taking advantage of modern SAAS products (e.g. github, slack, circleci, docker hub, whatever else). It's basically taken as a given that if you want to be secure you'll have a corporate network in your physical office and all your important internal tools will be on that network (or an even more tightly locked down subnet). I'd love to read any resources to the contrary.
- williamcotton 11y agoMedium and large organizations should just run their own services that parse the blockchain and turn the data embedded in to Bitcoin transactions in to the state of names and owners. This service would read from the public network and but could itself be only accessible on the corporate network/VPN. This applies to all sorts of Bitcoin metadata protocols beyond just Blockshain ID, such as Open Assets, Blockcast, and Open Publish. All of these systems use the public key infrastructure of native Bitcoin wallets for identification and authorization so it's in the ballpark of SSH, a proven approach in corporate settings.
- ludbb 11y agoThere's a big gap in parsing the bitcoin blockchain vs parsing a local database. The blockchain is a public ledger so any (encrypted or not) information you store there can be retrieved by anyone. Downloading it is very slow, and parsing it in a reliable way, i.e. using bitcoind's rpc, is even slower. So you'll want to build an index from it, which you'll happen to store in a local database. So after all that you end up with a local database and public information that anyone can access. How is that useful for this purpose?