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

feat(core-magistrate-crypto): add ports to bridgechain registration/update #3255

Merged
merged 27 commits into from
Nov 20, 2019

Conversation

dated
Copy link
Contributor

@dated dated commented Nov 13, 2019

Summary

Adds a ports property to the bridgechain transaction types. This property holds an object with plugin names as keys, and port numbers as values like the ports property on peers. For the time being the only allowed plugin to be included is @arkecosystem/core-api.

Checklist

  • Documentation (if necessary)
  • Tests (if necessary)
  • Ready to be merged

@lgtm-com
Copy link

lgtm-com bot commented Nov 13, 2019

This pull request introduces 1 alert when merging d22db35 into 0663b0f - view on LGTM.com

new alerts:

  • 1 for Assignment to constant

@dated dated marked this pull request as ready for review November 14, 2019 11:50
@ghost ghost removed the Status: In Progress label Nov 14, 2019
@ghost ghost added the Status: Needs Review label Nov 14, 2019
spkjp
spkjp previously requested changes Nov 14, 2019
Copy link
Contributor

@spkjp spkjp left a comment

Choose a reason for hiding this comment

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

We need a devnet-only milestone to not need to rollback again. Can you add one like we already did for invalid timestamps?

In other words we need to skip the new serde when on devnet and some milestone constant (e.g. skipBridgechainPortSerialization) is set. Like here:
https://github.com/ArkEcosystem/core/blob/develop/packages/crypto/src/blocks/block.ts#L230

And to get around the new schema we can simply use the exceptions.json where most bridgechain transactions already got added.

@dated
Copy link
Contributor Author

dated commented Nov 14, 2019

Sure, I'll have a look as soon as possible.

@dated
Copy link
Contributor Author

dated commented Nov 15, 2019

#3258 might require a rollback - is that up for discussion at the moment after all?

@ghost
Copy link

ghost commented Nov 20, 2019

A collaborator has approved this PR. A maintainer will merge this PR shortly. If it shouldn't be merged yet, please leave a comment saying so and we'll wait.

Thank you for your contribution!

@ghost
Copy link

ghost commented Nov 20, 2019

A collaborator has approved this PR. A maintainer will merge this PR shortly. If it shouldn't be merged yet, please leave a comment saying so and we'll wait.

Thank you for your contribution!

@faustbrian faustbrian merged commit c520d81 into ArkEcosystem:develop Nov 20, 2019
@ghost
Copy link

ghost commented Nov 20, 2019

Your pull request has been merged and marked as tier 2. It will earn you $100 USD.

@ghost ghost removed the Status: Needs Review label Nov 20, 2019
@dated dated deleted the feat/bridgechain-ports branch November 20, 2019 06:17
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.

3 participants