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

Runes: Restricted Issuer #3680

Closed
vforvilela opened this issue Apr 24, 2024 · 3 comments
Closed

Runes: Restricted Issuer #3680

vforvilela opened this issue Apr 24, 2024 · 3 comments

Comments

@vforvilela
Copy link

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.

struct Terms {
    ...
    issuer: Option<BitcoinAddress>, // Bitcoin address of the designated issuer
}

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.

@cryptoni9n
Copy link
Collaborator

pretty sure this is a clone of #3677

@HubertusVIE
Copy link

HubertusVIE commented Apr 25, 2024

I suggest adding an "issuer" field to the existing Terms structure.
issuer: Option, // Bitcoin address of the designated issuer

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.

@casey
Copy link
Collaborator

casey commented Apr 26, 2024

Continuing discussion in #3677. See comments there about using a fixed address.

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

No branches or pull requests

4 participants