Hi David,

An attempt at humour? No, not intentionally! haha But anything I can do that 
can make people laugh is good in my books.

It’s a somewhat serious ‘rough sketch’ of a working blockchain (at least I 
think it’s working) and an example of how such a system would work; a 
springboard.  I got a bit creative with the addition of a Scheme interpreter in 
an attempt to make the system ‘useful’ rather than ‘wasteful’.  It’s 
incomplete, i know that at this point, but I thought I would share.  Writing 
explanatory blockchains is pretty hot right now.  I hope this one is simple 
(and correct!) enough to show the concepts in a familiar language.

—
Burton Samograd

> On Dec 18, 2017, at 4:00 PM, David McClain <d...@refined-audiometrics.com> 
> wrote:
> 
> Well, I thought, after delving deeper into the code, that it might be some 
> kind of sophisticated programmer humor, making a comment about the vast 
> amount of CPU cycles devoted to nonsensical computing or some such… 
> 
> - DM
> 
> 
>> On Dec 18, 2017, at 15:54, Pascal Bourguignon <p...@informatimago.com 
>> <mailto:p...@informatimago.com>> wrote:
>> 
>> 
>> 
>>> On 18 Dec 2017, at 23:31, David McClain <d...@refined-audiometrics.com 
>>> <mailto:d...@refined-audiometrics.com>> wrote:
>>> 
>>> umm… was this supposed to be some kind of joke? I’ll bite... I don’t get 
>>> it. I was actually hoping to learn something here...
>>> 
>>> But the code does look rather peculiar on close inspection. Why the use of 
>>> macros for pushing new transaction blocks? And the conversions to octet 
>>> vectors may work for strings, but not in general for arbitrary integer or 
>>> float values…
>>> 
>>> If it is supposed to be a joke, I’ll chuckle and just chuck the code…
>> 
>> I guess not: 
>> https://dev.to/damcosset/trying-to-understand-blockchain-by-making-one-ce4 
>> <https://dev.to/damcosset/trying-to-understand-blockchain-by-making-one-ce4>
>> It’s like, everybody will be busy implementing blockchains.  It’s the new 
>> fizz-buzz…
>> 
>> 
>> 
>> -- 
>> __Pascal J. Bourguignon__
>> 
>> 
>> 
> 

Reply via email to