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

Renames and changing where Payment Comes From #210

Merged
merged 2 commits into from
Sep 26, 2024
Merged

Renames and changing where Payment Comes From #210

merged 2 commits into from
Sep 26, 2024

Conversation

blakebyrnes
Copy link
Contributor

This PR has some modifications to where you specify payment.

Datastore Manifest Removes Payment

It's no longer part of the Datastore Manifest. We realized that once we introduced the idea of there being multiple Argon mainchain instances, you need to ensure payment is coming from whichever deployment the CloudNode or Datastore has targeted. Allowing a Datastore to specify its own payment chain when the cloud node needs to be the one to hook up payments is simply too complex.

Renames

DataDomains were renamed to simply "domains", and Escrows were renamed to Channel Holds. In Ulixee, Channel Holds are used to establish micropayment channels.

Localchain CLI Config

The localchain configs were added to the cloud cli.

@blakebyrnes blakebyrnes merged commit f0395c6 into main Sep 26, 2024
14 checks passed
@blakebyrnes blakebyrnes deleted the payment branch September 26, 2024 12:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant