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

Adds support for IOTA altcoin: https://iota.org/ #929

Closed
wants to merge 252 commits into from
Closed

Conversation

cj4c0b1
Copy link

@cj4c0b1 cj4c0b1 commented Sep 15, 2017

Adds support for IOTA altcoin: https://iota.org/

ManfredKarrer and others added 27 commits July 17, 2017 10:05
…named to Bisq -> we rename the app data dir).
… and move protobuf-util to common like the other protobuf dependency. Also make it visible outside of test
the lines
SetupIconFile={localappdata}\Bisq.ico
UninstallDisplayIcon={localappdata}\Bisq.ico
are wrong, Bisq folder is located in {localappdata} and the icons are inside Bisq\ path
so a more coherent change would be
SetupIconFile={localappdata}\Bisq\Bisq.ico
UninstallDisplayIcon={localappdata}\Bisq\Bisq.ico
but even this would be wrong since SetupIconFile directive as it is used on compile time only and should contain the absolute path to the icon
…c initializer to SeedNodeMain, ProviderMain and StatisticsMain
Update displayStrings.properties
A new version (v3.0.0-M1) of the enforcer plugin was released on July
27th. If for whatever reason that new version ends up in the local ~/.m2
cache, it results in broken builds because the new version's checksum
gets validated instead of the older v1.4.1 checksum being validated.
This is because the version provided to check was set simply to
'RELEASE', i.e. an alias indicating "whatever the latest release happens
to be". This commit fixes #897 and avoids these potential build failures
by pinning the version explicitly to v1.4.1. This forces the correct
checksum to get validated, in turn causing the build to pass as
expected.
Previously every successful build was triggering a notification to be
sent to Slack, and this is too noisy.
This change removes the need to clone and build bisq's forks of
bitcoinj, libdohj and btcd-cli4j in order to build bisq itself.
# Conflicts:
#	doc/build.md
…idator and AltCoinAddressValidatorTest and 2 specific classes: PNCAddressValidator and PNCParams.
Add new altcoin with code "PNC"
@ManfredKarrer
Copy link
Member

This is not a correct PR.

@tr37ion
Copy link

tr37ion commented Jan 8, 2018

Will you add it to the next version? Would be nice.

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