Hi,

I got stuck at deploying of consensus contracts in Create MoC's instance, finish the deployment of consensus contracts and generate initial keys section.

Where I got stuck:

SAVE_TO_FILE=true POA_NETWORK_CONSENSUS_ADDRESS=<POA_NETWORK_CONSENSUS_CONTRACT_ADDRESS> MASTER_OF_CEREMONY=<MOC_ADDRESS> ./node_modules/.bin/truffle migrate --reset --network sokol

Log: no timeout, no error. I think account is unlocked.

Running migration: 1_initial_migration.js
  Deploying Migrations...
  ... 0xd2af1852703aa060701a57bf112fdca2636fc3a9d8f130870aa6290be080f667

I needed to update the address of unlock and engine_signer section to my MOC address to make party work.
Because the address was not my MOC address somehow.
So I might have failed to follow steps....

Could you give me hints?

Thanks in advance.

We should rewrite Adding a Validator key / Use Case 1 and Ballot Finalization Order sections on Manage Validator Ballots page after HF in Core which is scheduled for November 17, 2018.

The new smart contracts and Governance DApp allow to add a new Validator with three keys at once in the same ballot (mining key, voting key, payout key), so we should update descriptions mentioned above accordingly.

Lets minimize the damage to our eyes :)

https://github.com/poanetwork/wiki/wiki/POA-Installation

Replace 1.8... with something like "a stable Parity version, like 1.10.6 or later"

I did not find a way to edit the Wiki directly, .

The text on the page https://github.com/poanetwork/wiki/wiki/Ballots-Overview.-Life-cycle-and-limits#limits tells that there are global ballots limits.

According to the current smart contracts implementations, we have ballot limits for each validator separately (not global). E.g., https://github.com/poanetwork/poa-network-consensus-contracts/blob/fd2b2c6c2f4a4b1b5bdacd4f9510397e3c5124fa/contracts/BallotsStorage.sol#L135-L149

Therefore, the text on the page https://github.com/poanetwork/wiki/wiki/Ballots-Overview.-Life-cycle-and-limits#limits should be corrected.

For consistency when offering support documentation, please update the logo on the POA Network Wiki - https://github.com/poanetwork/wiki - to the current release. Here's the link to the latest logo version:
https://avatars2.githubusercontent.com/u/28943015?s=200&v=4

Thank you very much.

Wrong link is in Getting started -> Wallets -> MetaMask

Problem:
bootnodes.txt location is outdated
Solution:
update MoC instruction

https://github.com/poanetwork/wiki/wiki/Deleting-a-Node is correct in itself, but is applicable to azure templates that are not used now (ansible playbooks are used instead). In future we'll probably make azure templates up-to-date with playbooks, so I propose to not delete this file completely, but remove the reference to it from wiki.
Validator's AWS instructions mention how to remove an existing node from aws: https://github.com/poanetwork/wiki/blob/master/validator-guide-new.md#remove-instance

This is not issue but more like question.

I got stacked at POA Network Consensus contract process.
The document says "where MASTER_OF_CEREMONY is the public address of Master of Ceremony from the previous step...". but I have no idea which step ...

Is MASTER_OF_CEREMONY address same as owner address?

Thanks in advance.

I am currently setting up a POA network utilizing the your smart contracts, but I am having issues when launching the ansible playbooks. Namely because I see there is a NonAWS way for launching nodes, but this is not covered in the MOC Setup.

For instance, if I comment out the following in /group_vars/all
#access_key: "INSERT KEY HERE"
#secret_key: "INSERT SECRET HERE"
#awskeypair_name: "keypairname"

#vpc_subnet_id: "subnet-ID-number"

I still receive an error regarding undefined variables when running ansible-playbook. Perhaps it should be made more flexible to account for various virtual server providers

Problem:
README.md is master branch is outdated and not used for navigation
Solution:
Replace README.md with Home and sync it with every change

Challenge Description:

POA Network is sponsoring Ethereal with three equal bounty prizes of $500 Dai each! The challenge itself is inspired by our POA Game Fund where the POA Core is the perfect network for high transaction DApps and games due to its speed, cost efficiency and EVM compatibility. Deploying a game to POA Core is very easy and should pose no difficulty to anyone ready to accept the challenge!

Bounty:

Amount: 500 Dai.

Submission Requirements:

The main requirement is that the contracts and DApp/game are deployed on POA Core. If you wish to use xDai Chain instead to take advantage of stable gas prices, this is allowed as long as a majority of the contracts are deployed on POA Core.

Resources:

• POA Core resources: https://forum.poa.network/t/core-network-resources/1797
• Deployment guide for POA Core: https://forum.poa.network/t/tutorial-deploying-your-dapp-to-poa-network/1804

Submission Deadline:

April 30th.

Judging Criteria:

• Originality of concept.
• Difficulty of technical implementation.
• Fun factor!

Judging Date:

Judging will be at the end of the Hackathon on April 30th.

Challenge Description:

POA Network is sponsoring Ethereal with three equal bounty prizes of $500 Dai each! The challenge itself is inspired by our POA Game Fund where the POA Core is the perfect network for high transaction DApps and games due to its speed, cost efficiency and EVM compatibility. Deploying a game to POA Core is very easy and should pose no difficulty to anyone ready to accept the challenge!

Bounty:

Amount: 500 Dai.

Submission Requirements:

The main requirement is that the contracts and DApp/game are deployed on POA Core. If you wish to use xDai Chain instead to take advantage of stable gas prices, this is allowed as long as a majority of the contracts are deployed on POA Core.

Resources:

• POA Core resources: https://forum.poa.network/t/core-network-resources/1797
• Deployment guide for POA Core: https://forum.poa.network/t/tutorial-deploying-your-dapp-to-poa-network/1804

Submission Deadline:

April 30th.

Judging Criteria:

• Originality of concept.
• Difficulty of technical implementation.
• Fun factor!

Judging Date:

Judging will be at the end of the Hackathon on April 30th.

parity --chain /path/to/spec.json --reserved-peers /path/to/bootnodes.txt

ERROR
Spec json is invalid: missing field eip1108_transition_base at line 65 column 181

parity --chain /path/to/spec.json --reserved-peers /path/to/bootnodes.txt **ui
**
ERROR
Found argument 'ui' which wasn't expected

Problem: Whitepaper contains a note about a feature that won't be implemented, on the diagrams https://github.com/poanetwork/wiki/wiki/POA-Network-Whitepaper#creating-a-new-ballot and https://github.com/poanetwork/wiki/wiki/POA-Network-Whitepaper#voting-on-a-ballot - the note is as follows: "the method also checks, if any ballots are finished, but not yet finalized by the current time. If any, it finalizes them."

Solution: Remove that note from those diagrams.

Hi humans, i'm looking at playing with the POA network to familiarise myself with it and see how it can apply to projects, notably with the ERCC20 to ERC20 bridge, and i wondered if there were any documentation on running your own private POA network ?

Kind regards.

Recent changes in setup procedures need to be reflected in MoC instruction:

• there is no need to create a separate branch of network-consensus contract
• there is no need to compile it
• check configs

This is for discussion... few thoughts regarding https://github.com/poanetwork/wiki/wiki/Non-AWS-Node-Setup

• SSH-keys: it is not clear whether creating a separate key for each node significantly enhances security. On the downside it increases the possibility of forgetting/mixing passwords and losing access to nodes. Besides, there are other ways of storing ssh keys like hardware tokens, etc. I think we should avoid giving direct instructions here and rely on user's choice... we can't know his workflow and habits (does he share his computer with someone? does he install spyware?). Hopefully, if he's into crypto, he understands the importance of keeping private keys private and using strong passwords, in which case, he can manage with a few keypairs.
  So, as a guideline, I think we should recommend creating a separate password-protected key for each POA network (= 2 keys max at the moment). This can also help prevent accidental updates on wrong network. But, we leave it up to user to choose a keypair here.
  This note should go to the very beginning of the doc, because ---->

• ----> in the opening line "Create Ubuntu 16.04 Server Image..." it assumes that user created a server himself, most probably he had to provide ssh key during this process. Later down the doc he creates a new user on the server and a new key, but access with the original key is not revoked, so there are two keys to access the same server now. I think if in (1) we describe how to choose a key for the server then there is no need to create additional keypair later.

• however, it should be explicitly stated, that user must use a password-protected keypair, even though ssh allows password-less keys. + each key should have a different strong password.

• In the original versions of these guides I missed that there is an ansible-playbook option --ask-become-pass that prompts for sudo password. So it seems we can remove the requirement to create an additional user who can execute sudo without password, and add a note about this option instead.

• When there are multiple keypairs in ~/.ssh, it's possible to tell ansible-playbook which one to use by providing --private-key option with full path to the private key, e.g. ansible-playbook -i hosts site.yml --key-file ~/.ssh/id_poa_sokol.

When I open my MEW in the POA network I get a warning that states " We do not know the correct path for this network. Please open a github issue so we can discuss/be enlightened.

We need to make sure MEW knows the correct derivation path for POA. And removes the issue

Challenge Description:

POA Network is sponsoring Ethereal with three equal bounty prizes of $500 Dai each! The challenge itself is inspired by our POA Game Fund where the POA Core is the perfect network for high transaction DApps and games due to its speed, cost efficiency and EVM compatibility. Deploying a game to POA Core is very easy and should pose no difficulty to anyone ready to accept the challenge!

Bounty:

Amount: 500 Dai.

Submission Requirements:

The main requirement is that the contracts and DApp/game are deployed on POA Core. If you wish to use xDai Chain instead to take advantage of stable gas prices, this is allowed as long as a majority of the contracts are deployed on POA Core.

Resources:

• POA Core resources: https://forum.poa.network/t/core-network-resources/1797
• Deployment guide for POA Core: https://forum.poa.network/t/tutorial-deploying-your-dapp-to-poa-network/1804

Submission Deadline:

April 30th.

Judging Criteria:

• Originality of concept.
• Difficulty of technical implementation.
• Fun factor!

Judging Date:

Judging will be at the end of the Hackathon on April 30th.

Number of cores, amount of memory are of particular interest as this determines the cost. Extra points for specifying VM type for Azure/AWS.

For instance, would the B-series VMs in Azure work well for bootnodes? https://azure.microsoft.com/en-us/blog/introducing-b-series-our-new-burstable-vm-size/

Best, MM

We need to add a new page describing Emission Funds Ballot ballot type in Governance section of Wiki.

This issue is motivated by a long debug session around the Sokol Hard Fork upgrade process.

A user had installed a bootnode on Azure using the ansible deployment-playbook scripts but was unable to update his node using the following documents:

https://github.com/poanetwork/wiki/wiki/HFs-Sokol-2018-01-08

In my view there are several issues:

Specification -- There is no general strategy around how deployment ssh keys should be managed given a user may have multiple nodes running both on the testnet and core ( production ) networks. For example, if a user is running both a bootnode and Validator node on production should they deployments use same ssh keys? Further, if someone is running (2) Validator nodes on production, what then?

Implementation of deployments -- Scripts need to implement above specification or explicitly state what assumptions are around ssh key/pairs for deployments

For above see Issue: ( poanetwork/poa-devops#6 )

Documentation -- using above can call out all assumptions or provide clear guidance

Step 9 says:

set the following options as follows in group_vars/all:
allow_validator_ssh: true
allow_validator_p2p: true
associate_validator_elastic_ip: false

This is already set in the sources pulled from git, so seems redundant.

A suggestion is to replace an old sokol-explorer.poa.network with sokol.poaexplorer.com in README.md.

https://github.com/poanetwork/wiki/wiki/Bootnode-Setup-AWS sets the value of allow_bootnode_rpc to false, but in all.example it is set to true on both sokol and core branches.

Link does not work in "Chapter VI - in which MoC changes links in Validator's README": https://github.com/poanetwork/wiki/blob/master/validator-guide-new.md#exchange-your-initial-keys-for-mining-payout-and-voting-keys

Notes:

Deployment -> Create Instance: When I ran “ansible-playbook validator.yml” was not prompted for SSH key passphrase.

“Download and Configure Playbook” -> Step 7 recommends m5.large but was not available in my region … chose m4.2xlarge

Deployment -> Close external access -> Step 2 reads:
“if you later need to revoke access change necessary options to true and run the script again. E.g. to revoke ssh access to your node, set allow_validator_ssh: true.”

revoke not right word … do you mean “revert” or “enable”

Screenshots on the page are outdated: https://github.com/poanetwork/wiki/wiki/Validator-Set-Metadata

Getting started/
 Installation [TBD]
 Wallets/
   MEW
   Ledger
   Tresor
   Trust
 Exchanges [TBD]
 FAQ
Roles/
 Validator/
   AWS
   Non-AWS
 Master of Ceremony
 Full/Boot node operator/
    AWS
    Non-AWS
POA/
  Papers [TBD]
  What is POA
  Governance
  Role of validator [TBD]

For TBD section, please create placeholder pages

At least one member of community is using AWS to host a bootnode. Are these instruction sufficient? If so then should clean up "non-aws" language, if should there be a separate Bootnode Setup AWS document?

I Need to create a new section on the Wiki page for Telegram rules. It will contain the following with details below each point.

Rules

• No swearing
• No abusing/disrespect to other users.
• No FUD or rumours
• No price speculation.
• No spamming.

--- Keep topics relevant to POA

https://github.com/poanetwork/wiki/wiki/Frequently-Asked-Questions#about-the-token-sale

We should reword the answer to question 8 since the answer is not 100% accurate. Replacing "Never" with "NOT".

"No it will NOT be on EtherDelta as POA is NOT a ERC20 token. It has its own network & blockchain and will be released to regular exchanges, not one based on ERC20 tokens only."

Add CytoWise to list of wallets. Image file is below:

https://onedrive.live.com/?authkey=%21AF1zq9zCXjOXpfQ&id=5719CE4C3F099FAC%21115570&cid=5719CE4C3F099FAC

Lets reword the answer to the following:

"POA Network is not affiliated with any crypto exchange and we have no insights on their internal processes. Therefore, we cannot comment on the timing of the listing, neither can we point to where the token will be listed, until this is announced by the exchanges."

Refresh sequence diagrams here and add a new diagram for Emission Funds Ballot.