Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Devs still have to build blockchain functionality. Which one of the hundreds if blockchains?

And devs still have to build things like "ownership of item changed, reflect it in the game", "this guy is a member if a clan in game X, so has to be member of clan X(?) in this game" etc.

The hand-wavy way crypto proponents approach this is maddening.



> Devs still have to build blockchain functionality. Which one of the hundreds if blockchains?

No, you can bridge NFTs between chains.

It's a solved problem.

> devs still have to build things like "ownership of item changed, reflect it in the game

No. They should query chain data directly. They need to setup an indexer and route any query through it.

You can attach attributes and state to NFT which can be replicated automatically between chains when someone bridges.


> No, you can bridge NFTs between chains.

Who is this "you"?

> No. They should query chain data directly. They need to setup an indexer and route any query through it.

Right. They "just have to query". They "just have to setup" something.

> You can attach attributes and state to NFT which can be replicated automatically between chains when someone bridges.

Who is this "you"? Who is this "someone"?

Again, the hand-wavy way crypto proponents approach this is maddening. And of course, there are exactly zero examples of this working in real life.


Yes, there will likely always need to be some work done on the dev side to enable any of those use cases. A lot of the tools/services to enable these and other uses are either being built or haven’t even been started yet, so for the moment the level of effort from individual teams is higher than it could be.


> Yes, there will likely always need to be some work done on the dev side to enable any of those use cases.

Not "likely". There will always be work to integrate.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: