H.265 as Proof-of-Work

>>2697825
>A genuine creative potentially not shit idea on biz
Where the fuck do you think you are?

>>2697896
I'm just bored
I imagine the proof to be something like:

"Find an image X that, when encoded with H.265, yields a bitstream whose hash has N leading zeros"

H.265 is slow to encode, fast to verify, exactly what's needed for PoW. However I fear that it's too easily reversible. Not sure.

What I like about the idea is that ASICs are a dime a dozen and extremely optimized for smart phones because battery life... It would be a level playing field from day 0.

If it worked, you could mine efficiently with your smart phone when it's charging.

>>2697825
you'd probably have better luck on /g/

>>2697980
Already tried a few months ago, no reaction
I fear only an expert on video codecs can answer this, of which there are very few worldwide

I'm not too familiar with how much of the standard is implemented in hardware beyond the decoding, but if the decryption of protected content also happens via the same ASIC you could probably use it in some sort of blockchain algorithm.

>>2697987
/g/ is still salty from getting spammed with Bitcoin threads for the past 7 years.

I'll ask my friend who works on blockchain technology. I work with it too, and in theory what you're saying should be doable, but I'm less familiar with low level PoW algos.

>>2698059
That's another idea, to utilize DRM functions, good thought.
>>2698250
Cool. Looking forward to any input.

What phones can do HW h265?

File: devil_girl.jpg (108KB, 378x500px) Image search: [Google]

108KB, 378x500px

Muh blockchain will make me live forever....

So desperate now.

>>2697967
This sounds cool, do you have the skills to make a proof of concept?

>>2698599
Most new phones do H.265 (HEVC)

>>2698638
I worked on crypto projects, but judging the viability of this PoW idea is beyond my circle of competence, sadly

I have another, much simpler coin idea, that I'll probably try first

How would this even work?

Can't you take the target bits needed to create a block and then just run it through a hevc decoder? The whole point of hash functions is that you can't get the input from the output.

>>2697967
There is a "finite" amount of images though what if there is no such image