[edgyquant]

Could it potentially be used to keep a distributed database of information collected by a large array of satellites orbiting something like the sun? I know I’m reaching here, and I’m pretty anti-cryptocurrency so I’m not looking for a nail really, but I just think distributed stuff is cool and the way blockchains work surely has some purpose when light lag is in play.

Like couldn’t it be used across a dyson swarm of rotating habitats or something as the transaction currency between them?

[lmm]

Only if the setup needs to be zero-trust. Systems of correspondent banks etc. worked very well even in times where worldwide communication took weeks, and even today there are e.g. traditional Islamic money-transmission networks that operate extremely efficiently because they rely on trust.

[edgyquant]

True I’ve been reading the culture series lately so my vision was off a truly decentralized series of habitats. I could see a trustless ledger being a solution to them all wanting to trade currency etc but not necessarily being a single coherent group. Then again as I said I may just be reaching.

[lmm]

It's hard to imagine that such a collection of habitats would have bigger cultural differences, and lower trust, than people at opposite ends of the historic Silk Road (say), though it's not completely impossible.

[beambot]

Crypto transactions featured heavily in Stross' Neptune's Brood for synchronizing transactions over interstellar distances:

https://en.m.wikipedia.org/wiki/Neptune%27s_Brood

Money was split into slow, medium, and fast variants -- the former of which was subject to speed of light limitations in the key signing for verification.

[andreskytt]

AFAIK Indian telecoms are using blockchain tech to maintain a distributed database of do-not-call numbers. Lag of up to 24 hours is ok and the relatively small number of parties is quite trustworthy. Basically they just use the bc for consensus and mirror it to a rdbms for read queries. That’s the only bc implementation I know that is both in production and is not speculation- or crime-fed.

[ChymeraXYZ]

Hey, I have a few serious questions, as I have really been trying to understand the benefits of using blockchain over "classic" stuff. They may sound like I'm questioning things, and that's because I am but with the goal to further my understanding.

> Lag of up to 24 hours is ok

So you could use any eventually consistent DB? Or a pub-sub type queue that you process at your leisure?

> and the relatively small number of parties is quite trustworthy.

I'm assuming this parties need to apply/be invited? How is that different than needing an API key?

> Basically they just use the bc for consensus

Consensus of what exactly? AFAIU the consensus is about the state of the data on the blockchain, with sanity checking against itself, not about if many parties agree if "this number should be blocked"

> and mirror it to a rdbms for read queries.

I was always under the impression that it's quite fast to read the data off the blockchain if you are a node. Am I misunderstanding something or is what they are doing just overkill?

[edgyquant]

It will never be as quick to loop through a giant blockchain to generate a dataset and then do something with it as it is to run queries in a highly optimized database that mirrors the end result of looping through that ledger. Blockchains are kind of like git and you need to move through each commit before you can get a snapshot of the current data.

[tromp]

Some blockchains are far more optimized than that. Like Mimblewimble blockchains in which all spent outputs can be permanently eliminated without hampering verifiability of the UTXO set.

[lmm]

Blockchain in the sense of proof-of-work mining? A Merkle tree might make sense, signed updates might make sense, but I don't see that mining adds value in that use case.

[tromp]

PoW, besides being the simplest way to reach consensus, also allow for a fair distribution of new coins.

[lmm]

Huh? How does distributing new coins help with maintaining the do-not-call list?