PaySwarm Beta 1 Released - adds support for Web App Stores

Hot on the heels of the PaySwarm Alpha 6 release, PaySwarm Beta 1 has
been released. You can view the latest site on:

https://dev.payswarm.com/

All systems are live and seem to be working well with the new changes to
the code base. Improvements in this version of the code base include:

Support for Asset Re-Sale (Web App Stores)
------------------------------------------

Kumar McMillan, who has been involved with Mozilla's App Store
implementation, had stated that a decentralized app store concept is
important to them.

http://lists.w3.org/Archives/Public/public-webpayments/2013Mar/0002.html

Decentralized app stores have been a PaySwarm use case for a long while
now. The PaySwarm Alpha 6 release had around 80% of the code necessary
to support a decentralized Web App Store. Dave Longley added the other
20% of the code necessary to support this use case in the reference
implementation over the weekend.

Code on how to use this feature can be found here:

https://github.com/digitalbazaar/payswarm.js/blob/master/examples/publish-asset-for-sale.js#L106

The demo expresses an Asset (that could easily be a Web App) that
restricts listing the asset for sale with the following limits:

1. The asset is only valid for the date range provided, in this case
   it's 1 year from the date the asset was digitally signed.
2. The asset owner (the developer) should be paid a minimum of $0.01,
   or 80% of the re-sale price of the Web App set by the vendor
   (whichever is greater).
3. It specifically does not restrict PaySwarm Authorities from adding
   whatever payees they want to.
4. Vendors may only assign flat amounts to add to the total
   price, such as $1.00. That is, the Vendor can't say that they want
   80% of the total sale price as well.

Assume that the vendor's listed sale price is $1.00, then the listing
rules will result in a final price of:

Vendor's cut       : $0.195
Asset Owner's cut  : $0.795
Authority's cut    : $0.01
--------------------------
Total              : $1.00

We'll explain how listing restrictions work in more detail in a separate
e-mail to this mailing list.

----------------------------------------------------------------------

Detailed change log below:

  * Add warning modal for deleting vendor from budget.
  * Update payswarm context for listing restrictions.
  * Simplify budget display w/progress bar text.
  * Make payeeRateType and payeeApplyType optional in payee rules.
  * Wrap restrictions in asset w/listingRestrictions property.
  * Ensure purchase validity period is checked.
  * Only check listing signature against vendor (not asset provider).
  * Explicitly allow vendor to be different from asset provider.

-- manu

-- 
Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
Founder/CEO - Digital Bazaar, Inc.
blog: Aaron Swartz, PaySwarm, and Academic Journals
http://manu.sporny.org/2013/payswarm-journals/

Received on Tuesday, 5 March 2013 20:03:53 UTC