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

"Use upstream" mode #107

Open
RCasatta opened this issue Nov 20, 2024 · 0 comments · May be fixed by #108
Open

"Use upstream" mode #107

RCasatta opened this issue Nov 20, 2024 · 0 comments · May be fixed by #108

Comments

@RCasatta
Copy link
Member

RCasatta commented Nov 20, 2024

A calendar server can operate by simply calling another upstream server for timestamping, while performing a transaction by itself if the upstream is not available or if the ots proof doesn't upgrade in a given timeframe.

This can be useful in two contexts:

  • For an official calendar server to save onchain fees.
  • For private entities that don't want to blindly rely on public calendars. By setting up a private calendar server with this mode, they both avoid trusting the calendar server and in the happy path avoid onchain fees.

The calendar server must expose two new parameters:

  • --upstream <URL>
  • --upstream-timeout N

Test harness must be written to ensure this feature is working correctly.

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 a pull request may close this issue.

1 participant