Lots of questions will probably be forthcoming from the community. How is Boonex planning on protecting the modules? Will each module now have to call home to see if it is licensed? Come on Boonex, talk to us.
We are going to implement the system which is already done in Dolphin U. Site owner have to generate key&license on and enter them in dolphin, upon first paid module install the module is linked to this key&secret pair, so the module can't be installed on another site.
More detailed information on this process please. It is important for those currently using Dolphin to know the full process in details. I am already considering abandoning any future Dolphin products and just independently develop my site to add the features I need.
Site owner have to generate key&license on and enter them in dolphin - so dolphin site can ask for some info from the market for the site owner, for example list of bought modules.

Communication is performed using OAuth via https protocol.

Upon first install - module is linked to the particular key&secret, after first module install it is impossible to install it on another site.

Key&secret is linked to the particular site, so this pair have to be generated see more for every dolphin site you have.

Modules are updated automatically if they are in boonex market and free or was bought by the user.

All these is already working in Dolphin U - so you can try to see how it works!
So you are telling me that my site will be calling home to Boonex; how often will it be calling home. What happens if it can not call home to Boonex. You still are not providing the proper specifications, details, coding details on this.

And I really don't care what Dolphin U is doing or not doing.
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.