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

Attempt to roll back stateless mode implementation in a single PR #2209

Merged
merged 3 commits into from
May 22, 2024

Conversation

mjfh
Copy link
Contributor

@mjfh mjfh commented May 22, 2024

why:

  • Stateless mode is not fully working and in the way
  • Single PR should make it feasible to investigate for a possible re-implementation

mjfh added 3 commits May 22, 2024 20:23
why:
+ Stateless mode is not fully working and in the way
+ Single PR should make it feasible to investigate for a possible
  re-implementation
@mjfh mjfh merged commit 2c32205 into master May 22, 2024
18 checks passed
@mjfh mjfh deleted the Cull-stateless-mode branch May 22, 2024 21:01
header: BlockHeader;
transactions: seq[Transaction];
): Result[void, string]
{.gcsafe, raises: [CatchableError].} =
Copy link
Member

@arnetheduck arnetheduck May 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

where is this strange code formatting coming from, and why is it part of this revert? This is not how we format proc anywhere else, we should generally move in the direction of the style guide / nep1 / nph.

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.

2 participants