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

Some issues setting up a ceremony on Gesell #272

Open
sacha-l opened this issue Nov 24, 2022 · 3 comments
Open

Some issues setting up a ceremony on Gesell #272

sacha-l opened this issue Nov 24, 2022 · 3 comments

Comments

@sacha-l
Copy link

sacha-l commented Nov 24, 2022

Setup:

  • I'd suggest to give another option for developer to build the client from source:
  1. git clone https://github.com/encointer/encointer-node.git
  2. cargo build --release
  3. chmod +x target/release/encointer-client-notee
  4. NURL=wss://gesell.encointer.org && NPORT=443
  5. alias nctr-gsl="./target/release/encointer-client-notee -u $NURL -p $NPORT"

Funding:

  • Alice account for Gesell: if I were to use Polkadot JS Apps UI, what instructions am I missing to fund an account?
  • Trying to fund an account using encointer-client-notee client and getting the following insufficient funds error: [2022-11-24T16:03:24Z ERROR encointer_client_notee::utils] insufficient funds: fee: 86298000 ed: 500 bal: 81699625
@brenzi
Copy link
Member

brenzi commented Nov 24, 2022

Faucet has been topped up, so the funding issues should be solved for now

@brenzi
Copy link
Member

brenzi commented Nov 24, 2022

on the building instructions: sure, that could be a good thing to add and it can be easily skipped

@sacha-l
Copy link
Author

sacha-l commented Nov 25, 2022

Cool. Yes the faucet was dry, now its fixed thanks.

For instructions, I can make a PR to add. Other issues that came up:

  • It would be nice to have instructions on, when registering a community how to use an existing account or clarify that using the cli tool with new-account is just best practice. Right now I get thread 'main' panicked at 'called Result::unwrap()on anErr value: InvalidPhrase', client/src/utils.rs:230:83 even following the keystore file creation pattern, not sure why.
  • Instructions missing for addinf community metadata. I get the error: thread 'main' panicked at 'called Result::unwrap()on anErr value: CommunityMetadataError::InvalidAmountCharactersInSymbol(4)', client/src/community_spec.rs:127:21 which I understand why now, but we could also add this to clarify in the docs. In case, the symbol length was one character too long.

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

2 participants