From: Luke Durback <luke.durback@gmail•com>
To: "Jorge Timón" <jtimon@jtimon•cc>
Cc: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Standard BIP Draft: Turing Pseudo-Completeness
Date: Thu, 10 Dec 2015 01:36:28 -0500 [thread overview]
Message-ID: <CAEj3M+ze9HU1KWoWT2nugw9hYY97jk_xsL8WUWqThq_wrXSAVg@mail.gmail.com> (raw)
In-Reply-To: <CABm2gDq3K2uUWx_itZQJH53EFOJKAWOLiy3NdHWGPvUOCm33wA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
Tomorrow, I'll work on writing a way to do voting on proposals with BTC
used as voting shares (This will be difficult as I do not know FORTH).
That seems like a fairly simple, useful example that will require loops and
reused functions. I'll add a fee that goes to the creator.
IMO, if you write a complicated system of scripts that's used frequently,
it makes sense to charge a fee for its usage. A decentralized exchange
between colored coins, for instance might take a small fee on each trade.
On Dec 10, 2015 10:10 AM, "Luke Durback via bitcoin-dev" <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> This, combined with the ability to make new transactions arbitrarily
would allow a function to pay its creator.
I don't understand what you mean by "a function" in this context, I assume
you mean a scriptSig, but then "paying its creator" doesn't make much sense
to me .
Could you provide some high level examples of the use cases you would like
to support with this?
[-- Attachment #2: Type: text/html, Size: 1367 bytes --]
next prev parent reply other threads:[~2015-12-10 6:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 1:35 Luke Durback
2015-12-10 4:03 ` Jeff Garzik
2015-12-10 4:23 ` Luke Durback
2015-12-10 5:38 ` Jorge Timón
2015-12-10 6:36 ` Luke Durback [this message]
2015-12-11 15:36 ` Jorge Timón
2015-12-11 15:38 ` Jorge Timón
2015-12-11 21:45 ` Luke Durback
2015-12-12 20:00 ` Jorge Timón
2015-12-12 21:01 ` Emin Gün Sirer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEj3M+ze9HU1KWoWT2nugw9hYY97jk_xsL8WUWqThq_wrXSAVg@mail.gmail.com \
--to=luke.durback@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jtimon@jtimon$(echo .)cc \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox