-
Notifications
You must be signed in to change notification settings - Fork 1
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
Devise scheme for policing document reuse #81
Comments
Merkle inclusion proofs can mitigate this. There would have to be some batch-update merkle insertion bottleneck though. |
We also need a way to distinguish between documents that are or aren't reusable. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Certain documents might be considered to be owned under the umbrella of some external blockchain token. E.g. the minted value of token 1 may be derived from documents A & B; therefore token 2 cannot also be derived from A & B, but could instead be derived from C & D.
Likely this will have to be policed outside of the happ, because it is difficult to credibly maintain a list of nullifiers in the DHT. However, checking all document IDs on-chain is likely to by gas hungry if many documents are being aggregated.
The text was updated successfully, but these errors were encountered: