Definitely replacing reliance on things like google docs and docusign would be most apparent in the beginning. In the future the ability to hold one single Sat or group of Sats in a mnemonic recoverable wallet that secretly have UCAN authorization at decentralized contact points throughout the web providing read and write access to an unbounded amount of encrypted data. The Sat is effectively an access key token to all of your encrypted data.
Theoretically, I could inscribe one sat (this isn’t really even needed if we extrapolate the ordinal convention, all sats are already numbered, we can do labelling in off-chain indexer for super private access-key-sats that look no different than normal) with a WNFS URI, that link would be public on mainchain; however, the data behind it would be encrypted and only accessible if you have the keys to the taproot wallet that holds it. Behind that initial WNFS URI could be a whole file SYSTEM, encrypted and backed up on IPFS. ALL your information, all your bookmarks, contacts, backups, apps, you can have a whole operating system tucked away in there… or a backup of your personally trained AI model… it’s unbounded. I want it so people can cross a border with 12 words and pick up where they left off.
It gets really interesting when we start seeing people preload Sat inscriptions with effectively decentralized operating systems and apps. People could purchase these inscribed Sats and add it to their collection of Sat-keys in their wallet. I haven’t thought through all the details yet but I can imagine someone buys one of these preloaded inscriptions, get a phone, WIPE IT/ROOT IT/DEGOOGLE IT (i guess this Sat has keys to the instructions for you to do all of this) get a taproot wallet on it somehow, recover your operating system with all your file backups.
Also the opportunity for anyone to just buy one of these preloaded sats with privacy features/apps/OS and start doing best practices while remaining in clownworld.
Right now off the jump you could set up a service like drop box with inscribed sats, like oh you and your family want a dropbox, take 100 sats and inscribe them all with same thing, divvy up to the 30 members of your family and save the other 70 for next generations… Bam each one of you have access to an encrypted file system for the family.
You also easily have a full html website on IPNS right now, it would be rather easy to set up a decentralized website builder dapp that allows anyone to create a fully functional static site that only they (the inscribe satoshi key holder) can change the information of. No BS with DNS or any other agency or board no KYC nonsense either.
brief overview of the scope of WNFS
Paper co-authored by Marko Vukolic about how Filecoin is anchored to BTC (best effort decentralization in lieu of merge mining with BTC)
https://dl.acm.org/doi/pdf/10.1145/3560829.3563563
EDIT:
Watch from 31:19 to ~39:30
-how UCANS and WNFS form a sort of rollup
I think this approach could see a sort of “transparent” layer of Bitcoin emerge.
Hold an inscribed Sat on mainchain taproot wallet that has UCAN write and delegation access over your WNFS data, this UCAN chain can trigger smart contract wallets on L2s like RSK.
A user could acquire one of these access key sats on mainchain, have the BTC go directly through powpeg into a SC on RSK, spin up a SC wallet with the remaining BTC and have their RSK SC wallet controlled via UCAN triggers from whatever device you delegate to (using the master key on BTC main.)
UCANs could be used to delegate to a SC wallets and provide a layer of privacy for BTC users interacting with L2s. WNFS is essentially a decentralized internet, user’s could make their own webpages or interact on other WNFS sites. There could be alternative BTC payment rails within this layer that rival lightning and are settled on whatever layer, LN, RSK, or mainchain. WNFS is more like IPNS than IPFS in that it includes a mutability (redirect/pointer) element but Content Identification CIDs are standard in this area where an offchain protocol (read: hyper-expressive smart contract) could be verified to be authentic based on the CID itself. Kind of a bitcoin native internet layer to a degree.
The killer app for this layer would be a Sovryn Browser wallet (or operating system) that has DNS, IPFS, NOSTR, RNS resolution built in. It would show BTC and other asset balances but you wouldn’t necessarily know or care which chain/protocol they were on unless you elected for that view in UI. Your “apps” would be equivalent of webapps like stacker or cashu… just install the webpage (IPFS/WNFS link) to homescreen type deal. They would operate as hyper-expressive smart contracts; the line kind of blurs, but if it’s tamperproof code that carries out operations that trigger BTC or other token movements on L2s and/or mainchain what else is it?
EDIT #2 (may 16):
this guy gives a ~2 minute rundown of UCAN way better than I can explain it…
This guy’s paper kind of inspired all of my thoughts on this.
BTC native file systems → BTC native internet with decentralized cloud computing where we bring back CPU “mining” except you are just renting CPU power out for BTC payment (probably rBTC I think this whole system is more or less implemented and anchored to Filecoin already, just need to use RSK instead of filecoin and use keys from BTC main address for security and principle.
I’m sure I’m making a ton of assumptions etc but trying to learn as much as possible.
I think something like this is inevitable… the argument can be made it is already built just implemented on filecoin. If this is possible and only requires a few smart contracts deployed on RSK and possibly mainchain I think it could prove to be a great opportunity. In the Sovryn Layers call Yago mentioned our justifications for shamelessly stealing good code; Protocol Labs is not something to overlook, and may not even need to be “stolen,” rather “adopted.” Though it would also be cool to just fork Filecoin or upgrade RSK to have a BTC native decentralized storage and cloud computing.
update:
info on the IPVM decentralized cloud computing execution layer
At this point I can not imagine a world where this does not happen (via protocol labs or a fork of the IPLD)