Given that twetch.app is routed to via DNS and then a majority of assets are loaded via…

1PZZ5ZPifCZ2ZvJrhXD5v3BbfYot6zPhqo (17984) · June 25, 2020

Given that twetch.app is routed to via DNS and then a majority of assets are loaded via the same resolver then technically Twetch can be censored right? Also taken down for a variety of reasons. What solution is there for entire app to be on BSV?

Replies

1PZZ5ZPifCZ2ZvJrhXD5v3BbfYot6zPhqo (17984) · June 25, 2020

Maybe this is what @1708 is working on that I've found recently?

1PZZ5ZPifCZ2ZvJrhXD5v3BbfYot6zPhqo (17984) · June 25, 2020

Furthermore... what is the thinking around data storage in relation to opscodes? Miners may prune the opscodes data right? So it's basically up to some service to act between a miner or a client to download the opscode before it's lost?

1PZZ5ZPifCZ2ZvJrhXD5v3BbfYot6zPhqo (17984) · June 25, 2020

If the miners don't care about the opscodes, how does it become... validated? Especially if they prune it? Seems low security - what am I missing? @9

1J6h7Bex83EVCGvamT5LMVm9MECX4bSquW (7355) · July 7, 2020

There are definitely protocols for registration + discovery.

If there is an incentive to source a given set of mined (therefore ‘validated’) data in the form of any OP_CODE, then a provider can choose to sync & maintain that data, serving it for a fee.

1PZZ5ZPifCZ2ZvJrhXD5v3BbfYot6zPhqo (17984) · July 7, 2020

Meaning the hash is on the bitcoin ledger of what is to be served? So a "ledger cdn" can serve it for a fee? I'd feel more comfortable with this if the data to be served can be sourced from the ledger without worry of being pruned.