> can offer that we can't currently do without the use of a Blockchain.
The real issue with responses like this is that you can do anything with computers anyway. The blockchain basically gives you a
* Globally writable database
* With stored procedures
* And row level security
Now, you can always swap out that with a centralised service. Turing machines can do stuff and machines can talk to each other. Whether it's possible to build a technically equivalent thing is not really the important question.
What tends to happen though is that the underlying infrastructure if supported by a profit-making company is that it has its own agenda and desire to control access. There's no real desire for the base layer to be open, it's not profitable in itself.
One of the more appealing things to me in the area is that there's a lot of work with shared interfaces. Working with the ERC721 spec I can easily make a non-fungible token that refers to a ticket at a conference, or right to claim a financial security, or game item, or has a link to a wiggly line or whatever I want. Someone else can build an auction contract, and my nft will automatically work in it, as will anyone elses. If you have control of the NFT you can pick which auction type/contract/service you want to use. I don't (and shouldn't) care, that's not the part I build or manage.
Finally, "but can't you do it with postgres and ..." is true but there's a huge shift that's happened. Before, sure, I'd have to have built all this stuff on chain and have all of the complete pain-in-the-arse stuff to deal with that comes with crypto. But now that all exists.
So to make, say, an in game item that people can re-sell, swap, etc, instead of
* Make a website
* Setup the DB
* Manage user accounts
* Manage payment information
* Code the sales, auctions, etc
* Build the integration with my game & my API
* Manage and maintain the server
to do it the traditional way. To do it on chain I
* Create a trivial NFT contract
* Build the integration with my game & a generic API
That's it. All the other work, auctions, etc. has been solved and built already. User accounts are already managed.
You can always solve it another way. The more interesting question is in which cases should you solve a problem in certain ways? Not everything makes sense on chain, the database is slow and public (and even for very cheap chains comparatively expensive), and the stored procedures are extremely limited.
However some things can fit well - do you need to create some kind of economic incentive & want to let market forces control things (for example, filecoin and paying people for storage)? Maybe just creating a token on existing infrastructure will fit your needs. If it does, does it make sense to build even more things yourself?
Disclaimers - I am currently doing contract engineering in this area but am not looking for work, have only small holdings and am not here to shill for anything.