Who am I? I am developing a new distributed end point to end point engine based on synchronous push. Any change by an author (or device) in a group gets therefore immediately pushed to the group's participants. This approach stands in stark contrast to the current remote-procedure-call client-server model that dominates today. HIVEWARE is the technology's name which stands for Hyperstructured Interactive Virtual Environment software. Hiveware is based on two ISO standards: C++ and SGML. Hiveware does not use any servers of any kind which eliminates by design DDoS attacks. Hiveware can be applied to any industry or target work that has a reasonable API.

All connections in Hiveware are known to their users (there may be 1000s per app), but are not connected. They connect when an author makes a change in an object. This mechanism is referred to as SDCDC, or synchronous distributed context distributed content. Thus, data transfer is brief.

All Hiveware data transfers are encrypted and thus any distributed app built on this Hiveware Engine exhibits automatically three invariants: security, privacy and ownership.

Lastly, since ownership may be transferred, anyone my develop a Hiveware dApp using the Hiveware Engine without cost for the Engine. The business model, however, is that a percentage of each transaction is passed back to the ancestor. This is different from the much detested subscription model where software is paid for without relation to the work done by it. That percentage is set by a smart contract with the descendant Hiveware dApp and its ancestor.