I've had some push-back on the names of the proposed messages-- e.g.
"Invoice" in the accounting world means "I've already given you a
product or service, here is what you owe, payment terms, what forms of
payment are accepted, etc."
I think there might also be confusion about why we're defining our own
Invoice when there are at least three or four other existing standard
for electronic invoices.
So unless there is strong objection I'm going to change the names of
the messages:
Invoice --> PaymentRequest
Payment : ok as-is
Receipt --> PaymentACK (payment acknowledgement)
On Tue, Dec 4, 2012 at 12:06 PM, Mike Hearn <m...@plan99.net> wrote:
> Does it make sense to have this spec not include the details of
> bootstrapping? It's not complicated ....
BIP 0001 says: "If in doubt, split your BIP into several well-focussed ones."
I think it makes sense to keep the URI extension separate from the
binary message format.
> We should define a simple mechanism for extending the protocol now...
>
> message Invoice {
> extensions 1000 to max;
> }
Ok.
--
--
Gavin Andresen
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development
