- From: Andrew Bransford Brown <andrewbb@gmail.com>
- Date: Sun, 24 Jul 2016 19:30:08 -0500
- To: Melvin Carvalho <melvincarvalho@gmail.com>
- Cc: Jeffrey Cliff <jeffrey.cliff@gmail.com>, Web Payments <public-webpayments@w3.org>
- Message-ID: <CAPS+YFJ86rAPVtsyrEGiFR20yJxgzTscTXkob3VgwFH7wRuLcg@mail.gmail.com>
*CommerceID EventType Description* Christine Terms-DeliverMethod Paypal: christine1983 Christine Terms-DeliverMethod Bitcoin: xyz Christine Terms-DeliverMethod Ethereum: xyz Christine Terms-DeliverMethod CreditCard: myMerchantID Andrew Terms-DeliverMethod Hand-delivered: 123 Main Street Christine Deliver Lasagna Hand-delivered: 123 Main Street, left on front door-step Computer Notice "Email notification sent to Andrew." Andrew Complete Andrew Deliver $25 CreditCard: myMerchantID, callback VISA Notice "$25 Payment received myMerchantID" Christine Complete Computer Notice "Contract complete." The above needs some review, but shows what is possible. How does VISA know the callback? The EventType terminology need some clarification and the Description structure needs some scenarios. Andrew B. Brown 10723 River Plantation Drive Austin, Texas 78747 (512) 947-8282 http://linkedin.com/in/keihatsu On Sun, Jul 24, 2016 at 6:37 PM, Andrew Bransford Brown <andrewbb@gmail.com> wrote: > Verification could occur automatically or by asking the recipient. Note > the "Deliver" event below that receives verification from Paypal of > delivery. Christine also verified: > > > CommerceID EventType Description > Andrew Offer $20 > Andrew Terms Lasagna > Computer Notice "This is a legal offer." > > Christine Terms $25 > Christine Counter-offer > > Andrew Accept > Computer Notice "This is a binding contract." > > Christine Deliver Lasagna > Andrew Complete > > Andrew Deliver $25 > Computer Notice "Paypal verification." > Christine Complete > > Computer Notice "Contract complete." > > Each event can fire a "snippet" to run custom code. > > Andrew B. Brown > 10723 River Plantation Drive > Austin, Texas 78747 > (512) 947-8282 > http://linkedin.com/in/keihatsu > > > On Sun, Jul 24, 2016 at 6:03 PM, Melvin Carvalho <melvincarvalho@gmail.com > > wrote: > >> >> >> On 25 July 2016 at 00:44, Jeffrey Cliff <jeffrey.cliff@gmail.com> wrote: >> >>> ...except ethereum classic is trading at 0.92$ and ethereum-non-classic >>> is trading at 12.77$....together less than they were not that long before >>> the fork was first announced. That said there are interesting incentives >>> going on wrt mining, and a full flight of capital hasn't happened, but >>> still: not quite the 'double spend both coins at risen price' effect >>> >> >> Good point. The the price has risen post fork. More on this story. >> >> >> https://cointelegraph.com/news/realm-of-ethereum-splits-into-two-coins-volume-hashrate-of-etc-surges >> >> What Id like to point out is that double spending coins in two markets >> should now be considered a reality, and not necessarily, a catastrophe. >> >> I suggest that conceptually it's a game changer. >> >> >>> >>> On 24 July 2016 at 16:25, Melvin Carvalho <melvincarvalho@gmail.com> >>> wrote: >>> >>>> Jesse Schell one said, "does anyone remember when the term 'viral' >>>> meant bad?" >>>> >>>> There is a very interesting development in digital payments this >>>> weekend when ethereum created a hard fork in order to redistribute capital. >>>> >>>> The community was split on whether or not this was a good idea, and in >>>> the end it happened anyway. >>>> >>>> But something strange happened. >>>> >>>> Someone created a fork of the original code base called "ethereum >>>> classic" >>>> >>>> What this meant was that anyone with a balance on either ethereum fork >>>> would automatically achieve a double spend of those electronic coins. >>>> >>>> Contrary to popular wisdom the market has responded by rising the price >>>> of both double spent coins, rather than, a flight of capital. >>>> >>>> We live in interesting times. We now have two ethereum chains fighting >>>> for supremacy with different algorithms. >>>> >>>> Anyone who bought in has essentially doubled their capital, as of now, >>>> due to double spend acting as a feature, rather than a bug! >>>> >>> >>> >>> >>> -- >>> GENERATION 26: The first time you see this, copy it into your sig on any >>> forum and add 1 to the generation >>> >>> >> >
Received on Monday, 25 July 2016 00:30:40 UTC