Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the concept of Payment network to Smartcontracts #18

Open
bitgamma opened this issue Mar 16, 2020 · 0 comments
Open

Add the concept of Payment network to Smartcontracts #18

bitgamma opened this issue Mar 16, 2020 · 0 comments
Labels
question Further information is requested

Comments

@bitgamma
Copy link
Contributor

In addition to #17.

Let's define a payment network as the sum of all buyer wallets and merchant wallets associated to their respective registries. At the moment there isn't a contract representing this directly (especially since the merchant registry is not used).

Maybe the KeycardWalletFactory could turn into the PaymentNetwork smartcontract which allows creating both merchant and buyer wallets as well as managing both registries. Since different policies can exist for payment networks different implementations might exist. We can defined an interface common to all networks for outside interaction.

Another solution is to have the PaymentNetwork be a contract which simply references to a specific KeycardRegistry and a MerchantRegistry. Wallets would then get access to both registries through this simple mapping contract. This is more or less equivalent to storing the address of both registries in each wallet, but allow changing them (if needed) with a single transaction.

wdty?

@bitgamma bitgamma added the question Further information is requested label Mar 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant