Skip to content

Conversation

@halseth
Copy link
Contributor

@halseth halseth commented Apr 28, 2021

No description provided.

@halseth halseth mentioned this pull request Apr 28, 2021
2 tasks
// Since splitting the current share added new 32-byte
// randomness to the shares, we reset the childIndex.
child = left.Child(0)
s.childIndex = 0
Copy link
Contributor Author

Choose a reason for hiding this comment

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

maybe it shouldn't be reset, since if you split and merge, then start doing last shards, you get collisions again.

@joostjager
Copy link
Contributor

What's this @halseth? 🤔 😄

@halseth
Copy link
Contributor Author

halseth commented Apr 28, 2021

What's this @halseth? 🤔 😄

I'm fulfilling wishes: #5159 (comment)

@joostjager
Copy link
Contributor

Haha, nice, appreciated. Missed that earlier comment. If it wraps around, you can always fail the payment. Unlike the random index, which leads to silent collisions 👻

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