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

add dispatchable filtering for PoA mainnet launch #35

Closed
brenzi opened this issue Sep 7, 2021 · 5 comments · Fixed by #67
Closed

add dispatchable filtering for PoA mainnet launch #35

brenzi opened this issue Sep 7, 2021 · 5 comments · Fixed by #67
Assignees

Comments

@brenzi
Copy link
Collaborator

brenzi commented Sep 7, 2021

When we launch a standalone mainnet, we don't want users to be able to send extrinsics immediately. Especially token actions need to be suppressed before the official token generation event

as done for parachain:
https://github.com/integritee-network/parachain/blob/75650f539c07de174ef6d4e0cd2c60347907fc30/polkadot-parachains/shell-runtime/src/lib.rs#L153-L161

But please disable all Vesting calls, not only vested_transfer

@brenzi brenzi transferred this issue from integritee-network/worker Sep 7, 2021
@echevrier
Copy link
Contributor

Add vesting pallet to node
Block all vesting, multisig and balances commands only for standalone mainnet
Add compiler flag mainnet

@echevrier
Copy link
Contributor

If we suppress all balances call, as is done in the parachain, we can't start the worker:

*** Starting integritee-worker
Worker Config: Config { node_ip: "ws://127.0.0.1", node_port: "9970", worker_ip: "127.0.0.1", worker_rpc_port: "2070", worker_mu_ra_port: "3443", ext_api_url: Some("ws://127.0.0.1:2070") }
IntegriTEE Worker v0.8.0
*** Starting enclave in development mode
MRENCLAVE=JD2S6LSgysK1HtQhCt84M5ta14UFx2Vat76YSqwDCcov
MU-RA server listening on ws://127.0.0.1:3443
[+] RPC direction invocation server listening on wss://127.0.0.1:2070
[+] bootstrap funding Enclave form Alice's funds
[!] skipping remote attestation. Registering enclave without attestation report.
[>] Register the enclave (send the extrinsic)
[2021-09-28T15:22:24Z ERROR ws::handler] WS Error <Custom(Extrinsic("extrinsic error code 1010: Invalid Transaction: Inability to pay some fees (e.g. account balance too low)"))>
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: InvalidHexString(InvalidStringLength)', service/src/main.rs:336:71
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

@echevrier
Copy link
Contributor

What about the treasury calls?

@brenzi
Copy link
Collaborator Author

brenzi commented Sep 29, 2021

filter treasury calls too

@echevrier
Copy link
Contributor

And what about the balances call? And this error?

If we suppress all balances call, as is done in the parachain, we can't start the worker:

*** Starting integritee-worker
Worker Config: Config { node_ip: "ws://127.0.0.1", node_port: "9970", worker_ip: "127.0.0.1", worker_rpc_port: "2070", worker_mu_ra_port: "3443", ext_api_url: Some("ws://127.0.0.1:2070") }
IntegriTEE Worker v0.8.0
*** Starting enclave in development mode
MRENCLAVE=JD2S6LSgysK1HtQhCt84M5ta14UFx2Vat76YSqwDCcov
MU-RA server listening on ws://127.0.0.1:3443
[+] RPC direction invocation server listening on wss://127.0.0.1:2070
[+] bootstrap funding Enclave form Alice's funds
[!] skipping remote attestation. Registering enclave without attestation report.
[>] Register the enclave (send the extrinsic)
[2021-09-28T15:22:24Z ERROR ws::handler] WS Error <Custom(Extrinsic("extrinsic error code 1010: Invalid Transaction: Inability to pay some fees (e.g. account balance too low)"))>
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: InvalidHexString(InvalidStringLength)', service/src/main.rs:336:71
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

@echevrier echevrier linked a pull request Oct 5, 2021 that will close this issue
@brenzi brenzi closed this as completed in #67 Oct 7, 2021
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 a pull request may close this issue.

2 participants