-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Runes: Restricted Issuer #3680
Comments
pretty sure this is a clone of #3677 |
Agree with @cryptoni9n - it appears to be a clone. The difference is governance flag vs. issuer field. A field seems redundant as the deployer can be the governance holder. In the future, there could be a governance transfer to another address with an edict but again a special field would be redundant. That has no priority though, the flag is more important. |
Continuing discussion in #3677. See comments there about using a fixed address. |
To enhance the Rune protocol for issuing tokens reliant on a central entity, such as bonds, stocks, and asset-backed instruments, I suggest adding an "issuer" field to the existing
Terms
structure.The minting input would be restricted to transactions originating from the specified Bitcoin address, ensuring that only authorized transactions from the designated issuer can mint new tokens.
The text was updated successfully, but these errors were encountered: