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

(Core) Activate on-chain randomness #139

Merged
merged 1 commit into from
Mar 23, 2020
Merged

(Core) Activate on-chain randomness #139

merged 1 commit into from
Mar 23, 2020

Conversation

varasev
Copy link
Contributor

@varasev varasev commented Mar 23, 2020

The spec.json is changed for POA Core chain to activate the on-chain randomness described in https://www.poa.network/for-developers/on-chain-random-numbers.

The changed spec requires a validator to have Parity Ethereum v2.7.2 node.

The activation will occur at block #14350721 (31 March 2020 ~05:51 pm UTC).

Copy link
Member

@igorbarinov igorbarinov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@andogro please add info to https://www.poa.network/for-validators/hard-forks
and https://www.poa.network/for-developers/on-chain-random-numbers

I propose to add addresses of contracts for Core and Sokol here https://www.poa.network/for-developers/on-chain-random-numbers, also can duplicate it here https://www.poa.network/for-developers/developer-resourses Let's try to use tabs in Gitbook to switch between Core and Sokol details

@varasev varasev merged commit f7b0d1d into core Mar 23, 2020
@varasev varasev deleted the core-with-randomness branch March 23, 2020 15:38
@varasev
Copy link
Contributor Author

varasev commented Mar 23, 2020

The instruction for POA Core validators to activate Randomness: https://forum.poa.network/t/on-chain-randomness-activation-on-core/3307

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 this pull request may close these issues.

None yet

2 participants