Shared Address Solution

Technical Assumptions to be Verified

• It is possible to share an address among wallets

• It is possible for the owner of the address to authorize or deny transactions. If the address is shared among many clients, a transaction can be denied or authorized only by the address owner (the hub). A hub shares a richly funded address with clients who are interested in its service. The client can use such address a fee payer for an asset transaction upon approval from the hub owning the address.

Each customer wallet would contain one address per hub it is subscribed to. When it needs funds to create a new transaction, it uses this address as fee payer. The hub will then sign the transaction.

Technical Assumptions to be Verified

• Even in a shared wallet it is still possible to keep addresses separated and distinguish between the owners of the shared wallet

• One owner can hold his or her belongings in an address inside the wallet which no one else can manipulate.

• Using funds from an address requires the authorization of the real owner.

Upon client creation, a new wallet is created and shared with a hub. In this wallet there is an address private to the customer where the customer holds his valuables (assets) and a shared address where the hub holds some funds (bytes). In this image it is shown that a solution based on shared wallet would in effect create a network of shared wallets between hubs and end users. In such wallets, the end user address would be private to the end user and the shared address public to both. Creating a transaction using funds (bytes) from the hub shared address would require the hub to cosign.