Could you clarify? I see two promising proposals in this:
A) Redefining proof-of-work to mean one has to compile a GHC instead of
computing some obscure hashes only nerds care about
B) GHC will be compiled via contracts in the blockchain, to make sure
all mistake remain attributable
I like
Compiling GHC on a blockchain may not be economical, but running
GHC-compiled programs on a blockchain is definitely a great idea! I've even
come up with a paper title: A Secure Decentralized Transactional
Implementation of Spinless Tagless G-machine, aka Haskoin!
Time to recruiting a few
Leveraging the blockchain to compile GHC is a great idea!
Unfortunately the proof-of-work algorithm is still just wasted cycles.
On Sun, 1 Apr 2018, 07:28 , wrote:
> Overall this is a great proposal; glad we're finally modernizing! Still,
> it's got a pretty steep price tag
Overall this is a great proposal; glad we're finally modernizing! Still, it's
got a pretty steep price tag - maybe we can offset costs with an I.C.O.? ("GHC
Coin"?)
> El 1 abr 2018, a las 00:56, Gershom B escribió:
>
> Fellow Haskellers,
>
> Recently there has been much
Fellow Haskellers,
Recently there has been much work into creating a better and more
professional GHC development process, including in the form of DevOps
infrastructure, scheduled releases and governance, etc. But much
remains to be done. There continues to be concern about the lack of
use of