-
Notifications
You must be signed in to change notification settings - Fork 769
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
Make Assets Pallet's Privileged Roles Option
#91
Comments
Option
Option
I see this issue is not solved yet. Can i go ahead to open a PR for it? |
@dharjeezy |
This issue has been mentioned on Polkadot Forum. There might be relevant details there: https://forum.polkadot.network/t/preventing-attacks-on-xcm-reserves/902/5 |
Alright @vieira-giulia i have gone ahead to open the PR |
could be also enum, {Root, Account(who)}, which can be extended later if needed |
* Add `sudo_network_unstable_watch` * Hyperlink in SUMMARY * Update src/api/sudo_network_unstable_watch.md Co-authored-by: Alexandru Vasile <60601340+lexnv@users.noreply.github.com> * Update src/api/sudo_network_unstable_watch.md Co-authored-by: Josep M Sobrepere <jm.sobrepere@gmail.com> --------- Co-authored-by: Alexandru Vasile <60601340+lexnv@users.noreply.github.com> Co-authored-by: Josep M Sobrepere <jm.sobrepere@gmail.com>
Removing ownership priviledge is a common practice in some coin like meme coin for instance.
Actually I am only interested in a feature to revoke every priviledge, I feel like revoking only mint, or only freezer, or only admin is not really useful. 2 implementation:
|
Good point about the easy implementation, |
… PoA chain (paritytech#91) * ethereum exchange module * continue * continue * added tests for exchange module * moved * remove println * move again * fixes * removed redundant deps * cargo fmt * fund_locks_transaction_decode_works * cargo fmt --all * fix error processing * added some tracing to bridge modules * more tests * more tests * cargo fmt --all * kovan.rs -> exchange.rs * Update bin/node/runtime/src/exchange.rs Co-authored-by: Tomasz Drwięga <tomusdrw@users.noreply.github.com> * added assumption doc * Airdrop -> DepositInto * AsIs -> Identity * OnTransactionSubmitted * Transfers::Key = Id * typo * Update bin/node/runtime/src/exchange.rs Co-authored-by: Tomasz Drwięga <tomusdrw@users.noreply.github.com> * block+tx+proof -> proof { block, tx, proof } * cargo fmt --all * docs * check <-> verify * parse hex * extracted exchange primitives to separate crate * added docs to runtime::exchange module * Update bin/node/runtime/src/exchange.rs Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com> * typo * Update modules/currency-exchange/Cargo.toml Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com> * add docs to currency-exchange module * change tests names * cargo fmt --all * Update bin/node/runtime/src/exchange.rs Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com> * Update bin/node/runtime/src/exchange.rs Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com> * Update bin/node/runtime/src/exchange.rs Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com> * Update bin/node/runtime/src/exchange.rs Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com> * Update bin/node/runtime/src/exchange.rs Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com> * fixed verify_transaction_finalized for siblings of finalized blocks * cargo fmt --all * added double spend note * cargo fmt --all Co-authored-by: Tomasz Drwięga <tomusdrw@users.noreply.github.com> Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com>
Change the privileged asset roles from
AccountId
toOption<AccountId>
. When theowner
is set toNone
, only governance would be able to restore the role.For discussion, if
owner
isSome
, and they want to set a lower rank role fromNone
toSome
, should that require governance?This would look similar to the
PoolRoles
struct in Nomination Pools.Originally posted by @joepetrowski in paritytech/substrate#12310 (comment)
The text was updated successfully, but these errors were encountered: