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

Change pubkey addresses for multisig addresses and testnet. #85

Merged
merged 1 commit into from
Dec 26, 2014

Conversation

vertoe
Copy link

@vertoe vertoe commented Dec 26, 2014

I propose to update public key versions from the bitcoin defaults to darkcoin uniques. To avoid confusion:

  • change script public key address prefex from '3' (like bitcoin) to '7'
  • change testnet public key address prefix from 'm/n' (like bitcoin) to 'x/y'
  • change testnet script public key address prefix from '2' (like bitcoin) to '8/9'

Impact is to be discussed. The private key versions are untouched in this commit, so any fund is still valid and redeemable.

@vertoe
Copy link
Author

vertoe commented Dec 26, 2014

Impact is low, as the private keys and redeem script remain valid. We should add it to the release notes though ;-)

Old testnet wallet:
screenshot-4

Same wallet with new public key versions:
screenshot-5

Creating multisignature addresses:
screenshot-6

@darkcoinproject
Copy link

Looks great. I tested it and everything worked as expected.

darkcoinproject added a commit that referenced this pull request Dec 26, 2014
Change pubkey addresses for multisig addresses and testnet.
@darkcoinproject darkcoinproject merged commit dc71c6d into dashpay:v0.11.0.x Dec 26, 2014
@fernandogutie
Copy link

It makes a lot of sense, especially for multisigs. In the testnet cases the impact of an error is low, but sending to the wrong multisig means losing real funds.

@vertoe
Copy link
Author

vertoe commented Dec 26, 2014

Cheers.

@darkcoinproject
Copy link

@Fernando3 The client will only accept addresses starting with whatever the script pubkey is set to, so in this case the old addresses will become invalid. Worst case is they'll have to ask for the new address.

@fernandogutie
Copy link

Cool. I was talking about an error in the current scenario of multisigs starting with 3, in which you could send drk to a btc multisig.

@darkcoinproject
Copy link

Ah, that's a solid point.

@vertoe vertoe deleted the devel-0.9-keys branch December 27, 2014 07:57
FornaxA pushed a commit to ioncoincore/ion that referenced this pull request Jul 6, 2020
FornaxA pushed a commit to ioncoincore/ion that referenced this pull request Jul 6, 2020
Cherry-pick release notes from v5 release branch
PastaPastaPasta added a commit that referenced this pull request Jan 31, 2024
ogabrielides added a commit to ogabrielides/dash that referenced this pull request Oct 4, 2024
3ffa7fa2b6 chore: bump version to 1.3.2 (dashpay#94)
0f4efc9327 Merge pull request dashpay#88 from HashEngineering/feat/support-android
a181889489 fix: rust bindings build for macos (dashpay#89)
69bdc1aac7 Merge pull request dashpay#85 from kwvg/debug
39791d4e31 build: print build options after configure
73106a0121 build: use `-mbranch-protection=bti` on supporting `aarch64` compilers
6a3c28f6ca build: use stricter `-Werror` when testing compile flags
7a1b227637 build: rename {`NO`}`WARN_CFLAGS` to {`NO`}`WARN_FLAGS`, use with C{++}
28bea63838 build: set {`NO`}`WARN_CFLAGS` flags if not overridden and uniformly
32c2f0f5f8 trivial: rename `CORE_CXXFLAGS` to `CORE_FLAGS`, use with C{++}
b630c2c323 build: append `HARDENED_FLAGS` to `AM_CFLAGS`
e6008148e4 trivial: rename `HARDENED_CXXFLAGS` to `HARDENED_FLAGS`
af0e3daef5 build: subsume `PI{C,E}_FLAGS` into `HARDENED_CXXFLAGS`
9ff8618a1b build: expand `--disable-optimizations` to include `-O0` and `-fwrapv`
3036b83181 build: expand `--enable-debug` to include `-O0`, `-ftrapv` and dbg info
c90d43d43b build: add check to see if `CFLAGS` has been overridden
2d77f7ae49 build: remove vestigial `LIBTOOL_{CXX,CPP,LD}FLAGS`, `HARDENED_CPPFLAGS`
883a098868 build: autodetect i?86 and arm as 32-bit
deb3269820 build: don't specify exact `{CPU_}ARCH` if optimizations are disabled
720d49a44b trivial: fix indentation for `want_backend` check
f9328320af build: use `easy` backend if optimizations are disabled unless specified
3687cd59e0 build: define new flag `--enable-optimizations`
f82bfee5dd build: ensure help string format matches Autotool defaults
d68920063e build: define arguments as `--enable-[term]` instead of `--disable-[term]`
7f41e7dd16 fix: support android
1c2fc79c19 feat(rust): allow to move G1 and G2 elements between threads (dashpay#87)
3540b8bbed feat: debug with data hex (dashpay#86)

git-subtree-dir: src/dashbls
git-subtree-split: 3ffa7fa2b62aecf3943c142508de4b7ec6005bb5
PastaPastaPasta pushed a commit that referenced this pull request Oct 10, 2024
4e070243ae chore: bump version to 1.3.3 (#99)
d93956254e ci: disable Go bindings CI for macos for now (#98)
ae40c5c86d Merge pull request #97 from PastaPastaPasta/refac/pybind-bump-2.13.6
e835ece935 refactor: bump pybind version to 2.13.6
eda5d6a402 chore: change of gmp source (#95)
61f95aa80e chore: cleanup 6.2.1 left overs (#96)
adbd094409 Merge pull request #92 from kwvg/darwin_gmp
062ee6726b Merge pull request #90 from UdjinM6/fix_aarch_arch
3538d8b033 fix: aarch64 is not supported, should set ARCH to RELIC_NONE
e27a62f4a2 revert: disable gmp if targeting darwin on aarch64 when on 'auto'
bb2fe6ee55 build: enforce minimum version of libgmp based on arch and platform
9832b7a132 build: replace deprecated macros `AC_PROG_CC_C99` and `AM_PROG_CC_C_O`
b2428718b9 Merge pull request #91 from UdjinM6/fix_macos_test_build
3ffa7fa2b6 chore: bump version to 1.3.2 (#94)
0f4efc9327 Merge pull request #88 from HashEngineering/feat/support-android
a181889489 fix: rust bindings build for macos (#89)
738d187359 fix: detect gmp via brew earlier
ce4d6a47b6 fix: install libtool
4fa46ccaff fix: use macos-latest for test build
69bdc1aac7 Merge pull request #85 from kwvg/debug
39791d4e31 build: print build options after configure
73106a0121 build: use `-mbranch-protection=bti` on supporting `aarch64` compilers
6a3c28f6ca build: use stricter `-Werror` when testing compile flags
7a1b227637 build: rename {`NO`}`WARN_CFLAGS` to {`NO`}`WARN_FLAGS`, use with C{++}
28bea63838 build: set {`NO`}`WARN_CFLAGS` flags if not overridden and uniformly
32c2f0f5f8 trivial: rename `CORE_CXXFLAGS` to `CORE_FLAGS`, use with C{++}
b630c2c323 build: append `HARDENED_FLAGS` to `AM_CFLAGS`
e6008148e4 trivial: rename `HARDENED_CXXFLAGS` to `HARDENED_FLAGS`
af0e3daef5 build: subsume `PI{C,E}_FLAGS` into `HARDENED_CXXFLAGS`
9ff8618a1b build: expand `--disable-optimizations` to include `-O0` and `-fwrapv`
3036b83181 build: expand `--enable-debug` to include `-O0`, `-ftrapv` and dbg info
c90d43d43b build: add check to see if `CFLAGS` has been overridden
2d77f7ae49 build: remove vestigial `LIBTOOL_{CXX,CPP,LD}FLAGS`, `HARDENED_CPPFLAGS`
883a098868 build: autodetect i?86 and arm as 32-bit
deb3269820 build: don't specify exact `{CPU_}ARCH` if optimizations are disabled
720d49a44b trivial: fix indentation for `want_backend` check
f9328320af build: use `easy` backend if optimizations are disabled unless specified
3687cd59e0 build: define new flag `--enable-optimizations`
f82bfee5dd build: ensure help string format matches Autotool defaults
d68920063e build: define arguments as `--enable-[term]` instead of `--disable-[term]`
7f41e7dd16 fix: support android
1c2fc79c19 feat(rust): allow to move G1 and G2 elements between threads (#87)
3540b8bbed feat: debug with data hex (#86)

git-subtree-dir: src/dashbls
git-subtree-split: 4e070243aed142bc458472f8807ab77527dd879a
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