-
Notifications
You must be signed in to change notification settings - Fork 3k
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
M prefix added for script addresses #279
Conversation
@@ -126,6 +126,7 @@ class CMainParams : public CChainParams { | |||
|
|||
base58Prefixes[PUBKEY_ADDRESS] = std::vector<unsigned char>(1,48); | |||
base58Prefixes[SCRIPT_ADDRESS] = std::vector<unsigned char>(1,5); | |||
base58Prefixes[SCRIPT_ADDRESS2] = std::vector<unsigned char>(1,50); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a SCRIPT_ADDRESS2 for testnet also so we can test it out on testnet.
Does this the |
Output: |
Looks good 👍 Just need an RPC test to test functionality and then its good to merge. |
Checked the ability to receive and spend from old and new addresses plus existing RPC calls. Needs some python RPC tests though. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to change the file mode to +x for this file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just realized this file needs to be added to the automated tests in https://github.com/litecoin-project/litecoin/blob/master/qa/pull-tester/rpc-tests.py#L103
two tests are failing,possibly because of default address prefix change
|
Errors in p2p-segwit.py are due to the use of wrong version bits. The function self.build_next_block() produces blocks with version = 4, which are rejected by litecoind. Errors in nulldummy.py are also due to wrong version bits used. We should fix them in another pull request. |
Why another PR? No need, we could always change the PR title and outline all commits and describe what each commit fixes. |
The two PRs are not related. Isn't it better to separate them? |
If the test breaks are not related to this PR, then this can be merged. I have confirmed those tests do fail on master. |
|
hi. my ltc 3.548239 |
to LY3X9yDv1kVsyC2Trkuo1hhT13dx2AAP3h please |
Hi there, I'm attempting to run down a transaction which has led me here to this conversation. I was wondering if anyone could help? I purchased some litecoin and sent it to the address: My search led me to "3/M prefix". |
Test cases for M prefix addresses are still needed.